Muxie Get Muxie
Getting started Tutorial

Quick start

Open Muxie, create a terminal, split a pane, and prove durability by reattaching to a session that survives a restart.

This is a ten-minute tour. By the end you’ll have a workspace with a couple of panes, and you’ll have watched a session survive closing the window — the thing that makes Muxie different.

1. Open Muxie

On first launch, Muxie greets you with a Welcome pane: the mascot, a few quick-start tips, and a “Make it yours” section where you can pick a theme, font, and which optional features to turn on. You can reopen it any time from the command palette (open-welcome).

You start in a single workspace with one local terminal pane.

2. Create a terminal

Press Ctrl+T (or click + New) to open the new-tab menu. Choose Terminal for a local shell. The shell starts in your home directory.

Tip: The same + New menu is where you reach Browser, SSH…, and Sprite… sessions. The remote options appear once the SSH and Sprites plugins are enabled — see the Welcome quick start or Settings → Plugins.

3. Split the pane

Run something long-lived in this pane — a dev server, a watch task, or just top. Then split the view so you can work alongside it:

  • Ctrl+Shift+O splits right
  • Ctrl+Shift+E splits down

Move focus between panes with Alt + the arrow keys. Press Ctrl+Shift+Enter to zoom the focused pane to fill the workspace, and again to restore the split. Ctrl+Shift+= equalizes split sizes.

Each pane can also hold several pane-tabs — stacked terminals or browser surfaces, only one visible at a time. Cycle them with Ctrl+Shift+] and Ctrl+Shift+[.

4. Organize with workspaces

The left rail lists your workspaces (called Groups). Create a new one, rename it, and drag sessions between workspaces to keep unrelated work apart. Hover a workspace card to get its flyout — a quick list of every session inside it, with live status.

Toggle the rail with Ctrl+B, and the file explorer on the right with Ctrl+Shift+B.

5. Prove it’s durable

This is the part that matters. With a process still running in a pane (your dev server or top), close the Muxie window.

Now reopen Muxie. Your workspace comes back, the pane reattaches to the same session, and your scrollback is intact — the process never stopped. It was running inside the bundled daemon the whole time, not inside the window.

Note: This works the same for SSH and sprites.dev sessions: a dropped connection triggers an automatic reconnect, and the remote session keeps running on the host. Read why in Durable sessions.

6. Find your way around

  • Command palette — Ctrl+P (or Ctrl+Shift+P). Fuzzy-search every action: new tab, split, find, settings, and plugin commands. When in doubt, open the palette.
  • Settings — Ctrl+,. Theme, fonts, terminal engine, keybindings, notifications, plugins, and more. See the Settings reference.
  • Find in terminal — Ctrl+F. Search all panes with Ctrl+Shift+F.

Next

Put it to work: Run a coding agent and watch Muxie track its status across panes.