mixpeek/amux

What the fleet gets that a single agent never had:
- **Atomic tasks**: a shared kanban board where claiming is compare-and-swap, so two workers can never grab the same card; done requires evidence, verified requires a peer check
- **Worker awareness**: every worker sees the fleet (who is live, what they own, what they are doing) and can peek into any peer's terminal before interrupting
- **@ each other**: origin-stamped inter-worker messaging; the server records the true sender, so provenance is a fact rather than a claim
- **Steering**: type into any running session from the dashboard or phone; redirect mid-task without stopping the run
- **Schedules & loops**: cron-style recurring prompts (daily at 9am, every 15m) plus self-pacing autonomous loops for overnight runs
- **Groups & scope**: workers organize into lanes that share memory, environment, and gates; settings resolve card → worker → group → global
- **Model switching**: swap the model or provider on a running worker; pick the brain per task, keep the context
- **Message history**: every prompt, reply, and delivery is a ledger row you can fetch later
- **Self-healing**: a watchdog that auto-compacts, restarts crashed sessions, and replays the last message
> **amux.io** · Getting started · FAQ · Blog
Quickstart — one command
That is the whole setup. The installer checks prerequisites (Rust toolchain, tmux; it prompts before installing anything), builds the workspace, installs the server and CLI to ~/.local/bin, loads the launchd agents on macOS, mints ~/.amux (DB, TLS, auth token) on first boot, waits for /health, and prints:
Open **https://localhost:8824**, accept the self-signed cert warning once, and add your first worker from the dashboard. Re-running ./install.sh upgrades in place and never touches your data; ./uninstall.sh removes the binaries and agents and leaves ~/.amux alone.
After first install
Once installed, day-to-day commands are short:
make run is the command after git pull — it rebuilds release, installs the binary, and the launchd-managed server picks it up automatically. make dev is for working on migrations or features you don't want touching the live DB.
**Requirements:** tmux 3.2+, and at least one of Claude Code, Codex CLI, or Gemini CLI. The Rust toolchain is installed via rustup if you don't have it (with your confirmation).
Linux: systemd user services
On Linux with systemd (Ubuntu 22.04+, Debian 11+, Fedora 36+), ./install.sh automatically creates and enables three user-level services:
- amux-server.service — the main server
- amux-builder.service — auto-rebuild on code changes
- amux-builder.timer — periodic rebuild check (every 60s)
After ./install.sh completes, the services are ready to start:
View logs and status:
See docs/systemd-setup.md for complete documentation: troubleshooting, multi-user setup, environment overrides, and migration between versions.
For other Linux distributions without systemd, run the server manually:
**Platform support:**
- **macOS** (primary) — ./install.sh sets up launchd agents for automatic startup and rebuild
- **Linux** (systemd) — ./install.sh creates systemd user services (Ubuntu 22.04+, Debian 11+, Fedora 36+)
- **Other Linux** — ./install.sh builds and installs binaries; run the server manually or wrap in your process manager
> **License:** MIT + Commons Clause — free to use, modify, and self-host. Commercial resale requires a separate license.
Which server is real?
**The Rust server (crates/amux-server, port 8824).** That is what ./install.sh installs, what the dashboard talks to, and where all new work lands. Every /api family answers natively; the live proof is GET /api/debug/boundary, which reports proxied: []. If you are reading code, start in crates/ — it is the only server code in the tree. The same binary also answers the retired port 8822 while a compatibility bind survives (see Legacy), so there is no second server to reason about; the Python predecessor is gone.
Architecture
One Rust workspace, four crates:
| Crate | What |
|---|---|
| crates/amux-server | The server: axum HTTP API on **8824** (HTTPS, self-signed; plain HTTP redirected), single-writer SQLite store with an event journal, SSE + delta sync, scheduler/orchestrator runtime, embedded dashboard |
| crates/amux-dashboard | The SPA, embedded into the server binary at build time (no node/npm needed) |