Shared Memory
Chats that share what they learn.
Multiple Claude Code chats on one project stop re-deriving each other's work. One records a finding — a decision, a gotcha, an API shape — and the rest recall it, injected automatically. One command turns it all on.
Record once, recall everywhere
A shared pool stores facts (decision · gotcha · API shape · warning · todo). The next chat's relevant prompt gets them injected automatically — treat as known, don't re-derive.
Rides the code graph
Recall follows callers and callees: a fact about a function surfaces when you touch what calls it, not only on a literal keyword hit.
Scope & expiry
Facts can be private to one chat or shared project-wide, and can carry a shelf life — so a temporary workaround or a value that changed never misleads later.
One command, one panel
sentinel-suite start wires the context hook, graph, router, and pool, then opens a control panel showing tokens saved, expert routes, and shared facts in one view.
- Re-reads the same files
- Re-derives the same facts
- Burns the tokens twice
- A finding is recorded once
- Every chat recalls it, auto-injected
- Recall rides the code graph
Shared memory turns duplicated work into reuse.