devpit
A session step starts a Claude Code session for the card in the card's own terminal tab, where you watch it and answer what it asks. It runs in a terminal of the project rather than out of sight, because a session nobody could see would ask its first permission question to nobody.
The form
| Field | What it is |
|---|---|
| Name | what the lane and the runs call it |
| Model | left empty, whatever the account defaults to |
| Account | Default, or one of your profiles |
The session is started with the profile's own command line — the same mode your own sessions run in — and named after the card. A session step wants a checkout of its own, so the card's worktree is made the first time one is needed and the session starts there, on the card's own branch.
Where it runs
The run this step files ends as soon as the session is up, saying "the session is running in the card's terminal tab". The session itself carries on. If the card's tab is already open, it gets a new tab instead of being typed into one that is busy.
On the card, the Sessions section lists it, with Go to terminal beside it, and the card's dot says whether it is working or waiting on you. Several sessions can be going on one project; the island shows them all.
Closing the window does not end it. The terminal it runs in is a tmux pane — see Sessions that outlive the window.
Going on with it later
Once a session is finished or gone, Open as chat on that row carries it on as a chat, with the conversation it already had. It is not offered while the session is still running: two CLIs going on with one session would each write their own continuation of it, and the row says to stop it first.
What it does not tell you
What a session you drove yourself cost is not read back. The CLI writes a transcript and devpit writes down where it is, but nothing reads the totals out of it — so a card says what its runs cost, and is quiet about the rest.