Head to head
claude-mem vs repomix
claude-mem and repomix solve the same job (Memory & context), so this is a pick-one decision.
| Field | claude-memgithub.com Not yet swept | repomixgithub.com Not yet swept |
|---|---|---|
| What it is | Captures what the agent does via hooks, compresses events into semantic summaries, stores them in SQLite with FTS5 plus a Chroma vector DB, and injects the relevant slice into future sessions. Progressive disclosure: search returns a ~50–100 token index before you fetch detail. ~91k stars. | Packs an entire repository into one AI-consumable file (XML, Markdown, JSON or text) with directory tree, contents and per-file token counts. Tree-sitter compression strips implementation bodies to signatures for ~70% token reduction. Honors .gitignore; Secretlint scans for credentials before output. |
| Category | Memory & context | Memory & context |
| Cost tier | free | free |
| Pricing | Free · Apache-2.0 | Free · MIT |
| Why builders pick it | Runs with no intervention after install, which is why it beats a manual notes file. Content wrapped in <private> tags is excluded from storage. | A one-shot context packer, not persistent memory — the right tool when you want to hand the whole project codebase to a model in a single message, or audit what is actually in there. The secret scan before output is a genuinely good safety default. |
| Watch out for | not logged | not logged |
| How to wire it up | npx claude-mem install | npx repomix@latest |
| Editor's pick | Yes | Yes |
Other matchups worth running
Agent endpoint: GET /api/public/compare?slugs=claude-mem,repomix