Graphicle
Agent memory goes stale the moment the code it describes changes. Graphicle is one Rust program that gives a coding agent a code graph and project memory together, over MCP. It maps the repository, keeps docs, reviewed decisions and past agent sessions, and returns cited excerpts with exact files and lines. The useful part is the link between the two: a reviewed decision is pinned to the function it describes, and once that function changes, Graphicle withholds the decision instead of serving it as current. It runs locally, with no account and no API key. Created 14 October, it is already at v0.1.18, with 598 stars on GitHub.
What you get
- A code graph and project memory in one program, served to a coding agent over MCP
- Cited excerpts with exact files and lines, so the agent quotes the repo instead of recalling it
- Reviewed decisions pinned to the function they describe, withheld the moment that function changes
- Local only, no account and no API key, Apache-2.0, latest release v0.1.18
Agent memory that cannot tell when the code changed is a liability, not a feature. Pin the decision to the function, and withhold it when the function moves.
Repo: https://github.com/Graphicle-AI/graphicle
Quick poll
What would you use Graphicle for first?
- Giving my coding agent a code graph to search
- Pinning reviewed decisions to the code they describe
- Replacing stale agent memory with repo-grounded memory
- Running it locally on a real repo first
Vote in the comments.
If you found Graphicle interesting, I write about tools like this every week in The AI-Native Engineering Leader, what actually works for engineering leaders building with AI agents, and what to skip.
Top comments (1)
plain markdown for the memory file makes sense. if the agent can read it, so can I, and nothing to migrate later.