Reconnect a closed session

When the remote closes an SSH channel (you typed exit / logout, the device rebooted, your VPN dropped), Transit AI keeps the tab around with the final scrollback visible and a “session ended” banner at the bottom. You can reconnect in place without losing the tab slot.

Steps

1. Click the pane (so it takes keyboard focus).
2. Press Enter.

Transit AI:

1. Best-effort disconnects the dead backend session (so the AI’s list of open sessions stays accurate).
2. Opens a fresh SSH session to the same device using the same auth profile.
3. Swaps the new session ID into the same tab slot. Your custom tab label (if you renamed it) and any split-pane anchor are preserved.

The pane clears and you see the new shell’s welcome banner. The amber “session ended” banner disappears.

When reconnect fails

A reconnect can fail for the same reasons a first connect can — authentication, networking, host-key mismatch. Failures pop a toast in the bottom-right with the reason; the dead pane stays in place so you can retry by pressing Enter again, or close it manually.

Mass reconnect after a network blip

There’s no “reconnect everything” button in v1. Each tab needs an individual Enter. Auto-reconnect-on-blip is on the roadmap.

Why not just open a new tab?

You can — right-click the device in the sidebar and Connect again, and the dead tab can be closed manually. Press-Enter reconnect saves a click and preserves tab order, which matters when you’ve laid out multiple panes deliberately.