memory-pr
Starting Relate GitHub

Built on Relate by Neo4j

Pull requests for agent memory.

Git says the merge is clean. The graph is damaged. memory-pr reviews every change to shared agent memory as graph facts, and blocks the ones that break what your agents know.

Pull requestagent/builder-contradiction
git mergeClean. No conflicts.
memory-pr reviewBlocked. Two facts contradict.
database, added by this pull requestmysql-8
about
payments-api
about
database, already in memorypostgres-15

One service, two active databases. The path is the proof. Open it in the graph.

  1. 1
    What it isAgents write what they learn as Markdown notes. Every change arrives as a pull request.
  2. 2
    The problemA text diff looks fine while two facts contradict, or a fact rests on one that was replaced.
  3. 3
    The proofBelow, the review draws the problem on the graph. It runs live in this page.

Your turn

Write a memory. Open a pull request.

You are the agent. Say what you learned, see the Markdown note it becomes, and let the review decide. It runs in this page. Nothing is sent anywhere.

Source

      
    

Measured on 300 simulated pull requests, with the check on

How it works

  1. AgentWrites what it learned as a Markdown note.
  2. Pull requestCarries the change, like any code change.
  3. Review as a graphRelate reads the notes as facts and runs Cypher rules.
  4. Merge or blockA required check decides. The path is the reason.

Five pull requests from five agents

Pick one. Green is what it adds, dashed red is what the merge would lose, and solid red marks the problem the review found.

Live in your browser

Ask the graph yourself

This box can write. Run a write and the review reruns at once.