Tmux Sessions

Use tmux to keep terminals and TUI agents running when you close Emdash or lose a connection. When you return, Emdash can reattach to the running session.

Enable tmux

Set the app default in Settings, a machine default under Settings → Machines → your machine → System, or an override in Project Settings.

Emdash uses the project override first, then the machine default, then the app default. Changing a setting doesn't move an already-running process into or out of tmux.

Install tmux on the machine running the session and make sure it's on PATH. Local Windows sessions don't use tmux; SSH sessions can use tmux on the remote host.

What persists

Tmux keeps the process and terminal history on the host. Emdash uses readable, identity-backed session names to find the right session when reconnecting.

Closing a view or losing SSH access is different from stopping the process. Tmux does not keep processes alive through a host reboot or protect a session that you explicitly terminate. Chat UI conversation history and provider-specific resume support are separate from tmux.

Inspect a session

Run these commands on the machine hosting the session:

# List sessions
tmux ls

# Attach to a session
tmux attach -t <session-name>

# Stop a session and its processes
tmux kill-session -t <session-name>

Only stop sessions you no longer need. For connection problems, see Connect a Machine.