Track, spin off, hand off

The session you're in right now is often the work. Tracking makes it official: the session gets an issue — a name, a timeline, a place on the board, a presence on your phone — and stays bound to it for its whole life.

The doors in

• From the pane: type push track inside the session. Bare push track mints an issue from the session; add a title to name it yourself, or a reference to bind to an existing issue.
• From the tab: right-click → Track This Tab.
• From an issue: press Run on an issue and the new session is born tracked.
• From a folder: Track This Folder as an Agent makes a standing bench, so future work in that folder has a home.

Your agent knows these verbs too — the bundled push skill means you can just ask it to track the session, and it will run the same command you would.

What the Run button means

On an issue, one control tells the truth about its session state:

• Run — start a fresh session for this issue (offered on an Active issue).
• Open — focus the bound terminal tab: ● it's live, ◌ it's asleep and will wake.
• Reopen — the issue had a session before; continue that conversation.
• Waiting — a run was accepted; the terminal hasn't opened yet.

Resuming a session reattaches its issue — a session never comes back anonymous.

One session, one issue

A tracked session answers for exactly one issue, permanently. That's what makes the history trustworthy: the issue's timeline is what happened in that session. So when a new topic surfaces mid-conversation — a bug you noticed, a follow-up worth doing — you don't stretch the current issue over it.

Spin off

Spin Off Session… (tab menu, or push spin-off "what it's about" in the pane) mints the follow-up as its own issue: it carries the parent session's context, and both issues reference each other. The original session keeps answering for the original issue; the spin-off starts clean with a head start. Use it the moment you hear yourself say "oh, and also—".

Rerouting

Filed something under the wrong folder agent? Move the issue and the bound session relocates with it — the binding survives the move. Folder identity is explicit in Push: which bench an issue belongs to is a decision, not a guess from wherever the terminal happened to be cd'd.

Unlinking

Unlink Session releases a tab from its issue when a binding was simply wrong. The issue keeps its history; the tab goes back to being an untracked terminal.