Skip to main content
Rosie.run Docs

Session Persistence in Rosie SSH

Keep long-running terminal work safe when iOS backgrounds Rosie SSH or mobile networks change.

Coming soon

Rosie SSH is not on the App Store yet and is not in public beta. This page describes the planned behavior.

What happens in the background

iOS may suspend network connections shortly after an app moves to the background. Rosie SSH does not use prohibited background keep-alive modes.

If the SSH connection drops, Rosie SSH can reconnect to the server, but the remote shell process may already be gone unless you used a server-side session tool.

Use tmux

tmux keeps your shell session running on the server.

Start a new session:

bash
tmux new -s work

Run your long command inside tmux. If Rosie SSH disconnects, reconnect and attach again:

bash
tmux attach -t work

Detach without stopping the remote work:

bash
Ctrl-b d

Use mosh when available

mosh can help on mobile networks because it is designed for roaming and intermittent connectivity. It must be installed and configured on the server.

Use tmux for long-running work even when you use mosh.

Reconnect from Rosie SSH

In a terminal session, open the terminal menu and choose Reconnect if the connection looks stale. If the remote process ended, reconnecting starts a fresh shell.

Good habits for long commands

  • Start tmux before package upgrades, compiles, backups, or server maintenance.
  • Avoid leaving important work in a plain shell before locking the device.
  • Save remote files before switching apps for a long time.
  • Expect mobile networks to change between Wi-Fi and cellular.

Device lock

If you enable disconnect-on-lock, Rosie SSH closes SSH sessions when the device locks. That setting is optional. App Lock itself only covers the app UI unless you also turn on disconnect-on-lock.

See the Rosie SSH Privacy Policy for how lock settings are stored.