Every agent, by project.

Running opens with one card per project, led by the agent that most needs you. Open one to see its conversations as tabs, with changes, files, a terminal, and its local ports beside them. Approvals and questions from every agent collect in one Review queue.

Version the cache keys so a schema change can't serve stale rows.

Worked for 6mEdited 2 files, ran tests, 18 passed

Keys now include the schema version, so rows from before a schema change rebuild when they are read. I'd like to run the full cache suite once more before I commit.

Codex wants to run a command

npm test -- --grep cache

Allowed onceRunning npm test

Cap the retry backoff at 30 seconds and keep the jitter.

Worked for 3mRead 4 files, edited 1

Editing src/retry/backoff.ts

One queue for everything that waits.

Review gathers agent approvals and questions, teammates' requests, plugin access, Slack approvals, and proposed lessons. High-risk items come first, and Hansard holds each decision for four seconds so you can undo it.

Review

Review1 of 4 reviewedoldest 6m

Allowed once

Claude Code wants to run a commandApprovalHigh risk34m
Your agent asksQuestion6m
Run the cache tests in atlasSlack request2m
Keep migrations behind a dry run firstProposed lesson

Claude Code wants to run a commandrelayBound retry backoffWaiting 34m

High risk

git push --force-with-lease origin fix/backoff

Pushes the rewritten branch after squashing the retry commits.

DenyRSkipS

Your agent asksatlasVersion the cache keysWaiting 6m

Should old cache rows rebuild when they are read, or all at once at startup?

ApproveAAnswer with a noteEDenyR

Watch your agents work as a graph.

Running's overview draws every running agent with its subagents, the tools and MCP servers it calls, and you. Each call pulses along its link, and an agent that waits for you turns amber. Lanes shows the last 30 minutes, turn by turn.

Graph and Lanes

Agent graph

Version the cache keysExploreTest runnerFilesShellWebhansardYou

WorkingNeeds youFailedCallAnswer

Idle agents pause, then pick up where they stopped.

After 65 minutes idle at its prompt, once its prompt cache has expired, an agent pauses and frees its memory. Resume brings it back where it ran. Agents with work, approvals, or subagents keep running.

Automatic pause

6 RunningRecently updated

Version the cache keysRunning npm testnow
Trace a flaky login testEditing src/auth/session.ts1m
Review the worker shutdown pathWaiting at its promptPaused just nowRunning the shutdown tests64m65mnow
Schema migration dry runFinished8m
Idle before a pause
65 min
Only once the agent's prompt cache has expired.
To undo a decision
4 s
Press Z, or select Undo, before it is sent.
Until an item is overdue
30 min
Overdue items get a filter of their own.
Agents side by side
4
Display, Terminals shows up to four at once.

More of Hansard

Put it on the record.

Download Hansard