Evidence CodeMarine can inspect
- Local workspace edits and generated files
- Shell events exposed by the Cursor hook surface
- Dependency, MCP and project instruction changes
CodeMarine Dev · Cursor
Independent security around Cursor.
Code and dependency monitoring across Cursor work, with local edit and shell adapters available for setup.
INTEGRATION PROFILE Beta
- Provider
- Cursor local and Background Agents
- Primary transport
- Workspace watcher and Cursor hooks
- 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 local shell and write operations after setup
What you should not assume
- No live canary means active host invocation is not yet proof-backed
- Background Agents run remotely and need a future sidecar or gateway
- Native MCP coverage is expanding
Native controls protect Cursor. 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.
Install the CodeMarine skills for Cursor.
Install the CodeMarine app first, then add the security skills to Cursor. Hooks and MCP can be enabled separately.
codemarine agents install cursor --skillsThe app supplies the scanner. The provider skill or adapter connects it to Cursor.
- 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 Cursor.
Map the current workspace, provider paths and limits before deciding which controls to rely on.
