Keep sessions alive, and come back in one tap

Choose how long the app holds your sessions, let a dropped tab reopen itself with your command, and use the home carousel.

4 min read

Step by step

Choose how long sessions stay in the background
Pick Always keep, 15 minutes, 1 hour, 4 hours or Close when hidden. If the phone ends a long background stretch, the session waits for you as a card, just as it was.
Where: SettingsSession & batteryKeep session in background
Give the host a startup command
In the host editor, Command on shell open takes up to 12 lines that the app types into every new shell — cd into a project, start your multiplexer, launch an agent.
Where: HostCommand on shell open
Recognise a dropped tab
A drop is noticed right away. The tab turns into a card that keeps its place, its size and the command it started with.
Tap to come back
Tap the card and the app opens a fresh shell, then types that command again. It never dials on its own in the background — you decide when.
Use the carousel
The home screen shows every session as a card with a live thumbnail of its terminal. Live, Files, Dormant and Connecting cards sit side by side, so you see what each one is doing before you open it.

A drop ends the old shell and its scrollback. To keep a long job and its output alive through drops, run it under tmux or Herdr on the host and put that in Command on shell open: reconnecting then lands you back in it.
Keep screen on in Settings › Session & battery stops the screen from sleeping while the app is open, at the cost of battery.
Swiped the app away from Recents? Your session cards are still there next time.

Keeping sessions in the background: Android only today. On iPhone the session closes when the app leaves the screen.