tmux runtime

This page covers Tallpine's legacy and fallback tmux runtime. New macOS/Linux Terminal UI sessions use a detached native PTY host; existing tmux sessions and native-host startup fallback use tmux. Windows uses ConPTY. Runtime selection is automatic.

The macOS and Linux desktop packages include their own pinned tmux and use an Tallpine-owned socket. Desktop users do not need to install tmux, and Tallpine never shares the machine tmux server.

Standalone daemon and development

Source runs resolve configured or system tmux when needed. macOS still validates tmux before terminal spawn; Linux native-host spawn bypasses that check, although tallpine doctor still probes it:

# macOS
brew install tmux

# Debian / Ubuntu
sudo apt install tmux

Then run tallpine doctor. It reports whether that Tallpine process selected an explicitly configured, packaged, or system tmux. There is no runtime: tmux YAML setting.

Desktop terminal

The desktop xterm surface connects through Tallpine's WebSocket terminal mux. New macOS/Linux Terminal UI sessions use a detached native PTY host; existing tmux sessions and native-host startup fallback use tmux. Windows uses ConPTY. Closing the view does not discard the underlying session. Detached hosts can reconnect after daemon replacement.

There is no project-selectable process runtime. Source installs may need tmux for fallback or old sessions even when a new native-host session succeeds.