Run your coding agents together.
Know which ones need you.

See who is working, waiting for approval, or blocked. Notifications name the session and the reason, so you can respond without watching every pane.

Choose a sound and push notification for each event. Set quiet hours and separate Desktop and Mobile preferences. The alert history stays readable when delivery is muted. Status and alerts

Use the terminal, review changes, edit files and respond to agents from the same workspace. Mobile has its own touch controls and layout, with your desktop arrangement kept intact.

Connect your phone. HTTPS enables microphone and clipboard APIs; push also needs browser permission.

Dictate a prompt, hear an agent reply, or ask which sessions need your attention. Voice works from desktop and phone, with separate controls for listening and playback.

• DictationSpeak into a draft and send it to an agent or text surface. Speech recognition runs on your host machine.
• Read aloudListen to replies or spoken summaries. Choose which sessions generate speech and which device plays it.
• The assistantAsk about your sessions and navigate by name. Actions follow the trust settings you choose; consequential actions require confirmation.

Voice is optional. Speech models download when requested. The assistant uses a configured model endpoint and your budget; experimental Edge speech is a separate opt-in. Voice setup

Use familiar shortcuts across supported agent inputs. Shift+Enter inserts a new line, Ctrl+Backspace deletes a word, and clicking positions the cursor in recognized composers.

• Your keymapChoose swe-mux, tmux, VS Code, Vim or Emacs shortcuts for workspace navigation. Try a preset in the desktop demo toolbar.
• Image pastePaste a screenshot from your clipboard into an agent that supports image attachments. You can also attach a file.
• Shared clipboard historyReuse text copied inside swe-mux from desktop or phone. Pin entries and optionally retain history across restarts.

Workspace keymaps and agent text editing are separate features. Browser-reserved shortcuts and individual CLI capabilities still apply. Clipboard history records in-app text copies; it does not synchronize the system clipboard. Keyboard reference

Split agents, notes, files and previews into panes, with tabs inside each. Keep the code, conversation and running result in view together.

Run any shell, TUI or CLI in a real terminal. Recognized agents add status, transcripts and input support. The Markdown editor supports tables, code blocks and sending a selection to an agent. Workspace guide

Sessions can exchange messages, read each other's progress and request help within the permissions you set. See who asked, what they requested and where the response went.

Messages can wait in a session's queue until it is ready. Spawn and control requests require approval by default. Project permissions govern what agents can read and do. Queues and communication

A branch takes its turn in the queue, updates from master, and runs the checks you approved. Passed checks allow a fast-forward; a conflict or failed check stops the request.

A failed request returns to the agent that owns the branch. An agent cannot approve its own verification command. Enable the required Project permissions before allowing agents to request landing. Try the failed-check walkthrough · Git and landing

Search conversations across agent CLIs, reopen the transcript, and inspect the commands, changes and test results that were recorded. Resume earlier work with its context close at hand.

Optional evidence capture records observed tool activity and attributes commits to contributing sessions. It reports missing evidence rather than treating it as proof of success. History and auditing

A separate supervisor holds the terminals while the daemon restarts or the app updates. Reconnect to the working sessions and their scrollback.

The supervisor cannot survive its own death or a power loss. Cold recovery restores affected sessions as readable, resumable records. Session recovery

• Local dataProjects, history and settings live on your machine. No swe-mux account or usage telemetry.
• Your providersAgent CLIs use your existing subscriptions. Optional model features use your endpoint and budget.
• Optional automationEvidence capture, attention analysis and agent control have explicit Project permissions. Start with the workspace and enable what you use.

The update check fetches a static version manifest and can be disabled. See what crosses the network.

You need at least one agent CLI already installed and logged in. swe-mux does not install, manage, or proxy them. It runs the ones you already have, on the subscription you already pay for.

Install with Python

Requires Python 3.12 or newer. The package includes the built interface; Node is not needed.

$ uv tool install swe-mux
$ swe-mux # Windows desktop app

pipx install swe-mux is the alternative isolated install. For a browser on Windows, Linux or macOS, run swemux start, then open 127.0.0.1:8765. swemux doctor reports installation and runtime health.

The Windows app includes its tray and native window. First-run setup offers shortcuts. Linux and macOS use the daemon with a browser. All three platforms have required CI checks, including a source-daemon smoke test; that does not replace testing a published release on a clean machine.

Installation, source builds and upgrades · Start your first session · Troubleshooting