50 of 51 criteria have a sourced finding; 48 were also cross-checked by a second agent. Every comparison that includes workmux 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.
Terminal-native access: macOS/Linux CLI plus tmux dashboard TUI and sidebar pane; kitty/WezTerm/Zellij backends experimental. No desktop GUI, mobile apps, browser client, or editor extensions. Windows explicitly unsupported.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Only the cited atomic findings are established; no hands-on client matrix was run.
Windows is explicitly unsupported; no mobile, browser, or editor-extension clients exist in the documented inventory.
9 atomic answers
Desktop os [partial] Prebuilt binaries for macOS (Apple Silicon/Intel) and Linux (x86_64/ARM64); Homebrew on macOS/Linux. Windows is explicitly unsupported. Sources: workmux:update, workmux:kitty.
Mobile apps [unknown] Client access, mobile_apps: checked official docs (llms-full.txt, 2026-11-12), docs site navigation and sitemap, CLI command inventory; no installable mobile apps found.
Browser [unknown] Client access, browser: checked official docs (llms-full.txt, 2026-11-12), docs site navigation and sitemap, CLI command inventory; no browser client found.
Mobile browser [unknown] Client access, mobile_browser: checked official docs (llms-full.txt, 2026-11-12), docs site navigation and sitemap, CLI command inventory; no mobile browser client found.
Cli [supported] Documented command reference pages plus additional CLI-only commands (setup/send/wait), covering add/merge/status/list/dashboard/sidebar/remote/... on macOS/Linux. Sources: workmux:commands.
Editor extensions [unknown] Client access, editor_extensions: checked official docs (llms-full.txt, 2026-11-12), docs site navigation and sitemap, CLI command inventory; editors run as configured panes but no workmux editor extensions found.
Notifications [partial] Merge completion can raise a system notification (--notification); waiting/done surfaced via status icons, dashboard priority sort, and last-done jump. No general push notifications. Sources: workmux:cmd-merge, workmux:dashboard, workmux:status.
Cross device continuity [partial] Remote agents survive laptop sleep/network loss with automatic window reconnect on return; moving the same task to a different device is not documented. Sources: workmux:remote.
Eleven built-in harnesses (claude, codex, copilot, opencode, gemini, agy, kiro-cli, vibe, pi, omp, grok) launched as installed CLIs with prompt injection and status hooks; global named profiles allow custom commands/env; multi-harness layouts documented but not observed here.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Model-provider choice is inherited from each harness; no provider catalog was established.
Mixed-harness operation is documented (multi-agent generation, mixed layouts) but no two-harness run was observed in this pass.
5 atomic answers
Harnesses [supported] Built-in: claude, codex, copilot, opencode, gemini, agy, kiro-cli, vibe, pi, omp, grok; status matrix confirms 9 with hook support, Kiro/Vibe referenced as agent commands. Sources: workmux:agents, workmux:status.
Model providers [unknown] Agent and model choice, model_providers: workmux inherits providers from harnesses; no provider catalog found in checked docs.
Custom adapters [supported] Global named agents define type/command/args/env (incl. from_env), e.g. proxy and multi-account profiles; project configs reference but cannot define them. Sources: workmux:agents.
Mixed harness operation [partial] Multi-generation (-a claude -a gemini) and layouts mixing agents per pane are documented; no mixed-harness run was observed in this pass. Sources: workmux:agents.
Bring your own agent subscriptions and logins: local runs reuse installed CLI logins; remote login executes each agent native login flow. No workmux account, credits, or local-model route; agent switching via named profiles.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
API-key and local-model routes were not established beyond proxy-style env examples.
No vendor billing exists, so credits/overage behavior is not applicable.
7 atomic answers
Agent subscriptions [supported] No workmux account or tokens: local agents run as installed CLIs under existing logins; remote login runs native flows (claude auth login, codex login, ...). Sources: workmux:remote-logins, workmux:install.
Api accounts [unknown] Subscriptions, api_accounts: named-agent env examples show proxy use, but a BYO API-key route is not documented as such.
Vendor credits [unknown] Subscriptions, vendor_credits: the product has no billing, so no credit route exists to document.
Local models [unknown] Subscriptions, local_models: no local-model route found in checked docs.
Account switching [supported] Multiple Claude configs via named agents (CLAUDE_CONFIG_DIR) or direnv; per-project agent selection via config or -a flag. Sources: workmux:claude, workmux:agents.
Vendor account requirement [supported] No workmux account, signup, or payment exists: install the binary and run. Agent-side logins are the only accounts involved. Sources: workmux:install.
Provider restrictions [supported] Documented minimums: Codex 0.156+, Copilot CLI 0.0.422+ (waiting needs 1.0.18+), Zellij 0.44.1+, glab 1.37+, tmux 3.3+ on remotes, Apple Container on macOS 26+ Apple Silicon. Sources: workmux:status, workmux:cmd-add, workmux:remote-setup, workmux:zellij.
Install binary, optional init, then workmux add; works with local Git (local-state main detection) and hosted remotes (fetch refs, PR checkout). Requires an existing Git repo and tmux; no managed cloud exists; BYO-server onboarding via setup/doctor/login is experimental.
Remote-server onboarding is explicitly experimental.
Behavior in a non-Git directory and managed-cloud setup (no such offering) bound the result; see atoms.
7 atomic answers
First task setup [supported] Install (script/brew/cargo/mise/nix), optional workmux init, then workmux add creates branch+worktree+window+panes and starts the agent. Sources: workmux:install, workmux:quickstart.
No git [unknown] Onboarding, no_git: worktrees presuppose a repository; no non-Git project flow is documented.
Local git without remote [supported] Local-state main-branch detection without fetching; local merge and cleanup need no remote (remove --gone is the only remote-dependent cleanup). Sources: workmux:cmd-merge, workmux:config, workmux:workflows.
Hosted git [supported] Remote/fork refs auto-fetched; add --pr checks out GitHub PRs or GitLab MRs; PR-based flow pushes and cleans up after remote merge. Sources: workmux:cmd-add, workmux:workflows.
Prerequisite guidance [partial] Requirements stated (Git 2.5+, tmux or alternatives; remote checklist plus doctor with per-check fixes). No local pre-flight beyond quickstart. Sources: workmux:quickstart, workmux:remote-setup, workmux:cmd-remote.
Managed cloud setup [unsupported] No vendor cloud exists: placement is only local or user-owned remotes; installation offers only self-run binaries. Sources: workmux:config, workmux:install, workmux:remote.
Byo vps onboarding [supported] Add SSH server to global remotes, run remote setup/doctor/login from the project; node and hooks install automatically. Experimental. Sources: workmux:remote-setup, workmux:remote, workmux:cmd-remote.
Product CLI covers create/inspect/steer/stop/review with JSON output for status/list and agent-facing ops (status/send/wait/capture/run). No REST API, SDK, MCP server, or webhooks exist in the complete command inventory and docs.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
No API/SDK/MCP-server/webhook surface: automation goes through the CLI.
No published API-stability policy beyond versioned releases and remote protocol checks.
Api [unsupported] No REST or local HTTP API in the command inventory or full docs; machine access is CLI plus --json output. Sources: workmux:commands, workmux:cmd-status.
Mcp server [unsupported] workmux exposes no MCP server; MCP appears only as agent-side config mounted into sandboxes by the underlying harness. Sources: workmux:commands, workmux:sandbox.
Webhooks [unsupported] No webhooks in the command inventory or full docs; triggers are human or agent CLI invocations. Sources: workmux:commands.
Authentication [supported] No auth for local use (runs as OS user); remote nodes use promptless SSH keys with linger; logins are per-agent credentials, not product accounts. Sources: workmux:remote-setup, workmux:remote-logins.
Stability [unknown] Programmable access, stability: versioned releases and remote protocol matching are documented, but no CLI/API stability policy is stated.
Agents extend via six product-shipped skills and status plugins; integrations are product-managed through workmux setup with scoped credential mounts. workmux itself consumes no MCP and brokers no third-party OAuth.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
MCP consumption belongs to the underlying harness; workmux only mounts agent MCP config into sandboxes.
Permission scoping is via sandbox mounts, global-only agent definitions, and agent prompts rather than a product permission matrix.
7 atomic answers
Mcp client [unsupported] workmux has no MCP client of its own; OpenCode global MCP definitions are mounted into sandboxes for the harness to use. Sources: workmux:sandbox, workmux:commands.
Plugins [supported] Status plugins: Claude marketplace plugin (raine/workmux), OpenCode plugin (v1/v2 paths), Pi and OMP extensions; installed/updated by workmux setup. Sources: workmux:status.
Custom tools [supported] Agents run product CLI ops (add/status/send/wait/capture/run/merge) via shipped skills; sandboxed coordinators reach the host through the RPC bridge. Sources: workmux:skills, workmux:skill-coordinator, workmux:sandbox.
Rust CLI/TUI binary (Cargo, edition 2024) with prebuilt macOS/Linux binaries; no Electron/Tauri/native-GUI or mobile clients.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
No desktop GUI or mobile clients exist; the client is the terminal binary plus tmux/sidebar/dashboard surfaces.
4 atomic answers
Desktop implementation [supported] Rust CLI/TUI binary (no Electron/Tauri/GUI framework); prebuilt for macOS and Linux; multiplexer backends are tmux (primary) plus experimental kitty/WezTerm/Zellij. Sources: workmux:cargo, workmux:update, workmux:kitty, workmux:zellij.
Mobile implementation [unsupported] No mobile clients in the install methods, docs, or release assets; product is terminal-only. Sources: workmux:install, workmux:update.
Hybrids [unknown] Client implementation, hybrids: no hybrid client tech beyond terminal multiplexer backends was established.
Local creation via add with prompt intake; PR/MR branch checkout (not issue import); git branches are the source of truth with branch-derived handles; PR awareness is read-only with remote cleanup.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
No Linear/Jira-style issue import or two-way sync: external import is branch checkout only.
No product-level plan editors; supported edits happen in git or the hosting UI.
9 atomic answers
Local creation [supported] workmux add creates branch + worktree + multiplexer window + panes in one command. Sources: workmux:cmd-add, workmux:quickstart.
External import [partial] add --pr checks out GitHub PRs/GL MRs (gh/glab) and remote/fork refs; no ticket import from Linear/Jira. Sources: workmux:cmd-add.
Chat git triggers [partial] Chat-triggered creation via /worktree from a running agent; no git-event triggers (pre_merge/pre_remove are lifecycle gates, not intake). Sources: workmux:skills, workmux:workflows, workmux:config.
Authoritative tracker [supported] Git branches: local machine is stated source of truth for Git; remote servers hold no origin. Sources: workmux:remote, workmux:cmd-merge.
Durable task plans do not exist in the pinned release: prompts are one-shot launch briefs written to git-excluded `.workmux/PROMPT-<branch>.md` files (prompt.rs, prompt_loader.rs, setup.rs); the state store keeps pane-level status only (state/types.rs); dashboard/sidebar show agents and worktrees, not plans. Bounded inspection of raine/workmux at e72fd59 (homebrew-workmux tap holds packaging only) for plan/acceptance/revision/spec found no plan objects, editors, revision history, or implementation links.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
7 atomic answers
Plans [unsupported] No plan objects exist: work units are git branches/worktrees created by `workmux add`; `.workmux/PROMPT-<branch>.md` files are one-shot launch briefs, not durable plans. Sources: workmux:src-plan-objects, workmux:commands.
Acceptance criteria [unsupported] No acceptance-criteria fields: prompt frontmatter parses only a `foreach` matrix (prompt.rs PromptMetadata); nothing to satisfy, gate, or verify. Sources: workmux:src-plan-objects.
Editors [unsupported] No plan editors: `-e` authors the launch prompt once; `send` and dashboard input steer the running pane, not a plan document. Sources: workmux:src-plan-objects, workmux:commands.
Revisions [unsupported] No plan revision history: the state store keeps pane status/activity timestamps only; brief files are written at creation, not versioned. Sources: workmux:src-plan-objects.
Implementation links [unsupported] No plan-to-implementation links: list rows link branch, path, and PR status (git data), not plan items. Sources: workmux:src-plan-objects, workmux:cmd-list.
Amendment [unsupported] No plan amendment surface: the brief is consumed at launch; mid-run changes go through `send` steering of the live pane. Sources: workmux:src-plan-objects, workmux:commands.
Restart persistence [unsupported] No plan persistence across restarts: `resurrect` restores windows/sessions, not plans; the brief file persists on disk in its worktree but has no revision or re-dispatch surface. Sources: workmux:src-plan-objects, workmux:commands.
Hierarchy machinery does not exist in the pinned release: work is flat branches/worktrees; `merge --into` merges into any base branch (stacked git branches, not a product hierarchy); the state store has no parent/child/blocker/dependency fields; pre_merge/pre_remove are shell lifecycle gates; coordinator merge ordering is an agent prompt convention. Bounded inspection of raine/workmux at e72fd59 for epic/hierarchy/blocker/depend/readiness found no epics, blockers, readiness gates, dependency enforcement, or mandatory workflows.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Hierarchy [unsupported] No product parent/child depth: `merge --into` targets any base branch (stacked git branches), not a product hierarchy; `--parent-session` only places a tmux window. Sources: workmux:src-hierarchy, workmux:cmd-merge.
Blockers [unsupported] No blocker objects: `blockers` appears only in skill prose as an agent triage convention, with no product record. Sources: workmux:src-hierarchy, workmux:skill-coordinator.
Readiness [unsupported] No task readiness gates: `readiness` in source is the multiplexer shell-handshake wait (handshake.rs), not dispatch gating. Sources: workmux:src-hierarchy.
Enforcement [unsupported] No dependency enforcement: pre_merge/pre_remove run configured shell hooks before merge/remove; nothing gates dispatch on blockers. Sources: workmux:src-hierarchy, workmux:config.
State propagation [unsupported] No hierarchy across which state could propagate: working/waiting/done attach to panes only. Sources: workmux:src-hierarchy, workmux:status.
Task to epic [unsupported] No epics, so no task-to-epic growth path; scope changes use rename/set_base on the same branch. Sources: workmux:src-hierarchy, workmux:commands.
Identity retention [unsupported] No task-to-epic identity to retain: branch-derived handles address work and change on rename (see PLAN-01). Sources: workmux:src-hierarchy, workmux:cmd-list.
Workflow constraints [unsupported] No mandatory workflow or preset selection: `add` accepts free-form flags and scope changes do not require recreating work. Sources: workmux:src-hierarchy, workmux:cmd-add.
Shared context and memory do not exist as a product surface in the pinned release: named-agent config and per-worktree PROMPT briefs are launch inputs, not a managed store; the config schema has no memory keys; the 6 bundled skills are static prompt files; sandbox and file seeding only mount or copy files. Bounded inspection of raine/workmux at e72fd59 for memory/instruction/provenance/retriev/index found no memory store and no scope, provenance, correction, deletion, or freshness controls.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
10 atomic answers
Instructions [unsupported] No product instruction objects: agents read repo files through their own harnesses; workmux only seeds files (copy/symlink) and injects the launch prompt. Sources: workmux:src-memory, workmux:config.
Skills [unsupported] The 6 bundled skills are static prompt files installed to agent directories (skills.rs), not a managed skill store; no scope, provenance, or freshness controls. Sources: workmux:src-memory, workmux:skills.
Project docs [unsupported] No project-doc objects: PROMPT briefs are per-task launch files, not maintained cross-session docs. Sources: workmux:src-memory, workmux:workflows.
Memory [unsupported] No memory store: the config schema has no memory keys (the only `memory` is Lima VM RAM); the state store keeps pane status only. Sources: workmux:src-memory, workmux:config.
Scope [unsupported] No store, so no scoping: file seeding is per-worktree via globs, not a cited memory scope. Sources: workmux:src-memory.
Provenance [unsupported] No provenance records: brief authorship and file origins are not tracked. Sources: workmux:src-memory.
Correction [unsupported] No correction surface for stored context beyond editing files in the repo directly. Sources: workmux:src-memory.
Deletion [unsupported] No managed deletion: brief files live and die with their worktree on remove; nothing else is retained. Sources: workmux:src-memory.
Freshness [unsupported] No staleness controls: sandbox freshness.rs concerns container images, not context freshness. Sources: workmux:src-memory.
Takeover continuity [unsupported] No product-managed continuity: branches and brief files persist on disk; conversation history lives in each harness own store, resumable same-user via --continue/--fork. Sources: workmux:src-memory, workmux:skill-coordinator.
Architecture and API awareness do not exist as a product surface in the pinned release: the only built-in model call generates branch names (llm.rs); dashboard/sidebar filters match agent/worktree names; list columns carry git/status data only. Bounded inspection of raine/workmux at e72fd59 for search/index/retriev/citation/conflict/semantic found no code search, indexing, external-knowledge retrieval, citations, conflict detection, or review-time enforcement; those belong to the launched harnesses.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
10 atomic answers
Code search [unsupported] No product code search: the only built-in model call generates branch names (llm.rs); searching code is harness behavior. Sources: workmux:src-retrieval.
Indexing [unsupported] No repository indexing in the pinned source. Sources: workmux:src-retrieval.
External knowledge [unsupported] No external-knowledge connectors: remote file seeding (files/symlink globs) copies working files, not knowledge retrieval. Sources: workmux:src-retrieval, workmux:remote-setup.
Multimodal inputs [unsupported] No product multimodal handling: the worktree skill tells agents to inspect user-supplied attachment paths as prompt text; execution belongs to the harness. Sources: workmux:src-retrieval, workmux:skills.
Freshness [unsupported] No source-freshness tracking for awareness inputs. Sources: workmux:src-retrieval.
Access scope [unsupported] No retrieval access scope: panes see the worktree checkout; sandbox mounts bound the harness, not a retrieval layer. Sources: workmux:src-retrieval, workmux:sandbox.
Api retrieval [unsupported] No API retrieval surface. Sources: workmux:src-retrieval.
Citations [unsupported] No citation mechanism for retrieved context. Sources: workmux:src-retrieval.
Conflict detection [unsupported] No architectural conflict detection: hook and grep conflicts in source are clap argument conflicts and status-cache internals, unrelated. Sources: workmux:src-retrieval.
Review enforcement [unsupported] No product review-time enforcement: pre_merge hooks run shell checks before merge but enforce no architectural consistency. Sources: workmux:src-retrieval, workmux:config.
No issue objects exist: tracking is branch/worktree-based. Worktrees persist independently of windows, carry branch/age/status metadata, and need no external tracker; idea parking, discussion, and prioritization are absent.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Workmux tracks worktrees/branches, not issues: no create/edit/discuss/prioritize/label/assign/search/filter/archive/reopen semantics.
Findings rest on the CLI command inventory and docs; no hands-on fixture was run.
17 atomic answers
Create [unsupported] No issue creation: work units are created as git branches/worktrees via add. Sources: workmux:commands, workmux:cmd-add.
Edit [unsupported] No issue editing: changes happen in git and files directly. Sources: workmux:commands.
Discuss [unsupported] No in-product discussion or comments surface in the inventory or docs. Sources: workmux:commands, workmux:dashboard.
Prioritize [unsupported] No prioritization: dashboard sorts by status/recency, not priority fields. Sources: workmux:dashboard.
Label [unsupported] No labels; branch names and project grouping are the only organizers. Sources: workmux:commands, workmux:cmd-list.
Assign [unsupported] No assignment: single-user tool with no member model. Sources: workmux:commands.
Reopen [unsupported] No reopen: resurrect restores windows, not issue states. Sources: workmux:commands.
Project epic views [unsupported] No project/epic views; Agents/Worktrees tables group by project name only. Sources: workmux:dashboard, workmux:cmd-list.
Idea parking [unsupported] No idea backlog: add -A drafts from a prompt immediately create running work, not parked ideas. Sources: workmux:workflows, workmux:cmd-add.
Explicit dispatch [unsupported] No ready/dispatch states; background creation (-b) starts work immediately. Sources: workmux:cmd-add.
Task session separation [partial] Worktree (task unit) persists independently of windows/sessions: close keeps the worktree; session mode gives each worktree its own tmux session; resurrect restores windows after crashes. Sources: workmux:commands, workmux:workflows.
Metadata [partial] Per-worktree branch, age, agent status, mux presence, unmerged marker, and PR status; no issue-grade fields. Sources: workmux:cmd-list.
Durable states [partial] Branch merged/unmerged, agent working/waiting/done/stale, and exited reasons persist across views; no issue state machine. Sources: workmux:cmd-list, workmux:status.
External tracker requirement [partial] No external tracker required: direct-merge flow stays in git; PR flow uses GitHub only for review, then remove cleans up. Sources: workmux:workflows, workmux:cmd-merge.
Agents operate shared worktree handles through documented CLI ops (add/status/send/capture/wait/run) taught by product skills; human dashboard/sidebar/list views reflect agent-created work. No issue field model, claims, attribution, or conflict handling.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Handles are branch names, not issue records: no field edits, claims, assignment, or conflict semantics.
Agent CLI surface (send/capture/wait/run) is documented in the skill, not the CLI reference; no hands-on verification here.
14 atomic answers
Shared ids [partial] Worktree handles (branch-derived, project:handle cross-project) are shared by humans and agents; they are not issue IDs with fields. Sources: workmux:skill-coordinator, workmux:cmd-status.
Read [supported] Agents read the same state via status/list (incl. --json observations with reconciliation diagnostics). Sources: workmux:skill-coordinator, workmux:cmd-status.
State changes [partial] Agent lifecycle auto-reports working/waiting/done; agents trigger merges via skill; no product state machine. Sources: workmux:status, workmux:skills.
Dependencies [unknown] Agent-native issue operations, dependencies: coordinator orders merges by plan, but no product dependency objects found.
Children [partial] /worktree spawns child worktree agents from a running agent; no persistent parent/child record beyond branches. Sources: workmux:skills, workmux:workflows.
Results [partial] Agents report via capture/output review and prompt files; no structured result fields. Sources: workmux:skill-coordinator.
Human visibility [supported] Agent-created worktrees appear in dashboard, sidebar, list, and status with the same status rendering. Sources: workmux:dashboard, workmux:sidebar, workmux:cmd-list.
Attribution [unknown] Agent-native issue operations, attribution: no attributed-change display found in checked sources.
Permissions [partial] Local OS user; sandboxed agents cross to the host only via the RPC bridge; remote actions limited to own workspace. Sources: workmux:sandbox, workmux:remote-setup.
Living product specifications do not exist in the pinned release: PROMPT briefs are per-task launch files with no cross-task persistence, revisions, approvals, retrieval, or drift detection; the state store and dashboard hold no requirement objects. Bounded inspection of raine/workmux at e72fd59 for spec/requirement/persistent/approval/drift found no product-spec surface.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
9 atomic answers
Persistent requirements [unsupported] No persistent requirements: PROMPT briefs are per-task files with no cross-task store. Sources: workmux:src-specs, workmux:workflows.
Human edits [unsupported] No spec editing surface: humans author the launch brief once via -p/-P/-e. Sources: workmux:src-specs, workmux:cmd-add.
Agent edits [unsupported] Agents write new briefs via the /worktree dispatcher flow; no persistent-requirement edits with attribution. Sources: workmux:src-specs, workmux:skills.
Revisions [unsupported] No revision history for requirements. Sources: workmux:src-specs.
Approvals [unsupported] No approval rules for requirements; merge approval is git/PR flow (see PLAN-01). Sources: workmux:src-specs.
Implementation links [unsupported] No requirement-to-task links: list rows link branch/path/PR (git data). Sources: workmux:src-specs, workmux:cmd-list.
Later retrieval [unsupported] No retrieval of past requirements in later tasks beyond files left in the repo. Sources: workmux:src-specs.
Drift detection [unsupported] No drift detection between requirements and implementation. Sources: workmux:src-specs.
Review integration [unsupported] Review is diff/PR based with no spec-conformance consideration surface. Sources: workmux:src-specs, workmux:dashboard.
Independent agents run concurrently, each in its own worktree and multiplexer window/session; --max-concurrent bounds worker pools; running/waiting/failed/finished visible across dashboard, sidebar, list, and status.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Concurrency is documented, not observed: no multi-agent run was executed in this pass.
No documented CPU/RAM quotas; throttling is count-based only.
5 atomic answers
Concurrent sessions [supported] Each worktree gets its own window (or session in session mode); multi-generation creates many at once. Sources: workmux:agents, workmux:cmd-add.
Concurrent tasks [supported] Parallel workflows: independent agents per worktree on different branches with isolated terminal state. Sources: workmux:agents, workmux:readme.
Quotas [partial] --max-concurrent limits simultaneous worktrees for worker pools; no compute quotas documented. Sources: workmux:changelog.
Observed concurrency [unknown] Coordination, observed_concurrency: no concurrent run was executed in this pass.
Agents are placed per worktree with local/remote routing and worker-pool throttling; coordinator agents delegate via skills. No human assignment, claims, queues UI, or duplicate-work prevention.
Product-shipped /coordinator and /worktree skills define a coordinator role that spawns worktree agents with prompt files, monitors via status/wait, sends follow-ups, reviews output, and merges. Mixed-harness and retained-relationship depth untested.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Delegation behavior is documented in the skill, not observed hands-on in this pass.
Cross-harness teams and persistent relationship records were not established.
12 atomic answers
Roles [supported] Coordinator (plans/delegates, does not implement) vs worktree agents, defined by /coordinator and /worktree skills. Sources: workmux:skill-coordinator, workmux:skills.
Model harness effort [partial] Named agents allow per-agent model args (e.g. pi --model) and per-pane harness choice; no effort knob documented. Sources: workmux:agents.
Results return [supported] wait (with --timeout/--any and exit codes), capture output review, then merge; resumable across interruptions. Sources: workmux:skill-coordinator.
Cross harness [partial] Multi-agent generation and mixed layouts across CLIs documented; cross-harness team behavior unverified here. Sources: workmux:agents.
Orchestration owner [supported] Product-owned: skills ship in the repo and install via workmux setup; distinct from harness-native subagents (pi-suba noted as external publisher). Sources: workmux:skills, workmux:status.
Activation [supported] Invoke /coordinator or /worktree after setup --skills; spawn with add -b -P from prompt files. Sources: workmux:skills, workmux:skill-coordinator.
Authentication [partial] Local user context; sandboxed coordinators route through the host RPC bridge; no extra auth documented. Sources: workmux:sandbox, workmux:skill-coordinator.
Retained results [partial] Prompt files, captured output, and worktree contents persist until cleanup; no structured result store. Sources: workmux:skill-coordinator.
Followup [supported] Send follow-up instructions and re-wait; /merge after review; monitoring invariant survives interruptions. Sources: workmux:skill-coordinator, workmux:skills.
Unattended triggers: the command reference pages plus additional CLI commands and the docs contain no schedules, event triggers, recurring tasks, or completion conditions; work starts from human or agent CLI invocations.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary) · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
8 atomic answers
Schedules [unsupported] No schedules: CLI command inventory has no schedule command; nothing in full docs. Sources: workmux:commands.
Events [unsupported] No event triggers: Jira-style polling and git hooks are absent; pre_merge/pre_remove are lifecycle gates. Sources: workmux:commands, workmux:config.
Recurring tasks [unsupported] No recurring tasks in inventory or docs. Sources: workmux:commands.
Completion conditions [unsupported] No completion conditions: wait/--timeout is a blocking CLI call, not a trigger. Sources: workmux:skill-coordinator.
Scheduler location [unsupported] No scheduler exists, so no location; closing the client ends nothing scheduled. Sources: workmux:commands.
Overlaps [unsupported] No scheduler, so no overlap handling. Sources: workmux:commands.
Retries [unsupported] No trigger retries; hook/install steps are idempotent on rerun (setup/add resume), not scheduled retries. Sources: workmux:cmd-remote, workmux:remote-setup.
Client independence [unsupported] Nothing runs unattended: remote agents persist while the laptop sleeps, but they were started interactively. Sources: workmux:remote.
Notifications [partial] Merge system notification; waiting/done via icons, priority sort, last-done cycling. No push or definitions of pending-decision alerts. Sources: workmux:cmd-merge, workmux:dashboard, workmux:status.
Pending decisions [supported] Waiting (permission/question) state with dashboard priority sort and last-done jump across agents. Sources: workmux:dashboard, workmux:status.
Escalation [unknown] Intervention, escalation: no escalation chain found in checked sources.
Visible errors [partial] status --json target_errors with stable codes; doctor prints per-check fixes; troubleshooting guide; silent waits untested. Sources: workmux:cmd-status, workmux:cmd-remote.
Dashboard Agents/Worktrees views plus sidebar give a filterable fleet UI with attention sorting (waiting first), timers, diff stats, and navigation. No 12-task fixture was run; parent/child links and dependency views are absent.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
No disclosed 12-state fixture run; live-agent verification absent in this pass.
No parent/child tree or dependency rendering; coordinator relationships live in prompts/branches, not the UI.
8 atomic answers
Fleet fixture [unknown] Fleet UI, fleet_fixture: no disclosed 12-state fixture run found or executed.
Parent child [partial] Tables show project/worktree/agent rows but no parent/child tree for coordinator delegations. Sources: workmux:dashboard, workmux:cmd-list.
Dependencies [unknown] Fleet UI, dependencies: no dependency rendering found in checked sources.
History [partial] Elapsed-since-change timers, session titles, git stats per row; no per-agent event history view. Sources: workmux:dashboard, workmux:cmd-list.
Workload [partial] Diff stats and multi-agent counts per worktree; no load/capacity metrics. Sources: workmux:dashboard, workmux:cmd-list.
Navigation errors [unknown] Fleet UI, navigation_errors: navigation failure behavior not documented or tested.
Fixture mode [unknown] Fleet UI, fixture_mode: no fixture run; all findings are documented capability, not live-agent evidence.
One-shot add -A and growing coordinator-led epics share the same tool; optional layouts, natural-language prompts, per-agent profiles, and mid-run steering are documented. No mandatory presets, in-run plan edits, or relationship records.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Growing-epic flow is coordinator-convention, not product-enforced hierarchy.
Retained coordinator relationships and in-run plan edits were not established.
10 atomic answers
Quick task [supported] add -A writes prompt first, generates branch name, creates worktree with agent prompt inline. Sources: workmux:workflows, workmux:cmd-add.
Growing epic [partial] Coordinator breaks plans into worktree agents, orders merges, and takes follow-ups; no epic objects or enforced stages. Sources: workmux:workflows, workmux:skill-coordinator.
Presets [partial] Named layouts and agent profiles are optional; no mandatory workflow or preset selection. Sources: workmux:agents, workmux:config.
Natural language [supported] Inline/editor/file prompts; /worktree briefs from conversation; /coordinator natural-language plans. Sources: workmux:agents, workmux:skills, workmux:cmd-add.
Agent configuration [partial] Per-pane/per-layout harness choice, -a overrides, named profiles with model args; no effort control documented. Sources: workmux:agents.
Live roles [partial] Dashboard/sidebar show live agents with titles and statuses; coordinator vs worker roles not labeled in UI. Sources: workmux:dashboard, workmux:sidebar.
Retained relationships [unknown] Workflow flexibility, retained_relationships: no persistent delegation records found.
Auth friction [supported] No accounts or approvals to configure; remotes need only SSH key + linger with doctor guidance. Sources: workmux:install, workmux:remote-setup.
Local execution plus experimental BYO-server remotes over SSH in the same views; no vendor cloud or self-hosted service. Remote agents survive laptop sleep/disconnect with auto-reconnect; other-device continuation undocumented.
Survival covers the same laptop returning; continuing from another device is not documented.
12 atomic answers
Local [supported] Local worktrees with agent panes on the user machine; default placement. Sources: workmux:quickstart, workmux:config.
Byo remote [supported] User-owned Linux servers over SSH (home box, Proxmox VM, cloud VM); user provisions, pays, and holds credentials. Sources: workmux:remote, workmux:remote-setup.
Self hosted [unknown] Execution, self_hosted: no hosted control plane exists to self-host; the remote node is an agent runner, not a service.
Managed cloud [unsupported] No vendor cloud: placement is local or user remotes only; vendor operates no compute. Sources: workmux:config, workmux:remote.
Hybrid [partial] Local and remote agents coexist in dashboard/sidebar/list/status; placement set per project or per add. Sources: workmux:remote, workmux:config, workmux:cmd-list.
Provisioning [partial] remote setup installs node + hooks; server prerequisites (SSH, linger, toolchains) are user-provisioned with doctor checks. Sources: workmux:remote-setup, workmux:cmd-remote.
Resources [partial] Container CPU/memory limits configurable; server sizing and project toolchains are user-managed. Sources: workmux:sandbox, workmux:remote-setup.
Region [unknown] Execution, region: no regions; machines are wherever the user puts them.
Expiry [partial] Remote workspaces persist (laptop may sleep); lifespan bounds undocumented; local reap-agents prunes old tracked processes. Sources: workmux:remote, workmux:commands.
Client disconnect [supported] Remote agents keep working through sleep, network loss, or closed windows; the local window reconnects by itself. Sources: workmux:remote.
Other device continuation [unknown] Execution, other_device_continuation: attaching from a second device is not documented.
Git worktree/branch file isolation plus container (Docker/Podman/Apple) and VM (Lima/Kata) sandboxes with scoped mounts and secret exclusion. Host-side git ops stay outside the boundary; hostile-code containment is explicitly disclaimed.
Documented threat model: agent edits are untrusted on rebuild; host git operations, hooks, and content filters sit outside the sandbox.
Two-change code-separation validation was not performed in this pass.
12 atomic answers
Checkout [supported] Separate directory per worktree; supplemental files via copy/symlink config. Sources: workmux:caveats, workmux:config.
Branch [supported] One branch per worktree; merge --into supports stacked/subtask branches. Sources: workmux:cmd-add, workmux:cmd-merge.
Worktree [supported] Git worktrees are the core isolation unit, each with its own window/panes. Sources: workmux:readme, workmux:quickstart.
Container [supported] Docker, Podman, and Apple Container runtimes; ephemeral sessions; OCI runtime override (Kata) for hardware VM isolation. Sources: workmux:sandbox, workmux:changelog.
Vm [supported] Lima VM backend for persistent machines with Nix/Devbox toolchains; documented reduced Git-metadata isolation acceptance. Sources: workmux:sandbox.
Os sandbox [partial] Container/VM are the product sandboxes; agent-native OS sandboxes (Claude Seatbelt/bwrap, host-exec Seatbelt/bwrap) are harnesses, not workmux enforcement. Sources: workmux:sandbox.
Filesystem [supported] Sandbox scoped to the worktree; host files and credentials stay outside; container guests cannot modify shared git config/hooks. Sources: workmux:sandbox.
Process [supported] Separate panes/processes per agent; sandboxed agents run in a separate OS instance; RPC bridge syncs host features. Sources: workmux:sandbox, workmux:quickstart.
Secrets [supported] Host SSH/AWS/credential files excluded; per-agent credential mounts; remote logins and env passthrough stored privately on the server. Sources: workmux:sandbox, workmux:remote-logins.
Code separation [partial] Worktrees isolate files, but parallel branches can still conflict on merge; best practice is logically separate features. Sources: workmux:caveats.
Security boundary [partial] Documented boundary with explicit non-goals: untrusted edits, writable worktree programs, and host-side hooks are outside; "do not use" warning for strict threat models. Sources: workmux:sandbox.
Crash recovery via resurrect, resumable remote provisioning, automatic remote reconnect, and state-file reconciliation with diagnostics; transcript resume via --continue/--fork. Multi-day continuity and loss/duplication behavior untested.
Recovery is documented, not exercised: no crash/disconnect drill was run in this pass.
Context loss, duplicate actions, and multi-day continuity were not established.
12 atomic answers
Client disconnect [partial] Remote windows reconnect automatically (typed keys during reconnect were a fixed bug); local tmux reattach is multiplexer behavior. Sources: workmux:remote, workmux:changelog.
Worker crash [partial] Dashboard/list surface exited sessions with reasons (e.g. host rebooted); interrupted-agent detection flips stale working states. Sources: workmux:cmd-list, workmux:status.
Service restart [supported] resurrect restores worktree windows after tmux/computer crash and resumes conversations; remote setup reinstalls missing nodes. Sources: workmux:commands, workmux:workflows, workmux:cmd-remote.
Expiry [partial] Remote workspaces persist without stated lifetime; reap-agents exits tracked processes older than a threshold; sandbox sessions are ephemeral vs Lima persistent. Sources: workmux:remote, workmux:commands, workmux:sandbox.
Transcript reload [partial] resurrect resumes conversations; --continue/--fork reopen harness sessions in new worktrees; harness history tools bridge projects. Sources: workmux:workflows, workmux:claude.
Process reconnect [supported] Remote window is a live view that reconnects by itself after sleep or network loss. Sources: workmux:remote.
Task resume [partial] Resume via resurrect, re-add with resume flags, and resumable remote provisioning (finished hook stages are not repeated). Sources: workmux:workflows, workmux:remote-setup.
State reconstruction [partial] status reconciles state files with multiplexer reality and reports invalid/unattributed files instead of deleting them. Sources: workmux:cmd-status.
Context loss [unknown] Recovery, context_loss: lost-context behavior after crashes was not established.
Duplicate actions [unknown] Recovery, duplicate_actions: duplicate-execution behavior was not established.
Manual repair [partial] doctor prints a fix per failing check; troubleshooting guide; invalid state files are left for operator cleanup. Sources: workmux:cmd-remote, workmux:cmd-status.
Multi day continuity [unknown] Recovery, multi_day_continuity: multi-day epic survival across compute replacement was not established.
Dependencies via hooks and pane installs, secrets via files copy, caches via symlinks, dev servers as panes, remote node checks; per-worktree installs with background cleanup. No snapshots or managed services.
Snapshots [unknown] Dev environments, snapshots: no snapshot/restore surface found in checked sources.
Services [partial] Dev servers run as configured panes; no managed service supervision (ports, health, restarts). Sources: workmux:config, workmux:quickstart.
Ports [partial] direnv guide covers port isolation; login flows forward browser ports; no automatic port management documented. Sources: workmux:config, workmux:remote-logins.
Secrets [supported] .env and credential files via files/remote_files copy; never committed; private per-server storage for remote env. Sources: workmux:config, workmux:remote-setup.
Duplicate installs [partial] Each worktree installs independently; cleanup moves node_modules aside for background deletion; sharing risks divergence. Sources: workmux:caveats.
Collisions [partial] Port-in-use and merge-conflict collisions are warned about, not auto-resolved; work logically separate features. Sources: workmux:caveats.
Remote setup [supported] setup/doctor verify git, tmux, linger, agent CLIs/Docker, hooks, and logins on a clean server, pulling the sandbox image. Sources: workmux:remote-setup, workmux:cmd-remote.
Automatic repair [partial] doctor fixes, idempotent setup, resumable provisioning; no automatic diagnosis of app dependency failures. Sources: workmux:cmd-remote, workmux:remote-setup.
Retries [partial] setup and remote provisioning are idempotent/resumable; interrupted-agent detection re-marks activity; no general retry policy. Sources: workmux:cmd-remote, workmux:remote-setup, workmux:status.
Provider failures [unknown] Limits, provider_failures: provider-failure behavior was not established.
Agent stats [partial] Per-agent status, elapsed-since-change, session title, pane, git stats; stale filtering; no aggregates. Sources: workmux:cmd-status, workmux:dashboard.
Project stats [partial] Project column/grouping and status --all across repositories; no project-level rollups. Sources: workmux:cmd-list, workmux:cmd-status.
Failure status [partial] Working/waiting/done/stale plus exited reasons shown consistently across views (per docs); reconnect consistency untested here. Sources: workmux:status, workmux:cmd-list.
Approval status [partial] Waiting state marks permission/question prompts; dashboard prioritizes them; approval vs question not distinguished. Sources: workmux:status, workmux:dashboard.
Reconnect consistency [unknown] Status, reconnect_consistency: no reconnect drill was run in this pass.
Performance method [unknown] Status, performance_method: no disclosed measurement fixture found.
Responsiveness [unknown] Status, responsiveness: no measured interaction timings found; no lag claims made.
Per-task API and compute cost visibility does not exist in the pinned release: list, status, and dashboard expose git and agent-status data only; repo-wide inspection finds no spend, token-usage, allowance, compute-fee, alert, export, or drill-down code (`token` means auth tokens, `budget` means UI widths and a transfer cap). Bounded inspection of raine/workmux at e72fd59 (src/, skills/, docs/) found no cost surface.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
14 atomic answers
Task cost [unsupported] No per-task spend: list rows show PROJECT/BRANCH/AGE/PR/AGENT/MUX/UNMERGED/PATH (git/status data), no cost. Sources: workmux:src-cost-surface, workmux:cmd-list.
Billed vs estimated [unsupported] No billed or estimated amounts: the product has no billing and reads no provider usage. Sources: workmux:src-cost-surface, workmux:install.
Tokens [unsupported] No token counts: `token` in source means auth tokens (claude setup-token, stored credentials), never usage. Sources: workmux:src-cost-surface.
Subscription allowance [unsupported] No subscription-allowance display; agent subscriptions are BYO (see ACC-03). Sources: workmux:src-cost-surface.
Provider reconciliation [unsupported] No provider reconciliation: no usage import or export. Sources: workmux:src-cost-surface.
Compute cost [unsupported] No compute fees: placement is local or the user own servers; `budget` in source means UI widths and a 64 MiB transfer cap. Sources: workmux:src-cost-surface, workmux:remote-setup.
Drilldown [unsupported] No drill-down from statistics to cost: statistics are agent-status counts by task/project. Sources: workmux:src-cost-surface, workmux:dashboard.
Live human collaboration does not exist in the pinned release: a single-user local binary with no accounts, shared links, discussion, presence, or co-prompting; the dashboard `comment` action steers the operator own agent pane (diff_ops.rs). Bounded inspection of raine/workmux at e72fd59 for collaborat/multi-user/presence/co-prompt/share/sso found no collaboration surfaces.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
11 atomic answers
Visibility [unsupported] No shared visibility: dashboard/sidebar/list are same-machine local views over local JSON state; no accounts or shared links. Sources: workmux:src-collab, workmux:dashboard.
Comments [unsupported] Dashboard `comment` (diff_ops.rs send_hunk_comment) pastes a hunk-annotated message into the operator own agent pane: single-user steering, not human comments. Sources: workmux:src-collab.
Presence [unsupported] No presence: no users, sessions-by-person, or online indicators. Sources: workmux:src-collab.
Coprompting [unsupported] No simultaneous co-prompting: one operator per pane; `send` targets the local pane. Sources: workmux:src-collab, workmux:commands.
Ordering [unsupported] No multi-user input ordering: no concurrent inputs to order. Sources: workmux:src-collab.
Conflicts [unsupported] No conflict handling for co-prompting: none exists. Sources: workmux:src-collab.
Attribution [unsupported] No attribution: no second actor exists to attribute. Sources: workmux:src-collab.
Permissions [unsupported] No collaboration permissions: single OS user; sandbox mounts bound the harness, not people. Sources: workmux:src-collab, workmux:sandbox.
Plan restrictions [unsupported] No plans or tiers: the binary has no accounts, so no team or free-tier restrictions. Sources: workmux:src-collab, workmux:install.
Owner online [unsupported] No collaboration session exists to require the owner: remote agents outlive laptop sleep for the same user, which is continuity, not co-presence. Sources: workmux:src-collab, workmux:remote.
Roles and access boundaries do not exist in the pinned release: no accounts, organizations, roles, membership, SSO, or provisioning; the product runs as the local OS user and remote credentials are the single user SSH keys and agent logins. Bounded inspection of raine/workmux at e72fd59 for sso/organization/role/acl/member found no role or access-boundary enforcement.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Unauthorized access [unsupported] No access-control model: single OS user; sandbox mounts restrict harness files, not human roles. Sources: workmux:src-access-model, workmux:sandbox.
Approvals are agent-level (permission prompts, yolo opt-outs) with the sandbox as the product-enforced boundary; pre_merge hooks gate merges; login-time port forwarding is the only temporary access. No approver identities, lifetimes, or revocation model.
Product enforcement is the sandbox boundary plus user hooks; prompt-following behavior belongs to harnesses.
No named approvers, scoped lifetimes, or revocation flow documented.
14 atomic answers
Command [partial] Agent command prompts (Claude/Codex) with yolo bypass via named agents; sandboxed panes replace prompts with the boundary. Sources: workmux:claude, workmux:sandbox.
Tool [partial] Tool-use prompts surface as waiting state; same bypass/boundary mechanics as commands. Sources: workmux:status, workmux:sandbox.
Revoke [unknown] Approvals, revoke: revocation of granted access not documented (reap-agents kills processes only).
Tunnels [partial] Login browser flows use temporary localhost port forwarding; no general tunnel sharing documented. Sources: workmux:remote-logins.
Defaults [partial] Prompts on by default; yolo opt-in per agent; sandbox disables prompts relying on boundary instead. Sources: workmux:claude, workmux:sandbox.
Safer modes [supported] Sandbox container/VM modes; shared-permission symlinks vs yolo choice for Claude. Sources: workmux:sandbox, workmux:claude.
Enforcement [partial] Sandbox boundary and user hooks are enforced; prompt compliance is harness behavior. Sources: workmux:sandbox, workmux:config.
History lives in git (commits, branches) plus worktree metadata, dashboard diffs, and machine-readable status JSON. No decision records, comments, cross-user persistence, export feature, or integrity model.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
No audit vocabulary is warranted: no retention, integrity, or tamper model documented.
Machine-readable outputs exist, but no history export feature.
11 atomic answers
Actions [partial] Git history plus agent activity visible in dashboard preview; no attributed product action log. Sources: workmux:dashboard, workmux:cmd-merge.
Approvals [unknown] History, approvals: no approval records; merges are local git operations.
Edits [partial] Edits persist as commits; uncommitted changes visible in diff views and list markers. Sources: workmux:dashboard, workmux:cmd-list.
Discussion [unknown] History, discussion: no in-product discussion or comments.
Decisions [unknown] History, decisions: no decision-link records found.
Cross user persistence [unknown] History, cross_user_persistence: single-user tool; no second-user persistence surface.
Cross session persistence [partial] Worktree git history and PROMPT files persist across windows/sessions until cleanup. Sources: workmux:workflows, workmux:commands.
Export [partial] status/list --json and git log provide machine-readable history; no dedicated export feature. Sources: workmux:cmd-status, workmux:cmd-list.
Mutability [unknown] History, mutability: alteration rules for history not documented.
Retention [unknown] History, retention: retention windows unstated (log retention, reap-agents pruning noted without schedule).
Integrity [unknown] History, integrity: no integrity model; the word audit is not used in checked sources.
Effort [unknown] Review, effort: no steps/time measurements found.
Missed evidence [unknown] Review, missed_evidence: no fixture run to assess missed evidence.
Keyboard [supported] Full keybindings (jump/diff/input/sort/filter/commit/merge/kill/sweep/palette) plus optional mouse. Sources: workmux:dashboard.
Narrow screen [unknown] Review, narrow_screen: narrow-screen usability not documented or tested.
Context switching [supported] Numbered jump, toggle last agent, session filter, cross-project handles keep review context per worktree. Sources: workmux:dashboard, workmux:skill-coordinator.
Roles [partial] Titles and agent kinds identify who did what; coordinator/worker roles not labeled in UI. Sources: workmux:dashboard, workmux:cmd-status.
Retained context [partial] Worktree retains diffs, preview, and prompts until cleanup; removal deletes review context. Sources: workmux:dashboard, workmux:workflows.
Colleague takeover does not exist in the pinned release: a single-user tool with no second-user, ownership-transfer, or attribution surfaces; same-user resume (--continue/--fork, resurrect) is explicitly not full takeover. Bounded inspection of raine/workmux at e72fd59 for takeover/handoff/colleague/ownership found no handover surfaces; artifacts move only through git and the filesystem.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-13
12 atomic answers
Ongoing takeover [unsupported] No second-user takeover: no accounts, ownership transfer, or attribution surfaces. Sources: workmux:src-takeover, workmux:commands.
Same task [unsupported] A colleague cannot open the same task: handles address local worktrees with no shared identity layer. Sources: workmux:src-takeover.
Session history [unsupported] Session history (pane transcripts, status) is local to the machine; no product surface shares it with another person. Sources: workmux:src-takeover.
Decisions [unsupported] No decision records to hand over: merge and dispatch choices live in git and skill prompts, not product objects. Sources: workmux:src-takeover, workmux:skill-coordinator.
Artifacts [unsupported] Artifacts (branches, files, diffs) are shared only through git and the filesystem, not product takeover. Sources: workmux:src-takeover, workmux:workflows.
Permissions [unsupported] No permissions to transfer: single OS user. Sources: workmux:src-takeover.
Runtime context [unsupported] Runtime context (panes, sessions, remote windows) is local to the operator machine and remotes; no reattachment by another person. Sources: workmux:src-takeover, workmux:remote.
Owner disconnect [unsupported] Owner disconnect has no handover semantics: same-user windows reconnect; nothing transfers. Sources: workmux:src-takeover.
Ownership [unsupported] No ownership records: no assignment, claims, or transfer operations. Sources: workmux:src-takeover.
Attribution [unsupported] No attribution: single actor, no multi-author history. Sources: workmux:src-takeover.
Context loss [unsupported] No product-managed handover, so nothing is preserved or reported as lost at the product layer; git state persists. Sources: workmux:src-takeover.
Harness transfer [unsupported] No product transfer between harnesses: --continue/--fork resume the same harness conversation from its own store (per-harness forkers); a different agent requires a new worktree via -a. Sources: workmux:src-takeover, workmux:cmd-add.
Diff/patch review with file navigation, live terminal previews, PR links, and post-merge cleanup; prompt files and logs persist until removed. No artifact gallery, recordings, revision pinning, or leak analysis.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Retention ends at cleanup: removal deletes the worktree and its review context.
Reopening findings relies on harness history and git, not a product gallery.
13 atomic answers
Diffs [supported] Dashboard diff view with syntax highlighting; list shows per-worktree diff stats; WIP vs committed toggle. Sources: workmux:dashboard, workmux:cmd-list.
Documents [unknown] Artifacts, documents: no document gallery found.
Screenshots [unknown] Artifacts, screenshots: no screenshot artifacts surface found.
Recordings [unknown] Artifacts, recordings: no recordings surface found.
Previews [partial] Live terminal preview per agent; dev servers run as panes for manual preview; no hosted previews. Sources: workmux:dashboard, workmux:config.
Test outputs [partial] Test runs visible in agent preview/output; no retained test-report artifacts. Sources: workmux:dashboard.
Reviewer outputs [unknown] Artifacts, reviewer_outputs: no retained reviewer-report store found.
Task links [partial] Worktree rows link branch, PR number/checks, and agent status; no task-registry links. Sources: workmux:dashboard, workmux:cmd-list.
Revision links [unknown] Artifacts, revision_links: no exact-revision pinning found.
Persistence [partial] Evidence persists while the worktree lives; remote merge brings work home before cleanup. Sources: workmux:workflows, workmux:remote.
Child findings [unknown] Artifacts, child_findings: reopening completed child findings relies on harness history, not product retrieval.
Prompt leakage [unknown] Artifacts, prompt_leakage: no analysis of internal prompts leaking into outputs found.
User-configured hooks and panes run tests/lint/types/CI with pre_merge abort; coordinator and human diff review act as independent review. No built-in gates, required checks, or spec conformance.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
All verification is user-configured; the product ships no default required checks.
An agent saying checks passed is not a gate: only hook exit codes and human review enforce.
11 atomic answers
Tests [partial] Tests run via post_create hooks or dev panes; status preview shows results; user-configured only. Sources: workmux:config, workmux:dashboard.
Lint [partial] Lint runs the same way via hooks/panes; no built-in lint gate. Sources: workmux:config.
Types [partial] Type checks via hooks/panes; no built-in gate. Sources: workmux:config.
Ci [partial] CI status surfaces via PR checks columns; CI itself runs on the host, not in-product. Sources: workmux:cmd-list, workmux:dashboard.
Independent review [partial] Coordinator reviews output before merging (/coordinator, /merge); human reviews diffs; neither is a blocking gate by default. Sources: workmux:skills, workmux:dashboard.
Spec checks [unknown] Verification, spec_checks: no living specs exist, so no conformance checks.
Required checks [partial] Required only where the user configures pre_merge hooks; nothing required out of the box. Sources: workmux:config.
Failure blocking [partial] pre_merge hook failure aborts the merge; agent/test failures without hooks do not block. Sources: workmux:config.
Requirement conflicts [partial] /merge reviews base-branch changes before resolving conflicts; no requirement registry to conflict against. Sources: workmux:skills.
Configured policy [partial] Policy is the user .workmux.yaml hooks plus merge_strategy/merge_keep; no organizational policy layer. Sources: workmux:config.
Enforced policy [partial] Hook exit codes and the sandbox boundary are enforced; review compliance is conventional. Sources: workmux:config, workmux:sandbox.
Branch/worktree lifecycle with agent-driven commits, rebase command + skill with conflict intelligence, PR checkout/creation flow via gh, PR-check surfacing, and post-merge cleanup. No inline review comments or product-owned PR state.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Commits and PR creation are agent/CLI-assisted, not product-native operations.
Review comments and CI responses live in the hosting UI; workmux surfaces awareness only.
9 atomic answers
Branches [supported] Per-worktree branches with --base, fork refs, rename, and stacked --into merges. Sources: workmux:cmd-add, workmux:cmd-merge.
Worktrees [supported] Full lifecycle: add/open/close/resurrect/sync-files/remove with file ops and hooks. Sources: workmux:commands, workmux:workflows.
Commits [partial] Agents commit via /merge skill; dashboard commit action configurable; product CLI itself does not author commits. Sources: workmux:skills, workmux:dashboard.
Pull requests [partial] add --pr checks out PRs/MRs; /open-pr drafts and opens gh creation in browser without creating directly; remove --gone after merge. Sources: workmux:cmd-add, workmux:skill-openpr, workmux:workflows.
Comments [unknown] Git workflow, comments: no PR comment surface in product; review happens in hosting UI.
Ci response [partial] PR check status shown in dashboard/list columns with browser links; no in-product CI actions. Sources: workmux:cmd-list, workmux:dashboard.
Rebase [supported] rebase command plus /rebase skill with target flexibility and smart conflict resolution. Sources: workmux:commands, workmux:skills.
Conflicts [partial] /merge reviews both sides and resolves; plain CLI merge leaves git conflicts to the operator/agent. Sources: workmux:skills, workmux:caveats.
Product state [partial] Branch/worktree/mux state tracked (merged/unmerged, open/closed); PR state is read-only awareness. Sources: workmux:cmd-list, workmux:cmd-status.
The local user approves and merges (merge/rebase/squash strategies, --into targets, keep controls); pre_merge hooks gate merges. No release pipeline, deployment authority, or multi-party approval.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Single-user authority: no approver roles or deployment targets.
Exact-revision guarantees are git semantics; no product revision pinning.
6 atomic answers
Approve [partial] The local user approves by running merge or pushing the PR; no approval workflow or quorum. Sources: workmux:cmd-merge, workmux:workflows.
Merge [supported] workmux merge with merge/rebase/squash strategies, --into targets, --keep controls, and cleanup. Sources: workmux:cmd-merge.
Release [unknown] Delivery, release: no release pipeline surface found.
Deploy [unknown] Delivery, deploy: no deployment authority surface found; dev servers are manual panes.
Exact revision [partial] Merges the current branch tip; --keep allows verify-after-merge; no revision pinning or approval invalidation. Sources: workmux:cmd-merge.
Branch-to-PR links with check status, merge-then-cleanup delivery states, sweep staleness reasons, and git/log/prompt evidence until cleanup. No rollback/revert commands and no stale-approval model.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Undo is manual git (revert/reflog), not a product operation.
Delivery status ends at merge/cleanup; deployments are out of scope.
9 atomic answers
Commit links [partial] Branch/commit relationship is git-native and visible in diffs; no product commit-link registry. Sources: workmux:dashboard.
Pr links [partial] PR numbers, titles, closing-issue refs, and check status shown per worktree with browser links. Sources: workmux:cmd-list, workmux:dashboard.
Build links [unknown] Completion, build_links: no build-system links found.
Deployment links [unknown] Completion, deployment_links: no deployments exist to link.
Retained evidence [partial] Diffs, PROMPT files, logs, and git history retained until worktree removal. Sources: workmux:dashboard, workmux:workflows.
Rollback [unsupported] No rollback support: the command inventory has no rollback or undo operation; recovery is manual git. Sources: workmux:commands, workmux:cmd-merge.
Revert [unsupported] No revert command: conflicts and bad merges are resolved with git/agent effort, not product revert. Sources: workmux:commands, workmux:skills.
Stale approval invalidation [unknown] Completion, stale_approval_invalidation: no approval model exists to invalidate.
Dashboard Agents/Worktrees tables form a review queue (sort/filter/jump, diff, input-steer, commit/merge keys) with sweep bulk-removal of merged/gone work. No summaries, risk scoring, revision approvals, merge queues, or dedup.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Batch review is per-agent triage, not a coordinated release queue: no dependency ordering or approval pinning.
The six-plus-item fixture review was not executed hands-on here.
12 atomic answers
Review queue [partial] Agents/Worktrees tables with priority/project/recency sorts and session/stale filters act as the queue; the 12-state fixture was not run. Sources: workmux:dashboard.
Summaries [unknown] Batch review, summaries: no generated summaries; titles and git stats only.
Grouping [partial] Group-by-project sort and session filter; no epic or dependency grouping. Sources: workmux:dashboard.
Next actions [partial] Sweep reasons and merge-vs-remove guidance suggest next actions; no next-action engine. Sources: workmux:dashboard, workmux:workflows.
Stale approval invalidation [unknown] Batch review, stale_approval_invalidation: no approvals exist to invalidate.
Check deduplication [unknown] Batch review, check_deduplication: no dedup behavior found.
MIT-licensed Rust binary and repository (LICENSE + Cargo.toml at pinned v0.1.282); public source on GitHub; no component or hosted-service exceptions.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
6 atomic answers
Client license [supported] MIT: LICENSE grant plus Cargo.toml license field; the CLI/TUI binary is built from this source. Sources: workmux:license, workmux:cargo.
Server license [supported] No separate server component: remote nodes run the same MIT binary. Sources: workmux:cargo, workmux:remote-setup.
Hosted extensions [supported] No hosted service or proprietary extensions; docs describe only the open binary. Sources: workmux:home, workmux:repo.
Source visibility [supported] Public repository github.com/raine/workmux with full history; default branch main. Sources: workmux:repo.
Source revision [supported] Pinned revision v0.1.282 commit e72fd5925cbfd617bbefbf51a75f93d16556119d (2026-11-10), equal to main HEAD observed 2026-11-12. Sources: workmux:cargo, workmux:release-282.
Hosted parity [supported] Nothing hosted to diverge: releases are built from the public repo (update verifies checksums). Sources: workmux:repo, workmux:update.
Self-contained local binary with no vendor service, accounts, or required backends; code is git-portable and uninstall removes data dirs. Product state files have no documented portability contract.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
State-file portability (agents dir, workmux.log) has no documented format contract.
Agent-side history portability belongs to each harness, not the product.
8 atomic answers
Self hosting [supported] Runs entirely on user machines/servers; no vendor service to host or depend on. Sources: workmux:install, workmux:remote.
Vendor dependencies [supported] No required vendor services: install, config, git, and agents are all user-side; server needs no GitHub access. Sources: workmux:install, workmux:remote-setup.
Export [partial] Work is plain git (branches/worktrees) plus prompt files; machine-readable status/list JSON; state-file formats undocumented. Sources: workmux:cmd-merge, workmux:cmd-status.
Import [partial] Works in any existing repo (init adds config); add --from/--base/--pr imports branches, commits, PRs, and forks. Sources: workmux:quickstart, workmux:cmd-add.
Formats [partial] Git-native formats plus JSON CLI output; no proprietary formats to convert. Sources: workmux:cmd-status, workmux:cmd-list.
Cancellation [supported] Uninstall script removes hooks, skills, cache, and state; Homebrew/Cargo paths documented; no account to close. Sources: workmux:install.
Account independence [supported] Fully usable with no vendor account; agent logins are harness-side only. Sources: workmux:install, workmux:remote-logins.
History portability [unknown] Exit, history_portability: workmux state-file portability across machines was not established.
Code, prompts, credentials, and logs stay on user machines or user-owned servers; sandboxes exclude host secrets. No telemetry policy disclosed; only documented network behaviors are the daily update check (disableable) and release downloads.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
Not separately cross-checked
No telemetry or data-handling policy page exists; assessment rests on architecture plus the two documented network behaviors.
Model-provider data use belongs to each harness and its own policy.
15 atomic answers
Code data [supported] Worktrees live on user machines; remote servers are user-owned and never talk to Git hosting. Sources: workmux:caveats, workmux:remote-setup.
Prompts [supported] Prompts travel via CLI/files to local or user-server agents; no vendor service receives them. Sources: workmux:agents, workmux:remote-setup.
Credentials [supported] Host SSH/credential files excluded from sandboxes; remote logins/env stored privately per server; one-time --import with rotation caveats. Sources: workmux:sandbox, workmux:remote-logins.
Artifacts [partial] Diffs/prompts/logs persist locally until cleanup; no artifact-handling policy beyond that. Sources: workmux:dashboard, workmux:workflows.
Retention [unknown] Data, retention: retention/deletion schedule not documented (reap-agents pruning noted without schedule).
Deletion [partial] remove/--gone/sweep and uninstall delete worktrees, branches, cache, and state dirs; remote workspaces removed via remove/merge. Sources: workmux:workflows, workmux:install.
Training [unknown] Data, training: no training-use statement found; product transmits nothing to a vendor, but harness policies are separate.
Residency [unknown] Data, residency: no residency statement; data stays where the user runs it.
Subprocessors [unknown] Data, subprocessors: no vendor service exists, but no subprocessor statement was found.
Telemetry disclosure [partial] No telemetry disclosure page; only network behaviors documented are the update check and release downloads. Sources: workmux:update.
Telemetry defaults [unknown] Data, telemetry_defaults: no telemetry defaults stated; update check runs daily until disabled.
Telemetry controls [unsupported] No product telemetry control or collection module in the inspected config/source inventory. The documented opt-out only disables update checks. Sources: workmux:nov13-telemetry-controls.
Consent prompt [partial] First-run setup wizard offers skill/hook installation and nerdfont choice; no data-consent prompt documented. Sources: workmux:status, workmux:config.
Provider separation [supported] Product sends nothing to model providers; agent traffic is between the harness and its providers. Sources: workmux:agents, workmux:remote-logins.
Workmux is a free MIT-licensed application with no paid Workmux tier. Model use runs through the selected coding agent credentials; sandbox setup explicitly supports the user Anthropic API key. Provider usage and user compute are separate costs.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
Not separately cross-checked
The free application includes no hosted model allowance. Agent/model usage and user-operated compute have separate costs and limits.
12 atomic answers
Currency [supported] No currency: nothing is sold; install methods are all free. Sources: workmux:install, workmux:home.
Interval [supported] No billing interval: no subscription exists. Sources: workmux:home, workmux:repo.
Seats [supported] No seats: single binary per user, no team billing. Sources: workmux:install.
Seat minimum [supported] No seat minimum: nothing is sold. Sources: workmux:home.
Workspace fees [supported] No workspace fees: unlimited local/remote workspaces at no product charge. Sources: workmux:config, workmux:remote.
Included usage [partial] The full MIT binary is free. It bundles no vendor inference allowance; users supply coding-agent credentials and their own compute. Sources: workmux:home, workmux:readme, workmux:remote-logins.
Credits [supported] No credits: no vendor metering exists. Sources: workmux:home.
Trial [supported] No trial: the full product is free, not time-boxed. Sources: workmux:home, workmux:install.
Overages [supported] No overages: no metered units. Sources: workmux:home.
Taxes [supported] No taxes: no sale occurs. Sources: workmux:home.
Model cost [supported] Users supply coding-agent model credentials. The official sandbox setup explicitly supports passing the user Anthropic API key to the agent. Sources: workmux:nov13-provider-key, workmux:remote-logins.
Compute cost [supported] Compute is BYO: own machine plus own servers; no vendor compute fees. Sources: workmux:remote-setup, workmux:install.
Platform cost is $0 for one, two, or five developers (each installs the free binary on own hardware). Variable costs are agent subscriptions/API usage and any user-owned server spend, both unpriced in product sources.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Variable costs (agent plans, API meters, server bills) are unknown from product sources and excluded from the $0 figure.
No per-task token/time assumptions exist to price; the catalog forbids inventing task costs.
11 atomic answers
One person [supported] One developer: $0 platform (free binary, own machine). Sources: workmux:install.
Two people [supported] Two developers: $0 platform (each installs free; collaboration is out of product scope). Sources: workmux:install.
Five people [supported] Five developers: $0 platform; same per-seat-free scaling. Sources: workmux:install.
Task assumptions [supported] No fixed task assumptions stated; scenario uses one worktree/agent per developer with default config. Sources: workmux:quickstart.
Concurrency [partial] Parallel worktrees per developer bounded only by --max-concurrent and machine capacity, both user-side. Sources: workmux:changelog, workmux:remote-setup.
Tokens [unknown] Scenario cost, tokens: token prices live with harnesses/providers, not the product.
Compute hours [unknown] Scenario cost, compute_hours: server costs depend on user-chosen machines, unpriced in product sources.
Fixed cost [supported] Fixed cost $0: no platform, seat, or workspace fees. Sources: workmux:home, workmux:install.
Variable cost [partial] Variable costs are BYO agent subscriptions/API and server bills; amounts unknown from product sources. Sources: workmux:remote-logins, workmux:remote-setup.
Included cost [supported] Included: every product feature (dashboard, sidebar, sandbox, remote, skills) at $0. Sources: workmux:readme.
Unknown cost [partial] Unknown: agent plan/API meters and user-server bills; no product metering to reconcile against. Sources: workmux:remote-logins.
Actively maintained 0.x (v0.1.282 on 2026-11-10, weekly cadence) with public docs, changelog, and GitHub-issue support; experimental subsystems flagged. No SLA, status page, or access restrictions.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
0.x versioning with explicitly experimental backends (remote, kitty/WezTerm/Zellij); availability beta reflects that, not downtime.
No support commitments, status history, or deprecation policy documented.
Access restrictions [supported] No restrictions: public repo, docs, and binaries; no account, invite, or paywall. Sources: workmux:install, workmux:repo.
Support [partial] "Open an issue" invitations, docs, changelog, troubleshooting; community videos; no helpdesk or SLA. Sources: workmux:remote, workmux:skills, workmux:readme.
Response commitments [unknown] Support, response_commitments: no response-time commitments found.
Ongoing free MIT download with full functionality and no card, trial, or paid evaluation path; agent and compute costs stay separate. Single-user scope bounds team scenarios.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
Two-person collaboration scenario: each person free, but no shared/multiplayer surface exists (see TEAM-01).
Meaningful evaluation needs a coding-agent login (BYO subscription), not product payment.
10 atomic answers
Ongoing free [supported] Free and open source with no paid tier; full binary free indefinitely. Sources: workmux:home, workmux:repo.
Trial [supported] No trial: nothing to try out under time limit; the product is the free artifact. Sources: workmux:home, workmux:install.
Credits trial [supported] No credits trial: no credits exist. Sources: workmux:home.
Self host cost [supported] Self-run at $0 plus own hardware; open source with prebuilt binaries and source builds. Sources: workmux:install, workmux:license.
Early access [supported] Not gated: public repo, docs, and binaries with no waitlist. Sources: workmux:repo, workmux:install.
Free scenarios [partial] Solo, local Git, remote-BY0-server, dashboard/sidebar review all work free; two-person shared review has no product surface. Sources: workmux:quickstart, workmux:remote, workmux:dashboard.
Transparent: the ADE is free with no paid units, limits, overages, markups, minimums, or cancellable plans; agent/compute spend is third-party and out of scope.
Scope
Surfaces: workmux command-line interface (macOS/Linux binary), workmux dashboard terminal UI, workmux sidebar multiplexer pane · Version: v0.1.282 (commit e72fd5925cbfd617bbefbf51a75f93d16556119d, 2026-11-10); docs pass 2026-11-12 · Plan: Not specified · OS: macOS, Linux · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
9 atomic answers
Units [supported] No billing units: nothing metered. Sources: workmux:home.
Included limits [supported] No included limits: no quotas from the vendor. Sources: workmux:home, workmux:changelog.
Overages [supported] No overages: no metered units to exceed. Sources: workmux:home.
Minimum commitment [supported] No minimum commitment: nothing to buy. Sources: workmux:home.
Cancellation [supported] Nothing to cancel: uninstall removes local data; no account closure needed. Sources: workmux:install.
Sales only unknowns [supported] No sales-only unknowns: no enterprise tier or gated pricing exists. Sources: workmux:home, workmux:repo.
Transparency classification [supported] Classification transparent: $0, no units, no overages, no minimums, third-party spend out of scope. Sources: workmux:home, workmux:install.
Terminal-first workflow for parallel AI agents using git worktrees: one task per worktree and tmux window, sidebar and dashboard for agent status, sandbox containment, SSH remote servers, agent skills; described as free and open source.
Kind
vendor-claimed
Locator
Hero; Remote servers; How it works; Skills; Setup sections
Install via install script, Homebrew (macOS/Linux), Cargo, mise, Nix, or prebuilt binaries; shell completions for bash/zsh/fish; uninstall script removes data dirs; no account, signup, or payment step.
Always-visible agent overview pinned to tmux windows (or Zellij tabs): per-agent tile with status icon, worktree, elapsed time, project, git diff stats, optional PR number/checks, task description; toggle via workmux sidebar; session scoping and named views; requires status hooks.
Kind
documented
Locator
Setup; What it shows; Layouts; Sleeping agents; Session filter; Views
Experimental: run agents on user-reachable Linux servers over SSH; each remote agent keeps a local tmux window and appears in dashboard/sidebar/status/list as handle@remote; agent keeps working while local machine sleeps, loses network, or closes the window; window reconnects by itself; workmux merge brings work home; local machine stays Git source of truth.
Kind
documented
Locator
Overview (Experimental); How it fits together; Quick start
add -A auto-names from prompt; /worktree spins off from running agents; --fork resumes conversations (Claude/Codex/Pi); /coordinator plans+delegates+merges; /merge for direct merge; /open-pr + git push + gh pr create then workmux remove/--gone for PR flow.
Kind
documented
Locator
From terminal; From agent session; Forking; Coordinating; Direct merge; PR-based
Command reference inventory: 24 documented command pages (add merge rebase remove rename list status open close resurrect sync-files path shell dashboard sidebar reap-agents config edit init claude prune sandbox remote completions docs update last-done) plus additional CLI-only commands (setup, send, wait, capture, run); no REST API, SDK, MCP server, webhook, or scheduling commands appear in the reference or full docs.
Local git merge into main (or --into) with merge/rebase/squash strategies plus worktree+window+branch cleanup; --keep/merge_keep; --notification system notification; PR workflows merge remotely and use remove for cleanup instead.
Kind
documented
Locator
When to use merge vs remove; Options; Merge strategies; What happens
Prebuilt binaries for macOS (Apple Silicon/Intel) and Linux (x86_64/ARM64); background update check at most daily, disableable via auto_update_check:false or WORKMUX_NO_UPDATE_CHECK=1; update verifies checksums, Homebrew installs defer to brew.
Global ~/.config/workmux/config.yaml plus per-project .workmux.yaml; remotes and named agents are global-only; placement selects local or a named remote; panes support <agent> placeholders, splits, sizes; files copy/symlink; post_create/pre_merge/pre_remove hooks.
Built-in agents: claude, codex, copilot, opencode, gemini, agy, kiro-cli, vibe, pi, omp, grok; prompt injection via -p/-P/-e without config changes; named global profiles with type/command/args/env (incl. from_env); multi-worktree generation (-a/-n/--foreach) e.g. one worktree each for claude and gemini.
Kind
documented
Locator
Agent integration; Named agents; Per-pane agents; Parallel workflows
Permission options: symlink .claude/settings.local.json across worktrees, or named agent shadowing claude with --dangerously-skip-permissions; separate work/personal configs via named agents or CLAUDE_CONFIG_DIR.
Requires Linux x86-64/ARM64, promptless SSH, git, tmux 3.3+, systemd linger, API access; host mode (no sandbox) vs Docker mode per sandbox.enabled/isolation; server never talks to Git hosting and gets no origin; remote_files allowlist (64 MiB cap); no host-command proxying on servers.
Kind
documented
Locator
Requirements; Server or Docker; Install and check; Supplemental files; Security
remote login runs each agent native login flow (claude/codex/gemini/opencode/pi/omp) with localhost port forwarding; --import does a one-time credential copy (with rotation caveats); setup-token for Claude; sandbox env passthrough read once per workspace and stored privately on server.
Kind
documented
Locator
Per-agent login table; Copy logins; Claude long-lived token; Environment variables
Experimental Zellij backend requiring 0.44.1+; operates in current session; window-mode only; no dashboard preview (dump-screen covers focused pane only); sidebar supported; Windows is not supported.
Kind
documented
Locator
Experimental; Differences from tmux; Sidebar; Requirements
Container (Docker/Podman/Apple Container) and Lima VM backends isolate agents from host secrets; sandboxed agents get noninteractive prompts with sandbox as boundary; status/dashboard/merge work the same via RPC bridge; documented limits: edits untrusted, host git ops and hooks outside boundary, no hostile-code-containment promise.
Kind
documented
Locator
Security model; Agent permission prompts; Container/Lima backends; Threat model
Lists worktrees with AGE, AGENT status icons (incl. counts, text labels when piped), MUX window presence, UNMERGED marker; --pr shows PR status (gh); --json output; remote workspaces listed with remote name, last-known state, and exited reasons such as host reboot.
Template skill that drafts PR description from diff/commits and runs gh pr create --web to open creation in the browser; explicitly does not create the PR directly.
Kind
source-inspected
Locator
Gather context; Write PR description; Create the PR
Bounded inspection of raine/workmux at e72fd59 (homebrew-workmux tap holds packaging only, no product code): prompts are one-shot launch briefs written to git-excluded .workmux/PROMPT-<branch>.md (setup.rs write_prompt_file); prompt frontmatter parses only a foreach matrix (prompt.rs PromptMetadata); the state store keeps pane-level status/activity timestamps only (state/types.rs AgentState); dashboard/sidebar list agents and worktrees, not plans. Searched plan/acceptance/revision/spec across src/, skills/, docs/: no plan objects, acceptance criteria, editors, revision history, or implementation links.
raine/workmux at e72fd59: merge --into targets any base branch (stacked git branches, not a product hierarchy); the state store is flat per-pane records with no parent/child/blocker/dependency fields; pre_merge/pre_remove are shell lifecycle gates, not dependency enforcement; coordinator merge ordering is an agent prompt convention (SKILL.md); multiplexer readiness is a shell-handshake wait (handshake.rs), not dispatch gating. Searched epic/hierarchy/blocker/depend/readiness/enforce across src/, skills/, docs/: no epics, blockers, readiness gates, dependency enforcement, state propagation, or mandatory workflows.
raine/workmux at e72fd59: the config schema holds named agents, remotes, hooks, layouts, and status icons with no memory/instruction/role keys (the only `memory` is Lima VM RAM); the 6 bundled skills are static prompt files installed to agent directories (skills.rs), not a managed store; sandbox mounts and file_ops only mount or seed credential, config, and prompt files. Searched memory/instruction/provenance/retriev/index across src/, skills/, docs/: no managed memory store and no scope, provenance, correction, deletion, or freshness controls.
raine/workmux at e72fd59: the only built-in model call generates kebab-case git branch names (llm.rs generate_branch_name); dashboard/sidebar filters match agent/worktree names only; list columns are PROJECT/BRANCH/AGE/PR/AGENT/MUX/UNMERGED/PATH (git/status data). Searched search/index/retriev/citation/conflict/semantic/embed across src/, skills/, docs/: no product code search, repository indexing, external-knowledge retrieval, citations, conflict detection, or review-time enforcement; those belong to the launched harnesses.
Kind
source-inspected
Locator
llm.rs generate_branch_name; dashboard/sidebar name filters; command/list.rs WorktreeRow columns
raine/workmux at e72fd59: the /worktree skill dispatches by writing a per-task brief and running `workmux add`; the brief persists only as a git-excluded file in its worktree with no cross-task store, revisions, approvals, retrieval, or drift detection; the state store and dashboard hold no requirement objects. Searched spec/requirement/persistent/approval/drift across src/, skills/, docs/: no living product specification surface.
Manages git worktrees + tmux windows for parallel AI agents; features dashboard, sidebar, /worktree skill, agent status tracking, sandbox, remote servers, branch-name generation; install via script/Homebrew/Cargo/mise/Nix; philosophy "tmux is the interface".
Kind
documented
Locator
Why workmux; Features; Installation; Community videos
New worktrees are clean checkouts needing files copy/symlink config; parallel branches can still conflict on merge; per-worktree installs recommended; node_modules cleanup handled in background.
raine/workmux at e72fd59: list/status/dashboard expose git and agent-status data only (PROJECT/BRANCH/AGE/PR/AGENT/MUX/UNMERGED/PATH); repo-wide grep for cost/spend/budget/billing/invoice finds only UI width budgets, a 64 MiB transfer byte budget, and claude setup-token auth flows, never usage. No model/API spend, token usage, subscription allowance, compute fees, alerts, export, or drill-down anywhere in src/, skills/, or docs/.
raine/workmux at e72fd59: the dashboard comment action (diff_ops.rs send_hunk_comment) pastes a hunk-annotated message into the operator own agent pane, which is single-user steering, not shared discussion; state is local per-pane JSON with no user, team, presence, or permission fields; remote servers are the single user SSH machines. Searched collaborat/multi-user/teammate/presence/co-prompt/share/comment/sso across src/, skills/, docs/: no shared visibility, discussion, presence, co-prompting, attribution, or plan-restriction surfaces.
Kind
source-inspected
Locator
diff_ops.rs send_hunk_comment; state/types.rs and store.rs local JSON; remote/ single-user SSH model
raine/workmux at e72fd59: no accounts, organizations, roles, membership, SSO, or provisioning; the product runs as the local OS user with no signup (install guide); the config schema has no role or permission keys; remote/credentials.rs stores the single user SSH keys and per-agent logins. Searched sso/scim/organization/role/acl/member/policy across src/, skills/, docs/: no role or access-boundary enforcement beyond OS-user execution and sandbox file mounts.
Kind
source-inspected
Locator
config.rs key inventory; remote/credentials.rs SSH and login storage; install guide (no accounts)
raine/workmux at e72fd59: --continue/--fork resume the same user same-harness conversation from that harness own store (per-harness ConversationForker implementations); switching harness requires a new worktree via -a; resurrect restores windows after crashes for the same user and machine. Searched takeover/handoff/colleague/second-user/ownership/attribution across src/, skills/, docs/: no second-user, ownership-transfer, or attribution surfaces; artifacts (branches, files) move only through git and the filesystem, not product takeover.
Kind
source-inspected
Locator
conversation.rs ConversationForker per-harness resume; workflow/create.rs fork and continue; resurrect flow
The pinned product has no telemetry configuration or telemetry implementation in the inspected source/dependency inventory. Its network opt-out auto_update_check/WORKMUX_NO_UPDATE_CHECK disables update checking, not product telemetry. Provider-owned agent traffic remains separate.
Kind
source-inspected
Locator
Config key inventory; src/command/update.rs check_and_notify; bounded src/Cargo.toml/Cargo.lock search for telemetry, analytics, PostHog, Sentry, Segment and Mixpanel
The official agent-container setup explicitly passes the host ANTHROPIC_API_KEY into the selected coding-agent sandbox through the global env_passthrough setting. This is own-provider-key model access, separate from the free Workmux binary and any provider usage bill.
Kind
documented
Locator
Configuration: env_passthrough; Example configurations: Podman with ANTHROPIC_API_KEY