Preview: Switch, Create, and Detach Nash Sessions
This preview of Nash 0.13.7 looks at the new session switcher. It brings everyday workspace management into one dropdown: find a project, start a named session, or reconnect to work on an SSH host.
Find the Workspace You Need
In 0.13.7, click the session badge at the right end of the tab bar or press
SUPER+Shift+S (CMD+Shift+S on macOS). The switcher lists sessions by name,
marks the current one, and labels sessions with their SSH hosts. Without a
badge, it opens at the top of the panes instead.
Type to filter, use Up and Down to select, then press Enter to show the
session in this window. While the switcher is open, SUPER+1 through SUPER+9
jump to the numbered sessions. Escape closes it.
An unmatched name offers Create “name”, so starting a workspace called
release-review needs no separate dialog. New Session, also bound to
SUPER+Shift+N, generates a name instead. Rename Session… changes the name
of the session this window shows.
Bring an SSH Session into View
Choose Connect to SSH Host… and enter a destination followed by an optional session name:
max@devbox workThe destination accepts [user@]host[:port], including aliases from
~/.ssh/config. The list includes configured hosts and hosts used since Nash
started. Without a session name, Nash uses [mux].default_session.
Nash logs in, starts the remote mux server if needed, and creates the named
session if it is missing. The host needs Nash installed so it can run
nash cli proxy. Use distinct session names when you want local and remote work
kept apart: matching names share one workspace view.
Detach Is Not Close
Update for Nash 0.13.11: the selected noncurrent session now has separate
Kill and Detach buttons at the right of its row. × means Kill and
opens a confirmation dialog listing running programs and the number of panes
that will close. Use Detach or SUPER+D to keep mux programs running;
SUPER+Backspace keeps its two-step keyboard confirmation for killing. The
current session has no row buttons, and only eligible mux sessions offer Detach.
The description below refers to the original 0.13.7 interface.
In 0.13.7, the × in a noncurrent session's left gutter asks to Detach. It hides that session only in this GUI, across every attached client domain contributing its panes. Processes keep running; other sessions and attached GUIs are unchanged. The button appears only when all panes belong to attached Unix, TLS, or multiplexing SSH client domains—not for local or ineligible mixed sessions, or the current session.
That exclusion lasts for this GUI process, unless you explicitly reconnect.
Restarting Nash forgets it. By contrast, SUPER+Backspace asks to close the
selected session and end every pane's processes. Treat that confirmation as
destructive, not as another way to hide work.
Choose the Lifetime You Want
New configurations in 0.13.7 will enable mux mode by default. An update
preserves an existing explicit enabled = false; opt in through nash.toml:
[mux]
enabled = true
domain = "mux"
default_session = "default"
connect_automatically = trueOnly server-owned panes survive quitting Nash. Session commands also organize local workspaces, but naming one does not make its processes durable. If the server cannot attach at startup, Nash falls back to local panes and uses the local domain by default until restart; those panes end when Nash quits.
See Multiplexer Sessions for session lifetimes and Multiplexer Commands for CLI workflows.