Remote hosts need a POSIX shell, tmux, and SSH (AgentMux can install tmux where missing). This computer qualifies directly on Linux and macOS; on Windows there are two local hosts — WSL and native PowerShell, with native sessions persisted by a built-in session daemon.

No. Only local orchestration and semantic memory search need Ollama. Without it, everything else is fully functional.

AgentMux — A Desktop Control Plane for AI Coding Agents

Capabilities

Everything you need to operate a fleet of agents

AgentMux never owns the agent process — it attaches to a tmux session on the host. Persistence is guaranteed by construction, not by the client staying online.

Session persistence

Close the client, suspend the laptop, lose the network — agents keep running. Reopen and you're back in the same pane with scrollback intact. A four-hour migration no longer depends on one SSH connection staying up.

Direct terminal access

Every agent's pane is a full terminal — colour, mouse reporting, selection, search — not a transcript view. Step in mid-task, correct the agent, and hand control back without restarting the run.

A wall of terminals

Split the terminal area into up to nine panes — a 3×3 wall across hosts, each independently interactive. Drag the seams, double-click a tab to zoom, and the layout reflows with the window and is restored on next start.

Broadcast with receipts

Send one instruction to any selection of agents; each returns a receipt confirming delivery. Fan-out to a fleet is auditable rather than assumed.

Orchestration under approval

A local model served by Ollama can take an objective — say, working out why an agent stalled — one tool call at a time. Every mutating operation is held for your explicit approval; scheduled patrols are strictly read-only.

Retrieval memory, kept local

Project facts, preferences, and agent activity are indexed for retrieval by wording or by meaning. Embeddings are computed locally; nothing leaves the machine. Credentials matching known patterns are redacted before storage.

Product Tour

Real screens, real workflows

Everything below is an actual application screenshot — no concept renders.

Terminal

Attach, and it's a real terminal

Attach to any agent's tmux pane: full colour, mouse reporting, search and selection. The side panel shows process state, recent output, and lifecycle controls.

Start / Stop / Restart / Attach — one row of buttons for the whole lifecycle
An exiting agent leaves a usable shell instead of destroying the session
Ten terminals against one host is still one SSH connection, one authentication

Coordination

Tell the whole fleet — and know who heard you

Send the same instruction to any selection of agents, across projects and hosts. Each agent returns a delivery receipt, turning fan-out from "assumed" into "confirmed, one by one."

Target by project, by host, or by manual selection
Per-agent delivery status at a glance
Failed deliveries stand out and can be retried individually

Provisioning & Ops

A new host, working in minutes

The install panel inspects a host first and offers only the agent CLIs and runtimes it can actually support, stating why others are unavailable. Installation runs inside tmux, so a dropped connection can't leave a partial package tree.

CPU by mode and core, memory, disk, network, NVIDIA GPU telemetry
SFTP browser and editor with atomic writes and conflict checks
This computer managed with zero setup: no sshd, no credentials

Interface

Comfortable for an all-day watch

Apple's system palette by default, with six alternative themes including Nord, Solarized, and a light theme. Information density tuned for long supervision sessions.

Ctrl/⌘ K command palette reaches everything
Per-agent status and last output in the fleet tree
Seven themes, dark and light

Operating Scenarios

Built for these ways of working

01Long-running workloads

Migrations, refactors, and test campaigns that outlast a working session or a network link.

02Multi-host fleets

Three to fifty hosts with concurrent agent activity, presented as one tree with per-agent status.

03Coordinated changes

Instruct an entire fleet in one action, with confirmation of what was delivered.

04Provisioning

Bring a new host to a working state without assembling install commands by hand.

05Unattended monitoring

Scheduled read-only patrols that report stalled agents — without authority to act on them.

06Restricted environments

Planning, embeddings, and memory run locally. No proxying of agent model traffic, no reading of API keys.

Get Started

Four steps to your first managed agent

Remote hosts need only tmux and an SSH account — AgentMux can install tmux where it's missing. This computer is even simpler: no credentials at all.

Read the full docs→

1

