Sessions
Every agent conversation has a unique session ID that persists across restarts. Claude Yard uses these IDs to track what each session is doing, show your full history, and let you resume any conversation with a click. Both Claude Code and Codex sessions are supported.
Session status
Section titled “Session status”Claude Yard detects session state in real-time by reading terminal escape sequences — no polling required.
| Status | Indicator | Meaning |
|---|---|---|
| Idle | Solid dot | Claude is at the prompt, waiting for input (or session exited cleanly) |
| Running | Animated spinner | Claude is working on a task |
| Waiting | Solid dot (amber) | Claude needs confirmation before continuing |
| Error | X mark | Session exited with an error |
Errors and waiting sessions sort to the top of the sidebar so you can spot them quickly.
The sidebar
Section titled “The sidebar”The right sidebar shows every agent session on your machine — not just ones opened in Claude Yard. It reads Claude session data from ~/.claude/projects/ and Codex session data from ~/.codex/sessions/, merging both with the live state of open terminals.
What you can do from the sidebar:
- Click a closed session to resume it in a new tab (uses the correct agent’s resume command)
- Click an open session to jump to its tab
- See status at a glance — dots show what each session is doing
- Spot unread activity — badges appear on sessions that produced output while you were in another tab
The sidebar refreshes from disk every 10 seconds, so sessions started from the regular CLI show up automatically.
Project grouping
Section titled “Project grouping”Sessions are grouped by the working directory they were started in.
Persistence
Section titled “Persistence”Sessions survive app restarts. Close Claude Yard, reopen it, and the sidebar still has your full history. Terminal tabs themselves don’t persist (the underlying processes exit when the app closes), but resuming a session picks up the full conversation history.