Session types
Local shells, SSH hosts, and sprites.dev cloud boxes — three kinds of session that look and behave the same inside one workspace.
Muxie gives you one consistent way to work across three kinds of terminal session. They all live in the same workspace, all reattach the same way, and all benefit from durable sessions.
You create any of them from the + New menu (the titlebar button, or the +
on a pane). Local options sit at the top; remote options appear below a
separator once their plugins are enabled.
Local
A local shell on your own machine, started in your home directory. This is the
default session and needs no configuration. Local PTYs run inside the bundled
daemon’s local slot, which is what lets them survive closing the window.
SSH
Connect to a remote host over SSH. The SSH plugin adds a host picker to the + New menu, with quick search, recent hosts, and entries discovered from your SSH config. You can save connections — including credentials, stored through your OS secret store — in the connection manager.
SSH sessions are durable: the remote shell keeps running on the host, and Muxie
auto-reconnects after a network drop. They can also forward ports for previews
and bring remote open/clipboard events back to your machine.
sprites.dev
sprites.dev provides cloud development machines. The Sprites plugin lets you create a new sprite or reattach to an existing one from the + New menu, and manage them (and their forwarded ports) from the Sprites panel. Sprite sessions run over a WebSocket exec channel and reconnect automatically.
Choosing per new tab
If you work mostly locally, you can keep the + New menu fast: the
promptSpriteOnNewTab setting controls whether new tabs prompt you to choose a
session type or go straight to a local shell.
Related
- Workspaces & panes — how sessions are arranged.
- Durable sessions — why remote work survives disconnects.