| FMRS | 66 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 15 / 20 | 18 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Development teams that want shared project memory across different AI coding tools.
- Experienced developers who frequently start new sessions and lose context.
- Projects that value preserving design decisions and reasoning.
- Users who prefer local-first, privacy-friendly memory storage.
- Users working with multiple MCP-compatible agents who want a unified memory layer.
| - 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 | - Simple projects that only need single-session memory.
- Users without Node.js or Git environments.
- Teams needing cloud sync or centralized memory management (Memorix is local-first).
- Users needing fully automatic, review-free long-term memory (long-term memory requires manual candidates and approval).
- Beginners who are configuration-sensitive, as setup involves multiple steps.
| - 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 | - Read and write local files (project root and memorix data directory).
- Execute Git commands (e.g., commit history reading).
- Start local HTTP services (if background mode is enabled).
- Optional API keys for LLM generation and embeddings (e.g., OpenAI, OpenRouter).
- Install agent plugins, rules, hooks, and skills (via setup command).
| - 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 | - Local-first means memory is not synced to cloud; you must back it up yourself.
- Misconfigured API keys may send data to third parties; ensure keys are secure.
- Hooks may consume computational resources or impact performance.
- Long-term memory requires human review, otherwise incorrect information may accumulate.
- Orchestration may create multiple worktrees or branches, requiring careful merge conflict resolution.
| - 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, Codex, Cursor, Windsurf, Gemini CLI, GitHub Copilot CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Kiro, OpenCode, Trae | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 20 | 0 |
|---|