Evidence CodeMarine can inspect
- Resulting workspace code and configuration
- Dependencies, skills and MCP configuration added to the project
CodeMarine Dev · Grok
Independent security around Grok.
A provider adapter exists. Managed installation and verified protection are still being completed.
INTEGRATION PROFILE Planned
- Provider
- Grok
- Primary transport
- Workspace watcher and adapter assets
- 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
- The adapter can evaluate supported write and shell events when manually configured
What you should not assume
- The adapter is not a complete managed installation yet
- No live host proof is available
- Server-side remote MCP needs a governed gateway
Native controls protect Grok. 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.
Add the CodeMarine security skill to Grok.
The Grok skill is distributed through the early access integration bundle. Install the CodeMarine app, then request the Grok setup package.
The app supplies the scanner. The provider skill or adapter connects it to Grok.
- 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 Grok.
Map the current workspace, provider paths and limits before deciding which controls to rely on.
