| FMRS | 73 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 15 / 20 | 18 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 |
|---|
| Documentation | 18 / 20 | 18 / 20 |
|---|
| Setup experience | 15 / 20 | 15 / 20 |
|---|
| Best for | - Developers on long-running projects using Claude Code, Cursor, Windsurf, or similar tools
- Teams needing cross-session memory and codebase understanding
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Users unwilling to index code to a cloud service
- One-off scripts that need no persistent context
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Requires a ContextStream API key (secret env var)
- Reads and indexes project code files
- Optionally connects GitHub, Slack, and Notion integrations
- Writes MCP configs, rules, and lifecycle hooks into editor settings
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - Indexed code is stored in ContextStream's cloud (vendor states isolation per workspace)
- A leaked API key could expose workspace data
- Breaking changes with @modelcontextprotocol/sdk 1.28.0+
- Hosted HTTP OAuth may be blocked on corporate networks
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Claude Code, Cursor, Windsurf, Cline, Roo Code, VS Code + GitHub Copilot, Kilo Code, Codex, OpenCode, Aider, Antigravity, Claude Desktop | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 17 | 0 |
|---|