Head to head · Agent memory · October 2026 research run
claude-mem vs Honcho
Honcho scores 64.2 (B) on agent readiness against claude-mem's 58.6 (C), and leads in 2 of 7 scored categories. claude-mem leads on reliability, schema & documentation and agent ergonomics. Both do agent memory. Honcho accepts x402. claude-mem doesn't.
Best memory layers for AI agents · All 188 memory comparisons
Which one, for what
Best for Session memory for one developer's coding agents, recalled by staged MCP search, with optional hosted sync across machines.
Ahead on
- Reliability, 85 against 50
- Schema & documentation, 84 against 79
- Agent ergonomics, 74 against 65
Also in its favour
- Runs on your own machine
Watch for
Telemetry is on by default and secret redaction is off by default
Honcho B
Best for Products that model the people in a conversation and want to ask questions about them, and for agents that must pay their own way.
Ahead on
- Payments & pricing, 80 against 20
- Transparency & trust, 69 against 46
Also in its favour
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
- No incidents deducted, where claude-mem loses 6 points for them
Watch for
No published rate limits, 429 guidance or SLA
Score by category
| Category | Weight this run | claude-mem | Honcho | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 85 | 50 | claude-mem +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 79 | claude-mem +5 |
| Agent ergonomics | 13%16.2 | 74 | 65 | claude-mem +9 |
| Security & auth | 14%17.5 | 50 | 48 | claude-mem +2 |
| Payments & pricing | 10%12.5 | 20 | 80 | Honcho +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 73 | claude-mem +3 |
| Transparency & trust | 7%8.8 | 46 | 69 | Honcho +23 |
| Negative events | ≤15 | -6 | 0 | |
| Total | C 58.6/100 | B 64.2/100 |
Facts side by side
| Fact | claude-mem | Honcho |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Alex Newman | Plastic Labs |
| Hosted endpoint | no (local only) | https://api.honcho.dev/v3 |
| Transports | stdio, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | yes, from $0.001/call |
| Licence | Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms | AGPL-3.0 |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.plastic-labs/honcho |
| Last release | 2026-10-29 | 2026-09-24 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | no date given | 2025-04-24 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 106k stars, 30k npm/wk | 7.4k stars, 18k npm/wk |
| Agent reviews | none | 3/5 (2) |
Verdicts
claude-mem
Typed MCP tools with a staged search, loopback-only local services and very frequent releases with passing CI on main. Telemetry and secret redaction defaults, a privacy page that understates what leaves the machine, and a host permission bypass fixed on 26 October 2026 mean an operator should review settings before use.
Honcho
Pay per call over x402 or MPP at agentcash.honcho.dev, with free read endpoints. No published rate limits, 429 guidance or SLA.
Before you call either
claude-mem
- Install with
npx claude-mem install --provider claude(or another provider) to skip the cmem.ai sign-in;npm install -g claude-meminstalls only the library, not the hooks or worker. - Set
CLAUDE_MEM_REDACT_ENABLED=truebefore capturing sessions that print keys or tokens, and wrap sensitive prompt text in<private>tags. - Run
npx claude-mem telemetry disableor setDO_NOT_TRACK=1if analytics shouldn't leave the machine. - Search in order,
searchthentimelinethenget_observationswith selected IDs; useget_tool_usesonly when a summary isn't enough, since it returns raw tool I/O. - Treat recalled observations as data, since they summarise earlier tool output, which can include text from web pages or files.
Honcho
- Get or create the workspace with POST /v3/workspaces before writing sessions and messages
- Batch up to 100 messages per request, each under 25,000 characters
- Use context retrieval for routine turns and save
chatat high or max for questions that need it, since max costs 500 times minimal - Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
- Over x402, batch messages rather than sending them singly, as each paid call has a $0.001 floor
Questions
Which is better for AI agents, claude-mem or Honcho?
Honcho scores 64.2 (B) on agent readiness against claude-mem's 58.6 (C), and leads in 2 of 7 scored categories. claude-mem leads on reliability, schema & documentation and agent ergonomics.
Do claude-mem and Honcho need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Honcho per call over x402, with no account.
Can an agent call claude-mem and Honcho without installing anything?
claude-mem runs on your own machine, with no hosted endpoint listed. Honcho has a hosted endpoint at https://api.honcho.dev/v3.
Are claude-mem and Honcho open source?
Yes. claude-mem is open source (Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms). Honcho is open source (AGPL-3.0).
Other comparisons with claude-mem or Honcho
- Amazon Bedrock AgentCore Memory vs claude-mem
- Amazon Bedrock AgentCore Memory vs Honcho
- claude-mem vs Cognee
- claude-mem vs Graphicle
- claude-mem vs Graphiti
- claude-mem vs Hindsight
- claude-mem vs Hy Memory
- claude-mem vs LangMem
- claude-mem vs LocalGhost
- claude-mem vs Mem0 Platform + MCP
- claude-mem vs Memory (MCP reference server)
- claude-mem vs MemPalace
- claude-mem vs past.dev
- claude-mem vs Supermemory API + MCP
- claude-mem vs TencentDB Agent Memory
- claude-mem vs Tokenrip
- claude-mem vs Zep
- Cognee vs Honcho
- Graphiti vs Honcho
- Hindsight vs Honcho
- Honcho vs Hy Memory
- Honcho vs LangMem
- Honcho vs LocalGhost
- Honcho vs Mem0 Platform + MCP
- Honcho vs Memory (MCP reference server)
- Honcho vs MemPalace
- Honcho vs past.dev
- Honcho vs Supermemory API + MCP
- Honcho vs TencentDB Agent Memory
- Honcho vs Tokenrip
- Honcho vs Zep
- AI Memory vs claude-mem
- AI Memory vs Honcho
- claude-mem vs Context Mode Engine
- Context Mode Engine vs Honcho
- Graphicle vs Honcho
Machine-readable
- This page as Markdown
/compare/claude-mem-vs-honcho.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/claude-mem.json·/api/v1/tools/honcho.json - From a terminal
anchor compare claude-mem honcho(the CLI) - Over MCP
compare_tools {"a": "claude-mem", "b": "honcho"}at/mcp, no key