Sessions: bring terminals back after a relaunch

When SHIPIT starts again it lists the terminals that were running last time, grouped by workspace. Each one says what will happen.

Resume conversation: the agent returns to the same conversation. Conversation unavailable: no saved conversation was found, so it cannot be resumed. Reopen terminal: a plain shell simply opens in its folder.

The checkboxes decide what is restored. Deselect all clears every tick, Select all puts them back.

Restore all starts everything on the list, Restore selected only the ticked rows. Skip leaves the terminals stopped: start them later from Sessions or from the pane menu.

If only plain shells without a conversation were open last time, the window does not appear and they come back on their own.

TipSleeping panes are not listed here: they stay asleep until you press the button on the pane itself.

At the bottom of the Code sidebar there is a Sessions row; the number next to it counts the closed terminals waiting there. The same window opens with ⌘Y and with Sessions… in the workspace menu.

Everything is one list: first stopped terminals that can resume in place, then closed terminals, then closed workspaces. The field at the top filters by title, folder or workspace, and the saved conversation shows on the right.

The button at the bottom follows the row: Resume for a saved conversation, Start for a pane without one, Reopen for a closed one. Return presses it.

TipThe three-dot button at the bottom holds Resume all not running and Clear closed.

In Settings › Panes & sessions the switch Restore last workspace takes you back to the project you had open last. A closed workspace is not deleted either: it waits in Sessions with its panes, layout and conversations.

⇧⌘T reopens the last closed terminal at once.