devpit
An orchestrator works through sessions: Claude Code sessions of its own account, each in a terminal you can watch. This page is about the panel that shows them and what passes between them and the orchestrator.
The Sessions panel
The orchestrator's right panel opens on Sessions, and the chat's corner counts them — 3 sessions · 1 waiting — and opens it.
- Sessions are grouped by project. Every linked project is listed, with a session or without; its header opens a new terminal right over the chat, or a new chat in the project.
- In each group, the ones waiting on you come first, then the busy ones. A row says how long it has been at it and what it is on — Edit invoice.ts, Run npm test — or what it was last asked.
- Earlier · not running keeps the sessions that ended, with their history.
Open a row for its question, a reply field, and everything that passed between it and the orchestrator. From there:
| Action | What it does |
|---|---|
| Open its terminal here | the session's terminal over the chat, to work in as you |
| Go to it | its project and its tab |
| Watch it in a terminal | for a session running in the background, attaches it in a tab of its project |
| Remote Control | types /remote-control into its terminal, so it can be reached from claude.ai and the Claude app |
| Stop session… | ends it and closes its terminal — work in flight is lost, so it asks first |
The session's window
The terminal opened over the chat resizes from its edges and corners and remembers its size. Its header shows the branch, how far it is ahead or behind, and whether it runs in its own checkout or the project's folder. Changes, folded until you open it, holds the uncommitted files, the commits on its base and the diff. Click the name, or press F2, to rename it; that goes through the CLI's own /rename. Hiding the window keeps the session running; Close terminal… ends it.
Answering a waiting session
A session stopped on a question — a permission, a choice Claude asked for — shows under Waiting on you, both in the panel and above the composer, with its choices as buttons. A click answers it in that session's own terminal, as you; Esc dismisses it; Open terminal answers it there instead. Nothing is pressed unless the screen still shows exactly the question you clicked on, so a late or double click never answers the next one.
The orchestrator can read the question and recommend a choice. Only you answer it.
Handing a card's work to a session
Asked to, the orchestrator starts a new session of its account on a card: in the card's own checkout, or in the project's folder if you choose — it is told to ask which. The session opens in the card's terminal tab with your profile's own command, linked to the card, named after it, and on the board like any other; the card moves to the lane for work in progress, never into one that runs a step. If the folder is one Claude Code has not trusted yet, the trust question waits under Waiting on you before the session is even up.
It can also start a session in any linked project with no card at all, in a new terminal tab of its folder.
Hearing back
What its sessions did since your last message — one finished its turn, one is waiting on a question, one ended — is told to it at the start of your next one. It is not woken to say so.
A session that writes back to it, or a notice it asked for when a session went idle, does wake it, and its answer appears in the chat marked as not in answer to you, quoting who wrote. Each message it sends a session shows as a card: to whom, what was asked, and how that session stands now.
Replies you send as yourself
A "go on", or a change of plan said in its chat, can be drafted for a session rather than sent. The draft waits, editable, under Drafted for you to send — above the composer and in the panel. Send as you types it into that session's terminal as your own words; Drop throws it away. Nothing is sent without your click, and nothing is sent to a session stopped on a question: answer that first. Drafts are not kept across a restart of devpit.