Graphicle vs Zep

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.

Zep

Facts that new data invalidates keep the time they stopped being true. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.

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

Zep

1. Create the user and a thread before adding messages, as the quickstart does
2. Set return_context when adding messages to skip a second round trip
3. Keep episodes short. Every 350 bytes past the first costs another credit
4. Read Retry-After on a 429 and back off with jitter. Free accounts over quota drop to 5 requests a minute
5. Expect a delay after a graph add (202 Accepted) before new facts show up in search