Why not just tmux?

SAAHT uses tmux as its terminal runtime. tmux provides the pseudo-terminal, process persistence, scrollback buffer, input, resizing, and multi-client control.

SAAHT does not claim those capabilities as its own.

The difference when you connect

A normal tmux attachment starts a tmux client:

tmux attach -t web

The client takes over the terminal screen. tmux then controls scrolling, copy mode, status display, and prefix keybindings. Terminals such as Warp treat the attachment as one interactive program instead of retaining their normal scrollback behavior.

SAAHT connects through a bidirectional stream instead:

saaht connect web

The process still runs in a tmux-backed persistent terminal, but no tmux client takes over your terminal. Warp, iTerm, and similar terminals retain their normal scrolling, selection, copying, and search. Press Enter, then type ~. to disconnect without stopping the session.

What SAAHT adds

• A desktop overview of every managed session and its current status.
• Connection without tmux status bars, prefix keys, or copy mode.
• A private tmux server per session, launched with the environment and sandbox of the caller.
• Stable cursor-based output pages for agents reading a changing terminal incrementally.
• One installation that configures the CLI, desktop app, and background service.

What remains the same

tmux can already keep processes alive, accept input, capture bounded output, use short session names, and allow multiple clients to control one terminal. If you already like the tmux interface and are comfortable managing it directly, you may not need SAAHT.