docs/Features.md

Ref: main worktree-web-client-spec   Size: 1.5 KiB   History

# Features

## State-synced sessions

Detach and reattach without replaying terminal output. The daemon keeps the authoritative Ghostty VT state; clients receive a snapshot and then row deltas.

## Multiple clients

Use the terminal/TUI client (`mux`), browser wall (`mux web`), native client (`muxg`), or `mux a` automation interface with daemon sessions. Terminal and native clients can attach locally, through SSH handoff, over QUIC, or through a `--via` command.

## Session control

Create, browse, and arrange sessions in terminal and native client layouts. Detaching leaves sessions alive. Ending a session and stopping a daemon are explicit actions.

## Agent interface

`mux a` inspects and drives an existing session through JSON replies. It attaches at 0×0, so it does not claim session geometry, and it never offers SSH-agent forwarding.

## SSH-agent forwarding

`mux -A` is opt-in terminal-client behavior. It forwards that terminal client's SSH agent into its attached session; `mux a` does not offer an agent.

## muxg-only TCP loopback forwarding

TCP loopback forwarding is available only in `muxg`. `muxg --forward LOCAL_PORT:REMOTE_PORT TARGET` binds `127.0.0.1:LOCAL_PORT` and forwards TCP to `127.0.0.1:REMOTE_PORT` on the target host. It supports repeated rules, but not hostname destinations, wildcard binds, reverse forwarding, or UDP.

The native picker does not configure forwarding yet. Picker-based forwarding is future work.

## Platform support

Mux publicly supports Linux x86_64 only.