Evidence CodeMarine can inspect
- Workspace changes regardless of the Codex surface
- Apply-patch write activity through the available adapter
- Dependencies and agent configuration written to the project
Codex integration
Independent security around Codex.
Independent scanning for Codex changes today, with stronger command and MCP mediation in active development.
INTEGRATION PROFILE Beta
- Provider
- Codex CLI, IDE and desktop surfaces
- Primary transport
- Workspace watcher, plugin and write adapter
- Workspace scanning
- Available
- Blanket runtime protection
- Not claimed
What the integration can see and where it stops.
Workspace observation and pre-execution control are shown separately.
Defined blocking potential
- Supported write operations when blocking setup is enabled
What you should not assume
- The default integration is readiness-focused today
- Codex Bash and MCP interception are planned
- Hosted or specialized tool paths may sit outside local hook coverage
Native controls protect Codex. CodeMarine protects the shared environment.
Keep provider permissions and sandboxes. Add one deterministic policy around the workspace and the rest of your stack.
Controls the surfaces and execution modes owned by the provider.
Secures resulting code, software supply chain and supported actions under one control model.
A configured adapter is only the start.
Effective protection needs the right adapter, current configuration, healthy decision path and matching host proof.
No live proof means Setup needed or Beta.
- 01
InstallPlace the supported adapter and configuration.
- 02
VerifyCheck version, integrity and workspace binding.
- 03
ProveRun a harmless nonce-bound canary through the real host.
- 04
MaintainExpire proof when the host, policy or configuration changes.
Evaluate CodeMarine with Codex.
Map the current workspace, provider paths and limits before deciding which controls to rely on.