Add a host
Remote: address, user, and one of ssh-agent / key / password, with jump hosts supported. Local: nothing but a name.
2

Add a project and workspace
A working directory on that host. Or browse the host's files and add the directory in place — its name, path, and host are already known.
3

Add an agent and start it
A name and the command that starts it. Hit Start and it's running inside tmux on the host.
claude --dangerously-skip-permissions
4

⌃K opens the command palette
Attaching to an agent, opening a shell, installing a CLI, changing theme — the fastest route to all of it.
Ctrl / ⌘ + K

Ctrl/⌘KCommand palette

Ctrl/⌘BShow or hide the tree

Ctrl/⌘\Add a pane — instantly with the next open tab, otherwise asking what to attach

Ctrl/⌘⇧\Close the pane, leaving the tab and its shell open

Ctrl/⌘⇧↵Fill the area with the focused pane, and back again

Ctrl/⌘⌥←→Move between panes — zoomed, this reads them one at a time

Download

One build per platform, produced by GitHub Actions from the tagged commit

Every file ships with a .sha256 alongside.

macOS

macOS 11+ · Universal for Intel & Apple Silicon

agentmux-macos-universal.zip

Download ↓

Windows

Windows 10+ · WSL and native PowerShell local hosts

agentmux-windows-amd64.zip

Download ↓

Linux

GTK3 & WebKitGTK 4.1 required · amd64

agentmux-linux-amd64.tar.gz

Download ↓

Note: builds are not yet code-signed or notarized. On macOS, choose Open Anyway in Privacy & Security on first launch (or xattr -dr com.apple.quarantine); on Windows, "More info → Run anyway". Downloading with curl -L -O avoids the macOS quarantine attribute.

FAQ

Questions you might have

Does AgentMux decide what my agents do?＋

No. Objectives, prompts, and repository conventions remain yours. The orchestrator investigates and proposes; any action that modifies a host executes only after your explicit approval.

What do hosts need?＋

A POSIX shell and tmux on every host (AgentMux can install tmux where it's missing), plus SSH on remote ones. This computer qualifies directly on Linux and macOS; on Windows the same machine offers two local hosts — the WSL distribution (where tmux lives) and native Windows (PowerShell, persisted by a built-in session daemon, so closing the window does not stop native work either). Remote Windows hosts are not supported.

Is Ollama required?＋

No. Only local orchestration and semantic memory search need Ollama (one chat model plus one embedding model). Without it, everything else is fully functional.

Can it report or cap my agents' model spend?＋

No — deliberately. Agent traffic goes straight from the host to whichever provider the agent CLI is configured for. AgentMux does not proxy it and does not read the keys, so it can neither report cost nor enforce a budget.

Is it built for teams?＋

One operator per installation. State, credentials, and the decision log live on the workstation — no shared server, no team account, no central audit sink. Two people working the same fleet see the same tmux sessions but keep separate histories.

Does deleting something in AgentMux stop remote work?＋

Never. Removing a workspace or agent record only removes the local record — the tmux session keeps running. The one control that destroys a running session is named Kill, and it confirms first, stating what is lost.

A Desktop Control Plane
for AI Coding Agents

Works with the agents and infrastructure you already run

Everything you need to operate a fleet of agents

Session persistence

Direct terminal access

A wall of terminals

Broadcast with receipts

Orchestration under approval

Retrieval memory, kept local

Real screens, real workflows

Attach, and it's a real terminal

Tell the whole fleet — and know who heard you

A new host, working in minutes

Comfortable for an all-day watch

Permissions, credentials, and audit — built into the structure

Encrypted credentials

Host keys pinned

Secrets never reach the UI

Tool gate with risk tiers

Unattended = read-only

Fully auditable

Built for these ways of working

01Long-running workloads

02Multi-host fleets

03Coordinated changes

04Provisioning

05Unattended monitoring

06Restricted environments

Four steps to your first managed agent

Add a host

Add a project and workspace

Add an agent and start it

⌃K opens the command palette

One build per platform, produced by GitHub Actions from the tagged commit

macOS

Windows

Linux

Questions you might have

Let the agents run. Go get some rest.