/tmux is the primary working surface for live tmux panes in Agent Commander.
It is built for the normal workflow of keeping several tmux windows open across one or more machines and jumping directly into the pane you want, without forcing every action through the broader sessions or orchestrator views.
- Hosts with tmux capability and current online state
- Tmux sessions grouped into windows
- Panes nested under each window
- Repo, branch, provider, cwd, and activity context for each pane
- An inline workbench for the selected pane
The original sessions and orchestrator pages are useful operator views, but they mix together several concepts:
- tmux panes
- background jobs
- approvals and attention queues
- automation and governance
/tmux strips that down to the workflow most operators actually live in: pick a host, pick a tmux window, and work directly in the pane.
- Open
/tmux. - Select a host from the roster.
- Choose the tmux session/window you want.
- Open the target pane in the inline workbench.
- Use the embedded terminal controls, send input, idle/wake, or terminate actions without leaving the page.
/tmuxis the primary tmux workflow./sessionsis the broader inventory view across tmux panes, jobs, and services./sessions/[id]is the standalone session detail route./orchestratorstays focused on waiting-for-input, approvals, and errors./automationstays focused on orchestrators, workers, wakeups, runs, and governance.
- The tmux manager reuses the existing session and terminal runtime.
- It does not introduce a second tmux backend model.
- It does not replace
/sessions; it simplifies the common workflow. - It shows unmanaged panes automatically when they are already present in the session registry.
The tmux manager is intentionally read/write for pane work, not a full tmux administration surface. It does not yet add tmux-native rename/split/move controls beyond the session actions Agent Commander already supports.