Multi-agent work loses
context at every handoff.
Without a shared working state
An agent finishes and the next one starts cold — re-reading the repo, scrubbing scrollback, guessing what was decided. Handoffs live in chat and vanish. An auditor flags a real issue and it's lost by the next session. Two agents drift because neither can see what the other did.
With Nodepad
Every handoff, session, audit finding, and architecture decision lands on a shared board as recoverable state — the durable content stays in your repo docs. One where (CLI) or resume (MCP) rebuilds the whole picture for whoever picks up next, human or agent. Nothing to reconstruct.
The decision filter, unchanged: every feature must help answer “Where did we leave off?” — for a team, that means the next agent's first command hands back the full context.
Four flows. Each one recoverable.
The board holds the state and a link; the content lives in your repo (docs/handoffs/, docs/sessions/, docs/analysis/, docs/plans/). Link, don't copy — that split is what makes recovery one command and the truth durable.
One agent passes work to another. The card carries who it's for and where it's stuck — a real state machine, not a lost message.
Every working session leaves a marker and a drill point. Tomorrow's where restores the exact role you were in — not the project root.
An auditor agent files findings tied to a spec's invariants. Each is tracked to resolution and refs the exact rule it checks — no lost review.
The numbered specs as a map. Cards ref each other to show dependencies, so you can see what breaks if a spec changes.
Recovery in, recovery out.
The loop opens and closes on one verb. where loads the context; summarize records it so the next where loads cleanly. A handoff is only real when the receiver's where surfaces it.
Not another memory store.
A workspace you can see.
Plenty of tools persist agent notes to a database. Nodepad puts the same recoverable state on a board your team and your agents both read — with the backlink graph and version history those stores don't give you.
where / resume — handoffs for you, open session, drill point, findingsGET /context.json — no prose parsingStop starting
cold.
Pass the work. Keep the context. The next agent — or you, tomorrow — resumes in one command.