Brain · Relationship graph

Relationship graph

See the brain as a graph, not a folder. A force-directed SVG graph of brain cross-references; node size scales with influence score. Graph draws the mode you pick (Brain, Code, Recall or OKF), and the Table view ranks the same brain files by the same influence stats.

Start here if you want to click any decision and see everything it touches: Relationships. Both open from Memory, side by side in the Decisions and errors group.

See it in motion

Where to find it

  • Localhost: /relationship-graph.html?repo=<id>
  • API: GET /api/relationships?repo=<id>
  • Keyboard: ⌘ K then graph
  • Navigation: Memory in the sidebar, then Relationship graph under All tools, in the Decisions and errors group

What it does for you

Hubs are visually obvious.CLAUDE.md, INDEX.md, and decisions.md become the big nodes in the center; tactical files cluster around them. You see the structure of the project's knowledge in one frame.
Orphans drift to the edge.Files with zero references fly off to the corners. If a file is supposed to matter and it is out there, that is a finding: nobody links to it from where it would be read.
Hover a node for its numbers.The tooltip shows the file's category, influence score, tokens influenced, prompt mentions, inbound and outbound links, and PR and session mentions. In Code mode, clicking a node opens the Explain panel for what it depends on and what depends on it.

Configure

Nothing. It is built from the same brain markdown as the Relationships tab. Layout: a hand-rolled force-directed simulation in pure SVG (no D3, no framework). No client-side LLM. The graph draws up to 2,000 brain files per repo, ranked by influence score, and up to 10,000 of the heaviest cross-reference edges between them.

Use it well

Open at the start of a new feature. Find the hub closest to the area you're changing; read it first. After the feature ships, re-open and check whether the new file gravitated toward the center or drifted to the edge.

Read more

Last updated