Use Memory when you want to know why something is the way it is, what an agent learned in an earlier session, or which facts are tied to code that still exists.
Before you start
- A Graphify account at app.graphify.com.
- An indexed repository.
- A coding agent connected through the hosted MCP. Memories are written by agents, so a new repository has none.
How it works
1
Agents record
Connected agents write memories over MCP or the HTTP endpoint. Memories are scoped to your workspace.
2
Distil
A model turns raw memories into candidate facts.
3
Merge by rule
Duplicates fold by rule, never by model, so merging is deterministic.
4
Anchor
Each fact is anchored to the code entity it describes when one resolves. Provenance and anchors survive merging.
Explore memory
1
Open Memory
Open Memory in the Console and choose a Repository.
2
Recall
Use Recall a fact, entity, or anchor to search, or pick from Memory entities.
3
Inspect a fact
Read the Remembered facts for an entity, with their source turns and the graph node they’re anchored to.
Grounded and ungrounded facts
A fact is grounded when it’s anchored to a code node that still resolves. Ungrounded facts are normal, not errors: a decision about process, or about code since deleted, has nothing to anchor to. A remembered fact and an extracted code relationship are different kinds of evidence. For the current behavior, follow the anchor to Graph explorer and read the code. Explicit instructions and human decisions take precedence over anything inferred.How Memory fits with your agent’s own memory
Your agent can keep its own preferences and session notes. Graphify adds shared knowledge tied to your repositories that other agents and teammates in the workspace can inspect. Graphify doesn’t sync with or replace another memory store.Add a memory
1
Write it
Write one fact your team should keep. For example: Retry failed card charges at most three times, and never retry hard declines.
2
Give it a topic
Add a short topic, such as Payment retry policy, so related memories stay together. Graphify suggests one from your text, and you can change it.
3
Save
Select Save and keep. The Console shows Kept. Graphify is processing it. Memories are attributed to you. Your GitHub files aren’t changed.
Suggestions and kept memories
Graphify also picks up memories from recent conversations and from AI agents. These start as suggestions. Ask only uses a suggestion after someone keeps it. Connected agents may already see it, marked as unverified.
Keep a suggestion as it is, edit it and keep it, or discard it. If the code a memory refers to changes after it was saved, the memory is flagged: “The code this refers to changed after it was saved. Check that it is still true.” When two current versions disagree, Ask and agents use neither until you edit one to say which is right.
Remove and restore
Removing a memory means Ask and agents stop using it. Its history is kept, and you can restore it.Ask what your team knows
Search memory with plain words to find saved decisions, incidents and lessons. Turn on Only linked to code to see only memories anchored to code, or turn on Include suggestions not yet kept or Include what was said in conversations to search more widely. Ask answers each question on its own, so name what you mean in follow-ups.Verify and troubleshoot
Who can see memories?
Who can see memories?
Memories are scoped to the workspace they were written in. Workspace access controls apply.
Is there a local equivalent?
Is there a local equivalent?
Open-source Graphify keeps work memory in your repository. See Work memory.
Does saving a memory change my repository?
Does saving a memory change my repository?
No. Memories are stored in Graphify and attributed to you. Your GitHub files aren’t changed.
What’s next
Hosted MCP
Connect the agents that write memory.
Learning
How review feedback tunes reviews.
Connect your agent
Add the hosted MCP at
api.graphify.com/mcp. Sign in with OAuth, no API key.