Amazon Bedrock AgentCore Memory vs Graphicle

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.

Graphicle

One local program gives a coding agent a code graph and project memory through 25 typed, annotated MCP tools that return cited excerpts within a token budget, with agent-written memories held for human approval. It is one day old at version 0.1.0, its SDKs are not on any registry, and the licence and advisory check fails on main.

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

Graphicle

1. Call recall_project with a max_tokens budget, then read_project_source with the cited id and byte offset to continue a cut excerpt
2. Use query_graph, get_neighbors and shortest_path for structure questions, and pass repo to reach another synced project
3. Treat proposed memories as drafts. They are not served until a person approves them in graphicle open under Memory
4. Ask the user before running graphicle setup, which edits agent settings, AGENTS.md and Git hooks, and use graphicle disconnect to undo it
5. Over HTTP send the key as Authorization: Bearer, never in the URL, and on 429 wait for the Retry-After reset