Back to all features
Session continuity

tmux continuity

Create or resume persistent tmux sessions without memorizing commands. Agents and long-running jobs keep going after Redock disconnects.

feature demo videotmux continuity

Create or resume persistent tmux sessions without memorizing commands. Agents and long-running jobs keep going after Redock disconnects.

Overview

tmux keeps terminal programs inside a server-side session. A phone network change, app suspension, or closed SSH client detaches the outside terminal without necessarily stopping the programs running in the tmux session.

After tmux is enabled for a Host, Redock can create or reopen sessions for Hosts, Projects, and Actions without requiring hand-written tmux commands. Background tasks use remote tmux sessions so saved logs remain available and the live session can be entered when supported.

When to use it

  • Let a coding agent work for tens of minutes or hours while you lock the phone, switch apps, or move between networks.
  • Keep builds, full test suites, migrations, data jobs, and deployment scripts alive beyond the lifetime of one SSH connection.
  • Run a dev server or log follower continuously, then reattach later to inspect the same terminal output and state.
  • Maintain separate named sessions for implementation, tests, services, or production diagnostics on one Host.
  • Recover the exact interactive terminal after an interruption instead of starting a new shell and rebuilding context.

Let an agent work while you leave

Start a long implementation in a named tmux session, lock the phone, and return later to the same conversation, terminal state, and output instead of starting a new agent session.

Protect a long-running server or log view

Keep a dev server, build watcher, tail command, or REPL inside tmux so a brief mobile-network interruption does not terminate the process you are observing.

Maintain parallel work surfaces

Use separately named sessions for agent implementation, tests, service logs, and production diagnostics. Each can be restored independently without mixing unrelated terminal state.

How it works

  1. Install tmux on the remote Host and enable tmux support.
  2. Create or attach a session from Redock instead of memorizing tmux commands.
  3. Leave safely and reopen the same session from Project or Activity.

Practical guidance

tmux preserves the process on the Host; Mosh improves the live connection on unstable networks. Use them together when you need both continuity and smoother roaming.

Put this feature into your mobile workflow

Steer coding agent and work on your phone.

Get Redock Free