51 of 51 criteria have a sourced finding; 49 were also cross-checked by a second agent. Every comparison that includes amux links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Web dashboard/PWA (desktop and mobile browsers, Android via Add to Home Screen), native iPhone/iPad app (WKWebView wrapper, iOS 16+), Mac app (macOS 12+, Apple silicon and Intel, not notarized), and two CLIs. Server runs on macOS and Linux only; no Windows or Linux desktop app, no editor extension.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients, amux Mac app (native Swift window on WebKit), amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: macOS, Linux, iOS · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Mac app is not notarized; no Windows server or client; Android has a source wrapper in the repo but ships only as a PWA; all clients need a reachable amux server.
Cli [supported] Product-owned amux bash client and amux-rs Rust CLI for sessions, board, schedules, send, export/import. Sources: amux-mixpeek:cli, amux-mixpeek:selfhost.
Editor extensions [unsupported] No IDE extension: searched the repo for vscode/jetbrains/.vsix/extension manifests (none; only skills/ and integrations/cli-tools). Sources: amux-mixpeek:readme, amux-mixpeek:docsite.
Task actions [supported] Start/stop workers, send and steer, approve held actions, answer blocked prompts and review the board from dashboard, apps and CLI (FAQ phone answer; amux send/board verbs). Sources: amux-mixpeek:faq, amux-mixpeek:cli, amux-mixpeek:docsite.
Notifications [supported] Web push (VAPID, crates/amux-server/src/push), iOS app notification bridge (NotifyBridge.swift), Mac menu bar/Dock badge, plus urgent SMS/iMessage alert settings. Sources: amux-mixpeek:manifest, amux-mixpeek:ios, amux-mixpeek:readme.
Cross device continuity [supported] All clients connect to the same server, which holds sessions, board and history; Mac app restores windows after restart. Sources: amux-mixpeek:readme, amux-mixpeek:selfhost.
Runs unmodified agent CLIs in tmux: Claude Code, Codex, Gemini CLI, OpenCode (ACP/serve protocol), Ollama-backed local models, plus Grok and muse adapters; mixed fleets and per-worker model switching are supported.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Claude Code, Codex, Gemini CLI, OpenCode, Ollama
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Cursor, Aider, Pi and Antigravity are not integrated; Ollama is a raw model server without agent features; hot model switching is not available for every provider.
5 atomic answers
Harnesses [supported] Provider adapters for claude-code, codex, gemini, ollama, grok, muse (provider/static_providers.rs, provider/claude.rs) and OpenCode (opencode/); FAQ lists Claude Code, Codex, Gemini CLI, OpenCode and Ollama. Sources: amux-mixpeek:providers, amux-mixpeek:providercsv, amux-mixpeek:faq.
Model providers [supported] Anthropic, OpenAI, Google and Ollama models via each CLI; live model catalogs fetched with ANTHROPIC/OPENAI/GEMINI API keys (provider/live_catalog.rs). Sources: amux-mixpeek:providers, amux-mixpeek:faq.
Custom adapters [partial] Adding a harness needs a Rust ProviderAdapter implementation in crates/amux-server/src/provider/; no user-level plugin API found (searched provider/, docs/ for plugin/adapter registration). Sources: amux-mixpeek:providers.
Session integration [supported] Hybrid: launches the agent CLI inside tmux, reads status from Claude Code hook events and terminal scrape, and drives OpenCode through a structured ACP/serve protocol. Sources: amux-mixpeek:faq, amux-mixpeek:providercsv, amux-mixpeek:selfhost.
Mixed harness operation [supported] One fleet runs Claude Code, Codex, Gemini CLI and OpenCode workers side by side on the same board. Sources: amux-mixpeek:faq, amux-mixpeek:readme.
Bring your own: agent CLIs use their own Claude, ChatGPT or Google logins (subscription) or pasted API keys; amux sells no model credits; Ollama gives local models; Claude account rotation exists for plan limits.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Provider terms on subscription use by orchestrators are external; no vendor credits.
7 atomic answers
Agent subscriptions [supported] FAQ and pricing: sign in with Claude, ChatGPT or Google on your server; local runs reuse each CLI login. Sources: amux-mixpeek:faq, amux-mixpeek:pricing.
Api accounts [supported] Paste Anthropic, OpenAI or Gemini API keys (pricing FAQ; server.env keys in docs/credentials.md). Sources: amux-mixpeek:pricing, amux-mixpeek:faq.
Vendor credits [unsupported] Pricing and FAQ say model usage is billed by the provider separately; no amux-sold model credits (searched pricing, FAQ). Sources: amux-mixpeek:pricing, amux-mixpeek:faq.
Local models [supported] Ollama-backed local models run as workers (FAQ, provider/static_providers.rs). Sources: amux-mixpeek:faq, amux-mixpeek:providers.
Account switching [partial] Per-account Claude plan usage history and account rotator (api/usage_accounts.rs, scripts/claude-rotate.py); rotator is a script rather than a UI switch. Sources: amux-mixpeek:usageaccts.
Vendor account requirement [supported] Self-hosted needs no amux account (privacy policy); amux Cloud requires an account and subscription. Sources: amux-mixpeek:privacy, amux-mixpeek:pricing.
Provider restrictions [unknown] Provider terms on third-party subscription use are not documented by amux.
curl|bash installer (macOS/Linux) builds the Rust server, asks before installing Rust/tmux, then register a session in a directory and send a task; projects can use a worktree, and a plain directory works. Cloud is ready in about three minutes at yourname.amux.io.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Needs tmux 3.2+ and an agent CLI already installed and signed in; no Windows; Git is optional for plain sessions.
No git [supported] A session is a tmux pane in any working directory; worktree isolation is a separate option (docs/project-single-worktree.md). Sources: amux-mixpeek:docsite, amux-mixpeek:singleworktree.
Local git without remote [supported] Projects create a local worktree/branch under .worktrees without requiring a remote; land queue pushes only when origin exists. Sources: amux-mixpeek:singleworktree, amux-mixpeek:landqueue.
Hosted git [partial] GitHub use is through the agent CLIs and gh in skills (skills/amux-contribute.md); no first-class GitHub repo import. Sources: amux-mixpeek:singleworktree.
Prerequisite guidance [supported] README and docs list tmux 3.2+, one agent CLI, macOS/Linux, and Tailscale for remote access. Sources: amux-mixpeek:readme, amux-mixpeek:docsite.
Byo vps onboarding [unsupported] Searched README, docs, install.sh for VPS/remote-host provisioning commands: none; remote access is Tailscale to your own machine only. Sources: amux-mixpeek:readme, amux-mixpeek:installsh.
REST API under /api (every dashboard feature), amux/amux-rs CLIs, outbound webhooks for connectors; bearer-token auth; no versioned SDK, and an MCP registry client plus an amux app for ChatGPT.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No published SDK or API stability guarantee; the HTTP API retains legacy session/tag spellings.
Sdk [unsupported] Searched repo for sdk/client packages (package.json, Cargo workspace crates amux-cli/core/server/dashboard): no SDK published. Sources: amux-mixpeek:selfhost.
Mcp server [partial] amux app for ChatGPT exposes worker lists/output/board cards over MCP-style tools via cloud.amux.io (docs/chatgpt-app, privacy); no general MCP server for coding agents found. Sources: amux-mixpeek:privacy.
Webhooks [partial] Event dispatch and connector webhooks exist (runtime_jobs/event_dispatch.rs, api/connectors.rs); no documented generic task-start webhook. Sources: amux-mixpeek:connectors.
Operations [supported] Create worker, send, peek, stop, board CRUD/claim/assign, schedules, review-style audit, export are available through API and CLI. Sources: amux-mixpeek:cli, amux-mixpeek:boardguide.
MCP registry tab (~/.amux/mcp.json) with readiness checks, skills and slash commands for agents, connectors broker (Google, Slack, Granola), and browser/computer-use tools; credentials held in server.env/vault.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
MCP servers are inherited by the underlying CLIs; permission scope is per worker capability rather than per tool.
7 atomic answers
Mcp client [supported] /api/mcp registry reads and edits ~/.amux/mcp.json with readiness computed from credentials (api/mcp.rs). Sources: amux-mixpeek:mcp.
Plugins [partial] Skills/slash commands and templates directories (skills/, templates/), connectors; no plugin SDK. Sources: amux-mixpeek:docsite.
Instructions import [supported] Layered memories global→group→worker and CLAUDE.md/AGENTS.md/GEMINI.md read by the CLIs; skills library. Sources: amux-mixpeek:selfhost.
Authentication [supported] Connectors OAuth broker stores per-account tokens chmod 600 under ~/.amux/connectors; secrets in server.env (docs/credentials.md). Sources: amux-mixpeek:credentials.
Permission scope [supported] Per-worker capabilities and group scoping govern folders and env; grants.rs adds owner-approved ad-hoc grants. Sources: amux-mixpeek:ctlsandbox.
Integration owner [supported] Registry and connectors are amux-managed; per-agent MCP use is inherited from each CLI. Sources: amux-mixpeek:mcp.
Dashboard is a web SPA/PWA embedded in the Rust binary; Mac app is native Swift on system WebKit (about 1.5 MB); iPhone/iPad app is a native Swift WKWebView wrapper; Android wrapper is Kotlin Compose WebView in source.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Mac app (native Swift window on WebKit), amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: macOS, iOS · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
All clients render the same web dashboard; no React Native or Tauri.
4 atomic answers
Desktop implementation [supported] Swift app hosting WKWebView-style system WebKit window (desktop/amux-desktop.swift; README: native window on the system WebKit). Sources: amux-mixpeek:desktop, amux-mixpeek:readme.
Mobile implementation [supported] iOS: Swift WKWebView wrapper (ios/AmuxApp/Sources/WebView.swift; privacy policy); Android: Kotlin Compose WebView in source only. Sources: amux-mixpeek:ios, amux-mixpeek:android, amux-mixpeek:privacy.
Cards are created locally (UI, CLI, API), from delivered prompts through model-assisted intake, or imported from a GitHub issue by CLI; amux’s own board is authoritative; Telegram, channels and commit mentions can trigger work.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
GitHub import is a one-time copy into amux; updates stay in GitHub or amux separately.
Prompt intake [supported] Delivered prompts become board outcomes through semantic intake and the durable command lifecycle (api/board_intake.rs, docs/command-lifecycle.md). Sources: amux-mixpeek:intake, amux-mixpeek:convlife.
External import [partial] amux board import gh:owner/repo#N imports a GitHub issue (amux bash client, cmd_board import); no Linear or Jira import found. Sources: amux-mixpeek:cli.
Chat git triggers [partial] Telegram connector (api/telegram.rs), per-session channels and commit mention notes (runtime_jobs/commit_mention_notes.rs) route messages and commits; no PR-comment trigger found. Sources: amux-mixpeek:connectors.
Authoritative tracker [supported] amux’s SQLite board is the authoritative tracker; external trackers are not required. Sources: amux-mixpeek:boardguide, amux-mixpeek:schema.
Stable ids [supported] Cards carry stable prefixed IDs (issues.id) and a rev counter (migrations/0001_baseline.sql). Sources: amux-mixpeek:schema.
Sync [unsupported] No continuous sync with GitHub/Linear/Jira found: searched crates/amux-server/src and docs for sync of external issue state; only the one-shot import exists. Sources: amux-mixpeek:cli, amux-mixpeek:boardrs.
Supported edits [supported] Title, description, status, owner session, tags, due, type, gate, reviewer and dependencies are editable on amux cards. Sources: amux-mixpeek:schema, amux-mixpeek:boardguide.
External roundtrips [partial] Updating or closing the originating GitHub issue happens in GitHub or through the agent’s own gh use. Sources: amux-mixpeek:cli.
Cards carry acceptance criteria authored before execution by someone other than the executor; planning intent is versioned; project leads keep a plan file; plans can be revised while running with a new request invalidating older candidates.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Several protections are contract rules adopted by the vendor and enforced at board transition; plan editing UI depth was not confirmed.
Acceptance criteria [supported] Stored criteria per card, authorship checked, required before leaving todo (api/criteria.rs; contract rule 1). Sources: amux-mixpeek:criteria, amux-mixpeek:orch.
Editors [partial] Criteria and intent are editable through API/UI by their authors; no free-form plan editor found. Sources: amux-mixpeek:criteria, amux-mixpeek:planning.
Revisions [supported] Planning mutations record revisions (amux_core::revision EntityType/MutationKind used in api/planning.rs); board rev counter. Sources: amux-mixpeek:planning, amux-mixpeek:schema.
Implementation links [supported] Cards link to commits and artifacts as evidence; message-to-card receipts (docs/command-lifecycle.md). Sources: amux-mixpeek:convlife, amux-mixpeek:orch.
Amendment [supported] Additional requests or revised criteria update the same project’s intent and invalidate older candidates (docs/projects-lead-mode.md). Sources: amux-mixpeek:leadmode.
Restart persistence [supported] Server restart reconstructs the run from durable inputs (docs/projects-lead-mode.md). Sources: amux-mixpeek:leadmode.
Epics, parent/child decomposition (`amux board epic/decompose`), depends_on blockers that drive ready/unblocked state, epic auto-resolution when children finish, and typed cards with gates; flat lanes without a mandatory workflow.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Hierarchy depth and propagation beyond epic completion are only partly documented.
9 atomic answers
Epics [supported] item_type epic; epic completes when all children resolved (api/board.rs:553; amux board epic). Sources: amux-mixpeek:boardrs, amux-mixpeek:cli.
Readiness [supported] Computed status “unblocked” when all deps resolved (api/board.rs:437-486). Sources: amux-mixpeek:boardrs.
Enforcement [partial] Dispatcher promotes dependency-ready cards and board drive honors leases; manual worker sends are not blocked by dependencies. Sources: amux-mixpeek:convlife, amux-mixpeek:boardrs.
State propagation [partial] Epic status derives from children; discarded or quarantined children cannot manufacture completion. Sources: amux-mixpeek:convlife, amux-mixpeek:boardrs.
Task to epic [supported] amux board epic converts/attaches cards to epics; refinements reuse the open command epic. Sources: amux-mixpeek:cli, amux-mixpeek:convlife.
Identity retention [supported] Card ID, log and history persist across type/epic changes (issues.log, rev). Sources: amux-mixpeek:schema.
Workflow constraints [supported] No mandatory workflow; card type selects gate strictness (docs/guide.md). Sources: amux-mixpeek:boardguide.
Layered versioned memories (global→group→worker), per-scope rules/env/gates via /api/scope, skills library, repo instruction files read by the CLIs, project files via the file browser; memories are soft-deletable and versioned.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Staleness handling relies on grooming jobs and memory hygiene; per-fact provenance for repo docs is not tracked.
10 atomic answers
Instructions [supported] Memories layered global→group→worker plus CLAUDE.md/AGENTS.md/GEMINI.md present in the repo root (docs/self-hosting.md primitives). Sources: amux-mixpeek:selfhost, amux-mixpeek:memories.
Skills [supported] skills/ directory of skills and slash commands (skills/amux.md, amux-board.md, pr-merge.md). Sources: amux-mixpeek:docsite.
Project docs [supported] File browser edits and searches any worker directory (docs/self-hosting.md filesystem primitive). Sources: amux-mixpeek:selfhost.
Memory [supported] api/memories.rs versioned CRUD with layers; orchestrator/memory_resupply.rs re-supplies memory after compaction. Sources: amux-mixpeek:memories.
Freshness [partial] Board grooming of stale cards after 7 days (api/board_groom.rs); memory dream/consumer jobs; no TTL on memory text. Sources: amux-mixpeek:boardrs.
Takeover continuity [supported] Workers have durable identity, messages and memories server-side so another client or person sees the same context. Sources: amux-mixpeek:selfhost.
Universal FTS5 search over amux records and a file search/viewer for worker directories; computed `.mdai` files synthesize cited sources; photos, uploads, voice dictation and recordings give multimodal input; no repository code index or conflict detection.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Search covers amux data and file browsing, not a semantic code index; no review-time architecture enforcement.
10 atomic answers
Code search [partial] File browser search over worker directories; the agents’ own CLIs do code search; api/search.rs is FTS5 over amux records. Sources: amux-mixpeek:search, amux-mixpeek:selfhost.
Indexing [partial] FTS5 index over cards, messages, memories, workers, journal, schedules (api/search.rs); no repository code index found. Sources: amux-mixpeek:search.
Citations [partial] .mdai outputs label evidence MSG-<id>; no general citation of code context. Sources: amux-mixpeek:selfhost.
Conflict detection [unsupported] Searched crates and docs for architecture/API conflict detection at review: none (only duplicate-work and git guards). Sources: amux-mixpeek:orch.
Review enforcement [unsupported] No review-time architecture or API consistency enforcement found; verification is tests/criteria based. Sources: amux-mixpeek:orch.
Full native board: create, edit, log/discuss, priority via position and pin, tags, assign (owner session), full-text search, filters, archive/undelete, epic links on cards with child progress, backlog parking, explicit todo/claim dispatch, separate cards and worker sessions, typed gates; no external tracker needed. A fleet-by-epic swimlane view is designed in docs/board-command-center.md but not built at the pinned commit.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
Priority is ordering/pinning rather than a labeled field; multi-person discussion is a per-card log.
Project epic views [partial] Cards show an epic chip and epic detail lists children with progress (crates/amux-dashboard/static/app.js epic handling near lines 28651-28680, 53178); the epic swimlane view is a design in docs/board-command-center.md (build order item 4) and no swimlane code exists in app.js. Sources: amux-mixpeek:boardcc, amux-mixpeek:gitpanel.
Idea parking [supported] Backlog column parks cards without starting an agent. Sources: amux-mixpeek:boardguide.
Task session separation [supported] Cards are separate from workers/sessions; a worker is an execution record (docs/project-single-worktree.md). Sources: amux-mixpeek:singleworktree.
Agents use the same board IDs and fields as humans through the CLI/REST API: claim atomically, assign, change status behind gates, create dependencies and children, and post results; the dashboard shows writes with worker attribution; skills teach agents the verbs.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Owner-only edits and force bypasses are logged rather than blocked; conflict handling is atomic claim plus revision counter.
14 atomic answers
Shared ids [supported] One board for humans and agents; same card IDs. Sources: amux-mixpeek:boardguide.
Read [supported] amux board ls and GET /api/board read. Sources: amux-mixpeek:cli.
Human visibility [supported] Dashboard board shows agent writes with owner and log. Sources: amux-mixpeek:boardguide.
Attribution [supported] Card log/rev record actor; request log records worker API calls (api/audit.rs). Sources: amux-mixpeek:schema.
Permissions [partial] Scope/capability layers and AMUX_SCOPE_WRITE_AGENTS limit what agents write; board writes are open to workers in scope. Sources: amux-mixpeek:selfhost.
No maintained product-spec object across tasks. Memories, scoped rules, VISION.md-style files and per-card criteria exist but are not requirement records with approvals or drift detection.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Bounded search found no requirement-to-implementation tracing or drift detection.
9 atomic answers
Persistent requirements [unsupported] Searched docs/, crates/, skills/ for spec/requirement entities: only memories and card criteria exist. Sources: amux-mixpeek:memories, amux-mixpeek:criteria.
Human edits [unsupported] No spec object to edit; memory and criteria edits only. Sources: amux-mixpeek:memories.
Many workers run concurrently as separate tmux sessions across Claude, Codex, Gemini and OpenCode; no fixed quota in code, bounded by machine or Cloud plan size; dashboard shows live status per worker.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Practical limit is CPU/RAM and provider rate limits; concurrency is not enforced by a product quota.
5 atomic answers
Concurrent sessions [supported] Each worker is its own tmux session; FAQ says dozens in parallel (api/session_verbs.rs, backend/tmux.rs). Sources: amux-mixpeek:faq, amux-mixpeek:selfhost.
Concurrent tasks [supported] Each worker holds its own board cards; board drive dispatches ready cards across workers (runtime_jobs/board_drive.rs). Sources: amux-mixpeek:boarddrive.
Quotas [partial] No fixed seat or worker cap found; Cloud plans size the server (4/8/16 vCPU) and a worker-resource watcher exists (runtime_jobs/worker_resources.rs). Sources: amux-mixpeek:pricing, amux-mixpeek:faq.
Observed concurrency [partial] FAQ states dozens; docs/benchmarks and stall reviews record fleets up to 21 background agents but no catalog measurement. Sources: amux-mixpeek:faq.
Status visibility [supported] Workers show working/waiting/idle/stalled with structured wait reasons (amux-core/src/stall.rs); dashboard worker grid and peek. Sources: amux-mixpeek:stall, amux-mixpeek:faq.
Cards are assigned to human or agent owners; claiming is atomic so two agents never take the same card; board drive and intent routing assign work to workers; one writer per worktree is enforced.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Routing quality depends on a helper model; assignment by label is advisory when a human force-moves a card.
7 atomic answers
Human assignment [supported] owner_type human/agent on issues; amux board assign (migrations/0001_baseline.sql). Sources: amux-mixpeek:schema, amux-mixpeek:cli.
Agent assignment [supported] Agents claim or are assigned cards; board drive dispatches ready cards (runtime_jobs/board_drive.rs). Sources: amux-mixpeek:boarddrive, amux-mixpeek:cli.
Claims [supported] README and docs: claiming a card is atomic; claim and transition share one store transaction (docs/harness-recovery.md). Sources: amux-mixpeek:readme, amux-mixpeek:boardguide.
Ownership enforcement [partial] Claim and transition share one store transaction (docs/harness-recovery.md); one writer per worktree is a contract rule rolled out lane by lane (docs/orchestration-contract.md rollout). Sources: amux-mixpeek:orch, amux-mixpeek:harnessrec.
Workers message each other directly (channels, same-group peers) and read each other’s output via the API; project mode has one persistent lead that can use provider subagents; the amux skills teach agents the verbs. A server-side coordinator role is a prompt/skill pattern rather than a dedicated orchestrator agent.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No dedicated parent/child session type; delegation across workers is by message and board cards.
12 atomic answers
Roles [partial] Lead worker per project, reviewer spawned for verification (contract rule 3), group peers; roles are conventions plus scoped workers. Sources: amux-mixpeek:leadmode, amux-mixpeek:orch.
Model harness effort [supported] Model and provider are chosen per worker and switchable while it runs; flags per session. Sources: amux-mixpeek:faq, amux-mixpeek:docsite.
Messages [supported] amux send, channels API and same-group peer messaging (api/channels.rs, api/worker_messaging.rs). Sources: amux-mixpeek:workermsg, amux-mixpeek:faq.
Results return [partial] Agents read each other’s output through the REST API and peek; results return as card evidence and messages. Sources: amux-mixpeek:faq, amux-mixpeek:boardguide.
Cross harness [supported] Workers on different harnesses share the board and messages. Sources: amux-mixpeek:faq.
Orchestration owner [supported] amux supplies the board, messages, skills and drive loop; coordinator model loop is the user’s agent. Sources: amux-mixpeek:selfhost, amux-mixpeek:boarddrive.
Activation [supported] Always available on the server; no flag. Sources: amux-mixpeek:selfhost.
Authentication [supported] Agents call the API with the worker session token/bearer and server-stamped provenance (api/grants.rs). Sources: amux-mixpeek:selfhost.
Server-owned durable schedules ("daily at 9am", "every 15m", one-shots), event subscriptions on the ledger, recurring loops, a goal keeper for completion conditions, missed-run skip/catch-up policy and retries; runs on the server regardless of client.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
If the host is asleep or down, only capped catch-up replays missed runs; overlap handling is by skip/catch-up policy.
8 atomic answers
Schedules [supported] Schedules API with CRUD, run history and audit (runtime_jobs/scheduler.rs, api/schedules.rs). Sources: amux-mixpeek:scheduler.
Completion conditions [partial] Goal keeper holds a worker until its Claude Code /goal is met; card gates define done. Sources: amux-mixpeek:goalkeeper.
Scheduler location [supported] Rust server scheduler on the amux host (self-hosted or Cloud). Sources: amux-mixpeek:scheduler.
Overlaps [partial] Missed-run policy skip|catchup with a catch-up cap; no explicit concurrent-run lock documented. Sources: amux-mixpeek:scheduler.
Retries [supported] Reserve-refused one-offs retry at limit reset or after 15 minutes (scheduler.rs:311-352). Sources: amux-mixpeek:scheduler.
Pause/resume/stop per worker and fleet-wide, steering by sending text between turns, a Needs-you queue for pending decisions with optional auto-approve, push notifications and urgent SMS/iMessage escalation, stall detection and retained history.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux-rs and bash amux command-line clients, amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Stop kills the tmux session but history persists; Chat tab and terminal parity is partial.
10 atomic answers
Pause [supported] amux pause/resume and pause-all (bash cmd_pause). Sources: amux-mixpeek:cli.
Dashboard shows a kanban board by status with types and gates, a worker grid with live status, a Needs-you queue, state-of-the-org digest and a map/org graph; per-epic swimlanes are described in design docs but not present in the pinned dashboard.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Fleet-by-epic swimlane view is not shipped at the pinned commit; dependencies are visible on cards.
8 atomic answers
Fleet fixture [unknown] Rendered multi-epic fixture not examined; catalog does not run products.
No mandatory workflow: quick tasks go to any worker, tasks grow into epics, cards have types, natural-language requests route through intent planning, per-worker model/flags, in-run send/model switch; relationships are visible on cards and messages.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No visual coordinator/child run tree.
10 atomic answers
Quick task [supported] amux send or board add starts work without a preset. Sources: amux-mixpeek:cli.
Local tmux workers on your Mac/Linux host, self-hosted server reachable over Tailscale (BYO machine), and amux Cloud: a dedicated always-on Hetzner server per customer that keeps working when your laptop sleeps. Hybrid via export/import.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: local, own-server, vendor-cloud · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Self-hosted still runs on a host you keep awake; Cloud is paid from the start; no BYO-VPS provisioning installer.
12 atomic answers
Local [supported] Workers run in tmux on the machine hosting the server (README). Sources: amux-mixpeek:readme.
Byo remote [supported] Install on any macOS/Linux machine or server and reach it over Tailscale; no provisioning tooling (README, FAQ). Sources: amux-mixpeek:readme, amux-mixpeek:faq.
Hybrid [supported] amux export then amux import --to https://you.amux.io moves a local setup to Cloud; Cloud servers can join your tailnet. Sources: amux-mixpeek:readme, amux-mixpeek:faq.
Provisioning [supported] Ready in about 3 minutes after Stripe checkout; server image built per customer (pricing, cloud/README.md). Sources: amux-mixpeek:pricing, amux-mixpeek:security.
Payer [supported] Customer pays Cloud subscription and model providers separately. Sources: amux-mixpeek:pricing.
Resources [supported] Solo 4 vCPU/8 GB/80 GB, Team 8/16/160, Max 16/32/320. Sources: amux-mixpeek:pricing.
Region [supported] Hetzner Falkenstein, Nuremberg or Helsinki. Sources: amux-mixpeek:security.
Expiry [supported] Runs 24/7 while subscribed; after cancel the server runs until period end, snapshot kept 30 days. Sources: amux-mixpeek:pricing, amux-mixpeek:privacy.
Client disconnect [supported] Agents keep running in tmux on the server when a client disconnects. Sources: amux-mixpeek:readme, amux-mixpeek:faq.
Other device continuation [supported] Phone, Mac app and browser all attach to the same running workers. Sources: amux-mixpeek:readme, amux-mixpeek:faq.
Default shared directory per worker; optional isolated workers and projects each get a durable git worktree/branch under .worktrees with one writer; each agent CLI runs inside its own CLI sandbox derived from worker capabilities; Cloud gives a dedicated VM per customer; no container-per-worker.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
Worktrees are file separation, not hostile-code containment; CLI sandbox strength is that of each CLI.
12 atomic answers
Checkout [supported] Shared checkout is the default; explicit shared-checkout option also single-writer scheduled (docs/project-single-worktree.md). Sources: amux-mixpeek:singleworktree.
Container [unsupported] Searched crates and docs for per-worker container launch: only the Docker build of Cloud images (cloud/docker) and computer-use; no per-worker container. Sources: amux-mixpeek:sessionverbs.
Vm [supported] Cloud: one dedicated server per customer (security page). Sources: amux-mixpeek:security.
Os sandbox [partial] api/cli_sandbox.rs writes Claude Code's sandbox settings (claude --settings) from worker capabilities and the file states Codex lanes are reported unsupported; on Linux the sandbox needs bwrap and socat, otherwise enforce mode refuses to run a shell; customer OS boundary in api/customer_isolation.rs. Sources: amux-mixpeek:ctlsandbox, amux-mixpeek:custiso.
Process [partial] tmux process per worker; host guard lowers priority; no namespace isolation. Sources: amux-mixpeek:hostguard.
Network [partial] cli_sandbox.rs: network is unrestricted ('*') unless the owner sets AMUX_CAP_NETWORK=<domains>, which is written into the Claude sandbox settings as an allowed-domains list; no per-worker UI or default egress filtering, and no equivalent for other harnesses. Sources: amux-mixpeek:ctlsandbox.
Security boundary [partial] Customer OS boundary and CLI sandboxes; amux does not claim hostile-code containment (security docs). Sources: amux-mixpeek:custiso, amux-mixpeek:security.
tmux workers survive server restarts and client disconnects; on macOS workers return to their own conversation after reboot; usage-limit delivery resumes at reset; recovery adopts receipts and avoids replaying uncertain actions; the server does not restart a crashed agent process.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
A crashed agent process is not restarted automatically; macOS watchdog script is optional and Claude-only.
Worker crash [partial] FAQ: amux does not restart a crashed agent today; optional scripts/tmux-watchdog.sh restarts Claude workers on macOS. Sources: amux-mixpeek:faq, amux-mixpeek:readme.
Service restart [supported] Server self-adopts new builds, workers persist; crash tests restart the binary and exercise recovery (docs/harness-recovery.md). Sources: amux-mixpeek:harnessrec, amux-mixpeek:selfhost.
Expiry [supported] Cloud snapshot kept 30 days after cancel; no other compute expiry. Sources: amux-mixpeek:pricing.
Transcript reload [supported] Worker logs and history persist in ~/.amux and SQLite. Sources: amux-mixpeek:selfhost.
Process reconnect [supported] Server reattaches to surviving tmux sessions at startup (orchestrator/runtime.rs reconcile). Sources: amux-mixpeek:harnessrec.
Task resume [supported] Board cards, leases and project runs reconstruct from durable state (docs/projects-lead-mode.md). Sources: amux-mixpeek:leadmode.
State reconstruction [supported] DB state reconciled against backend reality at startup. Sources: amux-mixpeek:harnessrec.
Context loss [partial] Uncertain results retained as interrupted rather than success; agent conversation context depends on CLI resume. Sources: amux-mixpeek:harnessrec.
Environment variables layer global→group→worker and a vault holds secrets; Cloud keeps 7 daily backups and a 30-day snapshot; no automatic dependency install, shared cache, port allocation or collision handling per workspace.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Dependency installs and service ports are left to the agent and repo.
10 atomic answers
Dependencies [unsupported] Searched worktree creation (api/session_verbs.rs) and docs for dependency/node_modules setup: none; agents install their own. Sources: amux-mixpeek:sessionverbs.
Caches [unsupported] No shared cache or node_modules reuse across workers found. Sources: amux-mixpeek:sessionverbs.
Snapshots [partial] Cloud: Hetzner daily backups (last seven) and cancellation snapshot; no workspace snapshots. Sources: amux-mixpeek:privacy.
Services [partial] Apps tab shares local apps; no dev-service orchestration. Sources: amux-mixpeek:selfhost.
Cards carry turn, time and spend budgets with a repeat breaker (contract rule 6, scaffold), usage budgets stop new lead turns, provider usage-limit windows hold delivery until reset, vault spend caps are hard; enforcement for ordinary workers is soft.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Budgets and the repeat breaker are tracked as vendor contract rules behind preferences; per-session token limits are not hard stops.
8 atomic answers
Time limits [partial] Card time budgets move cards to needs-split (docs/orchestration-contract.md rule 6). Sources: amux-mixpeek:orch.
Turn limits [partial] Turn budget per card in the same contract; Claude max turns via flags. Sources: amux-mixpeek:orch.
Spend limits [supported] Vault spend_limits_usd are hard caps (api/vault_spend.rs); project usage budgets stop new lead turns. Sources: amux-mixpeek:vaultspend, amux-mixpeek:leadmode.
Provider failures [supported] Provider usage limits are told apart from crashes and stalls; delivery held and resumed. Sources: amux-mixpeek:limitresume, amux-mixpeek:orch.
Request log, per-worker logs, trace archive, audit timeline, stall vocabulary with structured waits, daily token stats and usage windows; board and worker state reconcile against backend reality at startup.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Usage export and per-project statistics are partial; figures are not benchmarked here.
Per-session daily token totals, Claude/Codex/Gemini plan usage windows (percent of plan, not dollars), per-account Claude usage history; no per-card dollar cost, child or epic aggregation, or budget alerts.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Subscription marginal cost is shown as plan usage, never as dollars; no per-task dollar roll-up.
14 atomic answers
Task cost [unsupported] Searched api/stats.rs, api/usage.rs, board.rs for cost per card: only token totals per session. Sources: amux-mixpeek:stats, amux-mixpeek:usage.
Session cost [partial] Token usage per session/day (api/stats.rs). Sources: amux-mixpeek:stats.
Child cost [unsupported] No child rollup found. Sources: amux-mixpeek:stats.
Epic cost [unsupported] No epic cost aggregation found. Sources: amux-mixpeek:stats.
Harness aggregation [partial] Usage meter lists providers side by side, not summed. Sources: amux-mixpeek:usage.
Billed vs estimated [partial] Plan-percent windows and tokens; no billed amounts. Sources: amux-mixpeek:usage.
Tokens [supported] Input/output/amux tokens per day. Sources: amux-mixpeek:stats.
No product-level concurrency cap, but a host guard computes machine pressure, backs automation off and lowers priority of strained processes, workers are CPU/RSS sampled, one-writer-per-worktree queues tasks, and the land queue serializes merges with composed-tree verification and bisect.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Check reuse/deduplication across epics is not implemented for user repos.
12 atomic answers
Concurrency [partial] No fixed cap; project tasks run one at a time per project (docs/project-single-worktree.md). Sources: amux-mixpeek:singleworktree.
Organization members can be invited by email to the server (Cloud Solo and up), see the same dashboard, and message non-isolated workers with a member-stamped origin; messages and card logs act as discussion; presence is limited and there is no co-prompting ordering UI.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No real-time presence or cursor-level co-steering; the host must stay online (self-hosted) or the Cloud server runs.
11 atomic answers
Visibility [supported] Org members share one dashboard and board on the same server (api/org.rs). Sources: amux-mixpeek:org, amux-mixpeek:pricing.
Comments [partial] Card log entries and messages, no comment threads found. Sources: amux-mixpeek:schema.
Presence [partial] Presence endpoint tracks where a viewer is (/api/presence/where, app.js:14181); no live presence indicators documented. Sources: amux-mixpeek:org.
Coprompting [supported] A member’s send to a non-isolated worker is delivered with a member stamp, as the owner’s is (docs/orchestration-contract.md). Sources: amux-mixpeek:provenance, amux-mixpeek:org.
Ordering [unknown] Delivery at turn boundaries is queued, but ordering between simultaneous senders is not documented.
Single workspace with owner, admin and member roles, email invites and a membership lifecycle; admin can manage vault secrets; Tailscale identity sign-in for invited tailnet members; no SSO/SAML/SCIM, no per-project or per-task roles.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Project roles [unsupported] Searched org.rs and app.js for project/group roles: group-scoped admin refused (org.rs:2712); no project roles. Sources: amux-mixpeek:org.
Task roles [unsupported] No task-level roles; card owner/reviewer fields are assignments not permissions. Sources: amux-mixpeek:schema, amux-mixpeek:org.
Membership [supported] Invites, invite URLs and member admin promotion (api/org.rs). Sources: amux-mixpeek:org.
Sso [unsupported] Searched crates for sso/saml/oidc/scim: one unrelated hit in api/browser.rs; no enterprise SSO. iOS app has Sign in with Apple (privacy). Sources: amux-mixpeek:org, amux-mixpeek:privacy.
Provisioning [unsupported] No SCIM or directory provisioning found. Sources: amux-mixpeek:org.
Approvals appear as Needs-you cards: held outbound email, spend grants, publish requests, owner-gated lands and capability asks; grants are time-limited and exact-change bound; vault spend caps are hard; agents may run in bypass (yolo) mode by default unless sandboxed.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Command/tool approval inside an agent CLI is the CLI’s own prompt surfaced via needs-input; default registration examples use --yolo.
14 atomic answers
Command [partial] Agent permission prompts are surfaced in the Needs-input queue and phone; each CLI enforces its own command policy. Sources: amux-mixpeek:needsinput.
Tool [partial] OpenCode permission asks answered by amux policy (boundaries.toml); other CLIs prompt themselves. Sources: amux-mixpeek:providercsv.
Network [unknown] No network approval flow documented in the sandbox module.
Secret [supported] Vault items require approval above max_usd_without_approval; credentials stay with the server. Sources: amux-mixpeek:vaultspend, amux-mixpeek:caps.
Approver identity [supported] Resolved with the caller’s proven identity, no peer text counts (api/grants.rs, approval_cards.rs). Sources: amux-mixpeek:grants, amux-mixpeek:approvalcards.
Lifetime [supported] Grants expire after GRANT_TTL_S and say so (api/grants.rs); standing approvals are explicit records. Sources: amux-mixpeek:grants, amux-mixpeek:standing.
Tunnels [partial] Public app links and ChatGPT relay can be stopped from the dashboard (api/tunnel.rs). Sources: amux-mixpeek:privacy.
Defaults [partial] Docs quick start registers with --yolo; bypass flags run in the CLI sandbox on contract lanes. Sources: amux-mixpeek:docsite, amux-mixpeek:orch.
Enforcement [partial] Server-enforced for money, email and owner-gated lands; model instructions are not treated as enforcement. Sources: amux-mixpeek:orch, amux-mixpeek:landapprovals.
Request log, per-worker audit timeline, card logs with revisions, message history with provenance stamps, config/move export bundles; request-log retention defaults to 14 days; history is editable by the owner and has no tamper-evidence.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No audit-integrity or retention guarantee beyond local database and logs.
11 atomic answers
Actions [supported] api/audit.rs timeline from tool events, browser events and API requests. Sources: amux-mixpeek:audit.
Review column and reviewer field on cards, a dashboard git diff view per worker, harness-spawned reviewer for verified, project candidate verification bound to an exact commit and a Needs-you queue; no PR-comment review workflow.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Review is board- and criteria-centric; line comments and request-changes with comments are not provided.
Comments [unsupported] No inline review comments found in app.js diff view. Sources: amux-mixpeek:gitpanel.
Request changes [partial] Reviewer returns card to doing with up to three fix rounds (contract rule 3); no formal request-changes object. Sources: amux-mixpeek:orch.
A second member sees the same workers, history, board and artifacts on the shared server and can message non-isolated workers; ownership transfer is by assigning cards; model/harness can be switched mid-run; no formal handoff object.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Isolated workers accept member input as metadata only.
Context loss [partial] Worker context lives in the agent CLI conversation, which stays with the worker. Sources: amux-mixpeek:selfhost.
Harness transfer [partial] Model or provider can be switched on a running worker (FAQ); conversation transfer between different harnesses is not documented. Sources: amux-mixpeek:faq.
Diff view, card artifacts and evidence, project candidate evidence, files and generated markdown, audio recordings and browser recordings, screenshots and shared local app previews; verification evidence persisted in full; no cross-task artifact gallery.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Artifacts are attached per card or per project; a global gallery and per-revision artifact browsing are not found.
Recordings [supported] Recordings API stores audio and browser recording sessions (api/recordings.rs, recording_sessions.rs). Sources: amux-mixpeek:selfhost.
Previews [supported] Apps tab shares a local app inside amux or by public link. Sources: amux-mixpeek:selfhost.
Test outputs [supported] Verification evidence is produced by the harness and persisted in full (api/verify.rs). Sources: amux-mixpeek:verify.
Reviewer outputs [partial] Reviewer findings attach to the card; persistence beyond card log not documented. Sources: amux-mixpeek:orch.
Gallery [unsupported] Searched dashboard and API for a cross-task artifact gallery: none (board artifact verb per card). Sources: amux-mixpeek:boardguide.
Task links [supported] Card artifact verb attaches evidence to a card. Sources: amux-mixpeek:cli.
Revision links [partial] Project candidates bind to an exact commit; ordinary cards cite commits in evidence. Sources: amux-mixpeek:singleworktree.
Persistence [supported] SQLite and ~/.amux files outlive sessions. Sources: amux-mixpeek:selfhost.
Child findings [partial] Reviewer and child outputs persist on the board; fidelity not confirmed. Sources: amux-mixpeek:orch.
Prompt leakage [unknown] No documentation of whether reviewer prompts include author reasoning.
Harness-run verification by card kind (command, HTTP, file, deploy, proof), a land gate on the composed tree, harness-spawned independent reviewer for verified, and card gates that block done; policy is configured per lane and several rules roll out gradually.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Lint/type/CI checks are whatever the configured gate command runs; no persistent-spec conformance.
11 atomic answers
Tests [supported] Deterministic verifiers run commands, HTTP and file checks (orchestrator/verify.rs). Sources: amux-mixpeek:verifypipe.
Lint [partial] Run via the card or land gate command; not a built-in linter. Sources: amux-mixpeek:landqueue.
Ci [partial] Land gate runs repo hooks on the composed tree; main-CI watch script triggers reverts (scripts/main-ci-watch.sh via land_red.rs). Sources: amux-mixpeek:landqueue, amux-mixpeek:orch.
Independent review [partial] Reviewer spawned by the harness, fresh and read-only (contract rule 3; rollout per lane). Sources: amux-mixpeek:orch.
Enforced policy [partial] Enforced at board transition on lanes with the rule enabled; force bypass is logged. Sources: amux-mixpeek:orch, amux-mixpeek:boardrs.
Per-worker or per-project worktrees and branches, commits attributed to the lane, a server land queue that cherry-picks onto origin/main and pushes, conflict return to the lane, and a contribute path that sends local changes upstream as a PR; PR creation and review comments are done by agents with gh rather than a product PR object.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No product-managed PR lifecycle; the main path lands to main without PRs.
9 atomic answers
Branches [supported] Projects own one named branch (docs/project-single-worktree.md). Sources: amux-mixpeek:singleworktree.
Owner approves projects and owner-gated lands bound to one exact diff; the land queue merges to main after a gate; production change procedure gates deploys; model agents do not hold merge or kill authority by contract rule.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Enforcement applies to contract lanes; ordinary lanes can still push with their own git credentials unless the rule is enabled.
Cards link to commits through commit mentions and evidence, deploy-wake notices report live commits, delivery status moves through done and verified, retained evidence persists, red main triggers revert commits, and project approvals invalidate when the candidate changes.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No first-class PR or build artifact links on cards.
9 atomic answers
Commit links [supported] Open cards named in merged commits (api/commit_mentions.rs). Sources: amux-mixpeek:agentcommit.
Pr links [unsupported] No PR link field on cards found. Sources: amux-mixpeek:pr-merge.
Deployment links [partial] Deploy wake notifies lanes of live commits. Sources: amux-mixpeek:deploywake.
Delivery status [supported] done vs verified with evidence on the card. Sources: amux-mixpeek:boardguide.
Retained evidence [supported] Verification evidence persisted in full. Sources: amux-mixpeek:verify.
Rollback [partial] Revert commits queued on red main; no deployment rollback UI. Sources: amux-mixpeek:orch.
Revert [supported] Attributed red from one entry gets a revert commit through the land queue (docs/orchestration-contract.md). Sources: amux-mixpeek:orch.
Stale approval invalidation [supported] A new request invalidates older candidates (docs/projects-lead-mode.md); land approval is for one diff. Sources: amux-mixpeek:leadmode, amux-mixpeek:landapprovals.
Needs-you queue and Needs-input modal for triage, review column, project candidates with evidence, land queue with bisect and priority; no summaries, risk/size grouping or batch request-changes UI.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Review of many completed tasks is board-driven; no purpose-built batch review workspace.
Source-available under MIT + Commons Clause (vendor-authored terms): free to use, modify and self-host; selling amux itself is not allowed; not OSI open source. Public repo covers server, dashboard, CLI, Mac/iOS/Android apps and the hosted-tier provisioning code.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
GitHub reports the license as NOASSERTION because of the Commons Clause.
6 atomic answers
Client license [supported] Single LICENSE file: MIT with Commons Clause v1.0; licensor Mixpeek, Inc. Sources: amux-mixpeek:license.
Server license [supported] Same repository-wide license. Sources: amux-mixpeek:license.
Hosted extensions [partial] cloud/ provisioning and gateway code is in the public repo under the same license; Stripe signup and Clerk accounts are services. Sources: amux-mixpeek:cloudreadme, amux-mixpeek:license.
Source visibility [supported] Public GitHub repo mixpeek/amux. Sources: amux-mixpeek:repoapi.
Self-hosting is the whole product with no vendor service; export to a single .amuxmove.json move bundle works on every plan and imports anywhere; Cloud cancel keeps a 30-day snapshot and deletion erases it.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Updates download from GitHub; move bundle is amux-specific JSON.
Vendor dependencies [supported] Self-hosted needs no amux account; only GitHub for install and updates plus your model providers. Sources: amux-mixpeek:privacy.
Self-hosted: code, prompts and logs stay on your machine and nothing is sent to amux; agent CLIs talk to their own providers. Cloud: dedicated Hetzner server in Germany/Finland, counts-only hourly usage report, daily backups, Stripe for payment. Website uses PostHog; apps have no analytics.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer), amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Model-provider data handling is governed by Anthropic/OpenAI/Google terms, not documented by amux.
15 atomic answers
Code data [supported] Self-hosted code stays local; Cloud code stays on your server and never passes through an amux service. Sources: amux-mixpeek:privacy, amux-mixpeek:security.
Prompts [supported] Prompts never pass through an amux service (privacy policy). Sources: amux-mixpeek:privacy.
Telemetry defaults [supported] Self-hosted: none; iOS app: none; Cloud: hourly counts-only usage report on by default. Sources: amux-mixpeek:privacy, amux-mixpeek:security.
Telemetry controls [partial] Self-hosted has nothing to disable; Cloud usage report opt-out is not offered in the policy. Sources: amux-mixpeek:privacy.
Consent prompt [unknown] No first-run consent prompt documented; none needed for self-hosted.
Provider separation [supported] Policy separates amux from agent CLI providers and ChatGPT app data. Sources: amux-mixpeek:privacy.
USD monthly: Self-hosted $0; Cloud Solo $39, Team $69, Max $129 per month with dedicated servers (4/8/16 vCPU); billed monthly, cancel anytime; model usage billed by the provider; Concierge $5,000 onboarding + $5,000/month.
Scope
Surfaces: amux Cloud (vendor-run dedicated server per customer), amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted free; Cloud Solo $39, Team $69, Max $129 per month · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Taxes are not stated; Team is described for small teams without a seat count.
Public prices allow fixed-cost scenarios only: self-hosted $0 for any team size plus model costs; Cloud Solo $39 for one person, Team $69 for a small team, Max $129 for large fleets; no seat pricing; model/API costs vary by provider plan.
Scope
Surfaces: amux Cloud (vendor-run dedicated server per customer), amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No invented task costs; scenario sizing guidance is vendor opinion, not metered.
11 atomic answers
One person [supported] Self-hosted $0 or Cloud Solo $39/month plus model plan. Sources: amux-mixpeek:pricing.
Two people [partial] Team $69/month or self-hosted; amux does not price per collaborator. Sources: amux-mixpeek:pricing.
Five people [partial] Team $69 or Max $129 by server size; no per-seat price. Sources: amux-mixpeek:pricing.
Task assumptions [unknown] No standard task assumptions published.
Concurrency [partial] Plan sizes imply capacity but no worker count per plan is stated. Sources: amux-mixpeek:pricing.
Tokens [unknown] Token usage depends on provider and is not priced by amux.
Compute hours [supported] Cloud servers run 24/7 at flat monthly price. Sources: amux-mixpeek:pricing.
Fixed cost [supported] Cloud plan fee; self-hosted $0. Sources: amux-mixpeek:pricing.
Variable cost [supported] Model provider usage only. Sources: amux-mixpeek:pricing.
Included cost [supported] Server compute and storage included in Cloud plans. Sources: amux-mixpeek:pricing.
Unknown cost [partial] Provider subscriptions and API usage unknown without a workload. Sources: amux-mixpeek:pricing.
Pre-1.0 numbering (v0.9.108 July 2026) with continuous main-branch shipping (about 1,900 commits in the month to 2026-11-16), rolling Mac asset release, App Store iPhone/iPad app; support via GitHub issues and email; no response-time commitments; Homebrew and PyPI channels retired.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer), amux iPhone and iPad app (WKWebView wrapper) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Mac app not notarized; amux Cloud commits no uptime or support SLA on the pages checked.
Response commitments [unsupported] None stated on pricing, security or privacy pages; SECURITY.md promises acknowledgement within a few business days only. Sources: amux-mixpeek:securitymd.
Release activity [supported] About 1,900 commits in 30 days on main. Sources: amux-mixpeek:repoactivity.
Status history [unknown] No public status page located at amux.io or in the repo.
Deprecation [supported] Homebrew and PyPI channels retired; Python server removed at 792ce1f; legacy port 8822 countdown. Sources: amux-mixpeek:selfhost, amux-mixpeek:faq.
Export options [supported] Move bundle export on every plan. Sources: amux-mixpeek:movebundle.
amux states it holds no security certifications and has had no third-party audit (security page updated 2026-10-21); no ISO or SOC 2 scope exists to record.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Vendor statement dated 2026-10-21; certifications may change later.
9 atomic answers
Iso scope [unsupported] Security page: no security certifications. Sources: amux-mixpeek:security.
Self-hosted is free forever with every feature; amux Cloud has no trial or free tier; evaluation of always-on, phone access and team invites works free via self-hosting plus Tailscale; model costs separate.
Scope
Surfaces: amux server and web dashboard/PWA (self-hosted Rust + SQLite, tmux workers), amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Always-on remote work without a laptop needs Cloud (paid) or your own always-on machine.
Transparent: public USD monthly prices with server specs for each plan, no overages or markups stated, model usage billed by provider, cancel anytime, Concierge prices published.
Scope
Surfaces: amux Cloud (vendor-run dedicated server per customer) · Version: default-branch commit fdb1f71 (2026-11-16); latest numbered release v0.9.108 (2026-07-13); rolling desktop-latest release assets (2026-10-19) · Plan: Self-hosted (free, MIT + Commons Clause); amux Cloud Solo/Team/Max for the hosted surface · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Claude Code, Codex, Gemini CLI, OpenCode and Ollama run side by side; native iPhone/iPad app and Mac app (not notarized); PWA on Android; phone can watch, steer, approve and answer prompts; server does not restart a crashed agent; source-available, not OSI open source.
Kind
documented
Locator
Which agents and models; Is there an iPhone, iPad or Mac app; Can I use amux from my phone; Is it secure; What happens when an agent crashes
Self-hosted free forever with every feature; Cloud plans are paid from the start, billed monthly, no free trial; model usage billed by the provider; Concierge $5,000 one-time plus $5,000/month.
Kind
documented
Locator
Self-hosted $0; Cloud Solo $39, Team $69, Max $129; Concierge; Questions
Self-hosted: no telemetry, no accounts, code never passes through an amux service; iOS app is a thin WKWebView wrapper with no analytics; Cloud: dedicated Hetzner server, hourly counts-only usage report, 7 daily backups, 30-day snapshot after cancel, deletion erases everything.
Kind
documented
Locator
Self-hosted amux; amux iOS app; amux Cloud; Data retention
Rules 1-8: frozen acceptance criteria, server-granted done, spawned reviewer for verified, one writer per worktree, land queue, budgets, fresh session per card
States amux holds no security certifications and has had no third-party audit; Cloud servers are dedicated Hetzner machines with a sign-in gate, three open ports and hourly self-updates; amux can reach hardware via Hetzner console.
Kind
documented
Locator
Short answer; amux Cloud; What the amux team can technically reach; Backups and deletion
mixpeek/amux had 562 stars on 2026-11-16; GitHub reports no SPDX license (NOASSERTION); description names Claude Code, Codex and Gemini CLI, native iPhone/iPad/Mac apps, Rust + SQLite, Tailscale and amux Cloud.