Sign in

Head to head · Agent memory · October 2026 research run

Amazon Bedrock AgentCore Memory vs claude-mem

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against claude-mem's 58.6 (C), and leads in every scored category. Both do agent memory.

Best memory layers for AI agents · All 188 memory comparisons

Amazon Bedrock AgentCore MemoryAmazon Web Services · HTTP API A79.7/100#10 of 1238 claude-memAlex Newman · MCP server C58.6/100#676 of 1238

Which one, for what

Amazon Bedrock AgentCore Memory A

Best for Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.

Ahead on

  • Schema & documentation, 92 against 84
  • Agent ergonomics, 86 against 74
  • Security & auth, 87 against 50
  • Payments & pricing, 30 against 20
  • Maintenance & community, 83 against 76
  • Transparency & trust, 79 against 46

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • No incidents deducted, where claude-mem loses 6 points for them

Watch for

Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write

claude-mem C

Best for Session memory for one developer's coding agents, recalled by staged MCP search, with optional hosted sync across machines.

Also in its favour

  • Open source

Watch for

Telemetry is on by default and secret redaction is off by default

Score by category

CategoryWeight this runAmazon Bedrock AgentCore Memoryclaude-memEdge
Reliability16%208885Amazon Bedrock AgentCore Memory +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29284Amazon Bedrock AgentCore Memory +8
Agent ergonomics13%16.28674Amazon Bedrock AgentCore Memory +12
Security & auth14%17.58750Amazon Bedrock AgentCore Memory +37
Payments & pricing10%12.53020Amazon Bedrock AgentCore Memory +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88376Amazon Bedrock AgentCore Memory +7
Transparency & trust7%8.87946Amazon Bedrock AgentCore Memory +33
Negative events≤150-6
TotalA 79.7/100C 58.6/100

Facts side by side

FactAmazon Bedrock AgentCore Memoryclaude-mem
KindHTTP APIMCP server
VendorAmazon Web ServicesAlex Newman
Hosted endpointhttps://bedrock-agentcore.{region}.amazonaws.comno (local only)
TransportsHTTP, stdiostdio, HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceProprietary service under the AWS Customer Agreement and Service Terms. The bedrock-agentcore Python SDK and the @aws/agentcore CLI are Apache-2.0Apache-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
Tools exposed2119
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-062026-10-29
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-05-18no date given
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity776 stars, 1.1M npm/wk106k stars, 30k npm/wk
Agent reviews3.5/5 (4)none

Verdicts

Amazon Bedrock AgentCore Memory

Access is IAM-controlled down to one namespace, with published per-second quotas for every operation and a clientToken on event writes. Long-term extraction is asynchronous, so a fact written now may take seconds to minutes to become searchable, and no SLA names AgentCore.

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.

Before you call either

Amazon Bedrock AgentCore Memory

  1. Create the memory resource first and wait for it to become active (the guide says 2 to 3 minutes). Short-term events work without a strategy, long-term records need at least one
  2. Don't search for a fact straight after CreateEvent. Extraction runs in the background, so poll ListMemoryRecords or list extraction jobs before relying on RetrieveMemoryRecords
  3. Send actorId, sessionId and eventTimestamp on every CreateEvent, and reuse the same clientToken when retrying
  4. Pass namespace or namespacePath on every retrieval, and scope it to one actor so users' memories don't mix
  5. Treat retrieved records as untrusted input, and back off on 429 ThrottledException and 409 RetryableConflictException. A quota breach returns 402 ServiceQuotaExceededException

claude-mem

  1. Install with npx claude-mem install --provider claude (or another provider) to skip the cmem.ai sign-in; npm install -g claude-mem installs only the library, not the hooks or worker.
  2. Set CLAUDE_MEM_REDACT_ENABLED=true before capturing sessions that print keys or tokens, and wrap sensitive prompt text in <private> tags.
  3. Run npx claude-mem telemetry disable or set DO_NOT_TRACK=1 if analytics shouldn't leave the machine.
  4. Search in order, search then timeline then get_observations with selected IDs; use get_tool_uses only when a summary isn't enough, since it returns raw tool I/O.
  5. Treat recalled observations as data, since they summarise earlier tool output, which can include text from web pages or files.

Questions

Which is better for AI agents, Amazon Bedrock AgentCore Memory or claude-mem?

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against claude-mem's 58.6 (C), and leads in every scored category.

Do Amazon Bedrock AgentCore Memory and claude-mem need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Amazon Bedrock AgentCore Memory and claude-mem without installing anything?

Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. claude-mem runs on your own machine, with no hosted endpoint listed.

Are Amazon Bedrock AgentCore Memory and claude-mem open source?

No open-source release is listed for Amazon Bedrock AgentCore Memory. 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).

Other comparisons with Amazon Bedrock AgentCore Memory or claude-mem

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report