Graphicle vs TencentDB Agent Memory

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.

TencentDB Agent Memory

A self-hosted team memory stack with layered recall, per-asset visibility and ACLs, documented HTTP APIs and frequent releases, 2.0.0 to 2.0.3 since August. The default deployment publishes its ports on all host interfaces with the core's bearer gate off, data-plane deletes trust a service-ID header, and the proxy's rate-limit and session admin routes have no authentication.

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

TencentDB Agent Memory

1. Set MEMORY_CORE_GATEWAY_API_KEY, KNOWLEDGE_SERVICE_KEY and a non-default admin key before exposing ports 8420, 8424, 8096 or 8125 beyond the host
2. In headless runs send x-team-id, x-agent-id and x-task-id headers to the proxy. Without all three it falls back to an interactive picker and skips memory
3. Expect every proxied turn to be stored. The proxy records upstream messages and model replies to Memory Core, and injected memory lands in your system prompt
4. Check data.valid on /v3/meta/auth/verify and data.isError on /v3/tools/call. Both can fail inside a success envelope
5. Retry /v3/session/add only on 500, 503 or a network error. The API reference says it isn't idempotent and writes a new object each call