Evidence CodeMarine can inspect
- Workspace changes and resulting source files
- Dependencies, lockfiles, rules and skills
- CodeMarine-mediated MCP tool activity
Claude integration
Independent security around Claude.
Continuous workspace security for Claude-written code, plus provider-specific hook and MCP paths.
INTEGRATION PROFILE Beta
- Provider
- Claude Code and Claude Desktop
- Primary transport
- Workspace watcher, Claude Code hooks and CodeMarine MCP
- 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 Claude Code shell and write operations after setup
- Defined catastrophic command classes through the local guard
What you should not assume
- Live host proof is not available yet, so hook surfaces remain Setup needed
- Claude Desktop native connectors and UI actions are not covered
- Cowork and computer-use actions are not intercepted by local hooks
Native controls protect Claude. 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 Claude.
Map the current workspace, provider paths and limits before deciding which controls to rely on.
