---
schema_version: 7
rubric_version: "0.3"
canonical_url: "https://podium.do/compare/agents/podium-vs-workmux/"
data_url: "https://podium.do/compare/agents/podium-vs-workmux/data.json"
generated_at: 2026-11-22
last_checked_at: 2026-11-12
last_cross_checked_at: 2026-11-21
oldest_checked_at: 2026-11-06
publisher: "Podium"
---

# Podium vs workmux

> Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. Sourced findings follow the same evidence rules for Podium and its competitors. Facts labeled Podium team research come from Podium's own team and have no linked source. None of this removes the conflict of interest.

> Based on data from adecomparison.com by Podium (https://adecomparison.com; source repository https://github.com/madeinorbit/ade-comparison, snapshot 4322f0c of 2026-11-22), used under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Source links and check dates are kept. Podium arranges the findings into pairs, applies its publication checks, and added its own research where marked "Podium team research". Data license terms: https://github.com/madeinorbit/ade-comparison/blob/4322f0c035f303791413639d1462a138443d8c1e/DATA-LICENSE.md

48 criteria sourced for both products; 35 criteria also agent cross-checked for both. 50 criteria with a sourced finding for at least one product. "Sourced" findings passed publication validation. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. Humans approve the rubric, templates and prototype; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent.

Each row gives the finding's status, support, check date and answer. Scope, limitations, atomic answers and sources for every finding are in each product's document, under the criterion ID. Judgment rules are in the rubric.

- Podium source checks: 2026-11-06. Details: https://podium.do/compare/agents/products/podium/index.md
- workmux source checks: 2026-11-12. Details: https://podium.do/compare/agents/products/workmux/index.md
- Rubric: https://podium.do/compare/agents/rubric/index.md
- Canonical HTML: https://podium.do/compare/agents/podium-vs-workmux/
- Machine-readable JSON: https://podium.do/compare/agents/podium-vs-workmux/data.json
- Methodology: https://podium.do/compare/agents/methodology/

## Access and agent choice

### ACC-01: Client access

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium ships desktop, CLI and browser clients, including phone-browser control. The native iPhone app is private beta; the complete download offering contains no native Android app.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### ACC-02: Agent and model choice

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium launches the native Claude Code, Codex, Grok, OpenCode, Cursor and Pi CLIs in persistent terminals on machines you control. The 0.2.0 release calls Pi fully supported. Models come from each harness catalog, and capabilities differ per harness: Pi declares no quota, handoff or hooks. Mixed-harness operation was not exercised.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### ACC-03: Subscriptions, API keys and vendor credits

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports native coding-agent logins and managed provider credentials. Claude subscriptions (via native login or a managed setup-token) and local ChatGPT/Codex login are supported paths, alongside Anthropic and OpenAI API keys. Docs list billing and hosted metering as not implemented product claims.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### ACC-04: Onboarding and project prerequisites

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Docs describe a first-run flow (install, podium, register a Git repository, confirm a detected logged-in harness) and a headless VPS installer with machine joining. Setup time and failure rate were not measured, and no self-serve managed cloud setup is documented. The current README and installation guide use podium.do/download and podium.do/install.sh as the canonical stable entrypoints.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### ACC-05: Programmable access

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The podium CLI covers issue create, show, update, claim, dependencies, artifacts, session send/status/read/stop and review actions, and the server exposes the same issue commands as a bearer-token MCP tool endpoint. No documented public HTTP API, SDK or webhooks were found.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### ACC-06: External tools and extensions

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. Podium gives agents its own issue tools over CLI and MCP, and agent profiles import and export Claude Code agent files. No Podium documentation for user-configured MCP clients, plugins or custom tools was found.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### ACC-07: Client implementation

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Desktop releases use a Tauri 2 shell that serves the Podium web UI; mobile source uses Expo and React Native. A native iPhone release is described as private beta.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. Rust CLI/TUI binary (Cargo, edition 2024) with prebuilt macOS/Linux binaries; no Electron/Tauri/native-GUI or mobile clients.

## Planning and context

### PLAN-01: Intake and external tracker relationship

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium issue records are native and authoritative with stable references, CLI creation and editing, and agent-driven filing from conversation. The in-product assistant has Linear search, create and move tools when a key is configured, but no import or two-way tracker sync was found.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### PLAN-02: Durable task plans

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Issue brief, acceptance criteria, state paragraph and todos persist on the durable issue record. Release 0.3.0 removed the separate design and notes fields and appended their text to the brief. On the human issue page the title, description and acceptance are editable and the brief is read-only; agents edit the brief and other fields through issue commands.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### PLAN-03: Hierarchy, dependencies and evolving scope

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports persistent parent and child issues, phases and typed dependency links, including reparenting an existing issue without replacing its identity. Since 0.3.0 issue types are task, phase and decision: epic and other kinds are retired, and any issue with children acts as a parent. Dependency types are fixed to blocked-by, related, discovered-from, supersedes and duplicates. Cycles are refused and docs list an open blocker as a reason an issue cannot start. No mandatory workflow preset applies in the baseline.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### PLAN-04: Shared context and memory

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. v0.3.0 routes Podium issue instructions and relay environment through terminal and engine session launch. Claude stream sessions use appended instructions and boundary callbacks; Codex server sessions use developer instructions, Grok ACP uses rules, and OpenCode uses the prompt system field. Claude and Codex boundary hooks can re-prime after compaction. Transcript mirroring is on by default; full-text indexing needs the command-palette flag, which defaults off. Agent profiles can carry markdown instructions. Curated memory, skills and memory correction or deletion controls remain unestablished. No instruction-delivery or compaction scenario was run.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### PLAN-05: Architecture and API awareness

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Not established. Podium mirrors daemon transcripts by default, keeps a full-text index only when the command-palette flag is on, and stores session attachments. No repository code search, architecture awareness or API retrieval feature was found.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### PLAN-06: Native issue management and idea backlog

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes native issue creation with an optional start flag, separate dispatch, editing, comments, labels, assignment, search, board filters, archive, sibling ordering and an issue tree. Issue records have their own identity separate from sessions and stages are durable. The idea-to-mission scenario was not run. v0.3.0 refuses an agent close or done update while issue sessions are computing unless --confirm-interrupt is supplied; guidance says to request review and close only on user instruction.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### PLAN-07: Agent-native issue operations

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. CLI and MCP address the same canonical issue records for reads, creation, edits, claims, state, dependencies and artifacts. Relayed agents have worker capability scoped to their issue subtree, with --outside-scope confirmation for other existing issues. attachSession is not subtree-gated, but direct rehoming from a real issue is refused and an agent attach naming a Proposed target is refused. That does not make every Proposed subtree inert: operator attachment or spawn-time cwd binding can leave a session attached to a Proposed issue; newSubissue without targetId then bypasses the proposed-parent guard, creates a human-audience backlog child and attaches the existing session. This path remains at v0.3.0 source and was not exercised live. Concurrent-edit handling remains unknown.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### PLAN-08: Living product specifications

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The spec CLI and service (living specs under pspec with stable SP IDs) are in v0.3.0. Specs is an experimental, default-off feature listed on the edge channel: the flag controls the Specs UI, the spec line in CLI help and whether agents are told about the spec CLI. The podium spec command itself is dispatched, and the server specs service has no flag check, so direct CLI use does not need the flag. This agrees with the docs, which call specs not baseline rather than blocked. Not run end to end.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

## Coordination and automation

### COORD-01: Parallel work

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Docs and release notes describe many sessions running as independent terminals, one worktree per issue, and several paired machines under one server, with session and issue state visible on the flight deck, board and CLI. Agent-initiated spawns are limited to 10 per target issue per UTC day. Achieved concurrency is unmeasured.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### COORD-02: Ownership and dispatch

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Issues carry an assignee, claim sets assignee and in_progress, a coordinator session can be set per issue, sessions have seats, and work can be placed on a chosen machine or agent profile. claim has no exclusivity check of its own, locks are advisory leases and Podium does not serialize agents editing one worktree, so exclusive ownership is not enforced.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### COORD-03: Inspectable delegation and communication

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium orchestrates delegation itself: podium agent spawn starts a full child session on an issue with a chosen harness, model, effort or agent profile, mail carries messages, and bounded await reports the child result. Children are real sessions shown as seats on the flight deck. Agent-initiated spawns take a daily budget per issue. A complete delegated task with retained child findings was not run.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### COORD-04: Unattended triggers

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The server owns a scheduler for cron and one-time automations that spawn agent sessions, skipping overlaps and not backfilling occurrences more than an hour late. The Automations UI is an edge-visibility feature that defaults off and docs list automations as non-baseline. Agents can subscribe to issue and session events.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### COORD-05: Intervention and attention

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Chat and native CLI views share a session. v0.3.0 defaults human controller chat to steer and immediately types it into running Claude Code, Codex, Grok and OpenCode TUIs that declare native busy-input queuing; undeclared harnesses wait for a boundary, and compaction waits. Mail and automation keep when-ready delivery. Stop, resume, questions, decision issues and offers remain available. This is inspected implementation, not a cross-harness runtime parity result.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. Stop (dashboard kill/remove/reap-agents), resume (resurrect/--continue/--fork/reconnect), steer (input mode/send), and waiting-state attention (priority sort, last-done) all documented; no pause or escalation chain.

### COORD-06: Fleet and epic management UI

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Release 0.3.0 ships a flight deck showing a whole mission in one view: phases, every task and its state, who works on what, what is blocked and by what, and proposals. Done work stays visible. The CLI prints the same snapshot. The waterfall source is dormant and the Timeline view was deleted, so per-task timeline history is not shown. The shared 12-task UX scenario has not been run.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### COORD-07: Workflow flexibility and orchestration visibility

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. A quick task can be an interactive session or an issue; an issue can grow into a mission by gaining children while keeping its identity; no mandatory workflow preset applies in the baseline. Per-agent harness, model and effort are chosen at spawn or through agent profiles, and the deck shows seats. The coordinator-with-two-reviewers scenario was not run.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

## Execution and reliability

### RUN-01: Laptop-independent execution

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The published Podium execution choices are local user machines and a user-owned VPS or paired machine. No vendor-operated agent host is in the complete download offering.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### RUN-02: Workspace and process isolation

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### RUN-03: Recovery, expiry and continuity

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Closing a browser tab does not stop the agent process on a running Podium host. Idle sessions may hibernate under configurable policies; a stopped session keeps its transcript, branch and resume reference. Release 0.2.0 says a failed update rolls back and running sessions keep running through the upgrade; database rollback remains a manual restore. Terminal reattachment goes through the driver adopt contract with process-identity and observation-lease checks. Worker-crash and multi-day behavior were not tested.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### RUN-04: Development environment reliability

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Only machine setup is documented: the installer installs missing runtime tools and pairs a host, and the state directory holds server-managed secrets. Dependency caching, services, ports and automatic repair for project environments were not found.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### RUN-05: Limits and failure handling

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes retryable errors, optional auto-continue with backoff, bounded waits and provider quota. Claude stream and hosted headless drivers enforce a supplied turn deadline, with no deadline when timeoutMs is absent. The one-shot headless server runner supplies its budget, default ten minutes. Agent spawns have a daily per-issue budget. Operator-configurable task-wide turn, token and spend caps remain unestablished; quota display is not enforcement.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. Count-based throttling (--max-concurrent), wait timeouts, process-age reaping, pre-merge abort, and sandbox proxy limits exist; no time/turn/token/spend budgets or provider-failure policy documented.

### RUN-06: Truthful status and operational statistics

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Podium offers local logs and crash export, structured session status, issue stats, a usage and analytics sheet with hourly list-price cost, per-task costs and host load panels. The 0.3.0 notes report a vendor benchmark of about 330 MB server memory against about 1.2 GB for an earlier Podium build, and 8 to 52 percent faster start; the method is published in the repository and was not reproduced here. Usage export and cross-reconnect consistency were not established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. Host log, reconciled state files with --json diagnostics, per-agent/row stats (status, elapsed, titles, diffs), waiting/done failure semantics, and doctor checks. No traces, usage exports, aggregates beyond views, or measured performance claims.

### RUN-07: Per-task API and compute cost

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Since 0.2.0 Podium shows what each task costs, on the task header and the usage sheet, with per-session rows and descendant rollups. The 0.3.0 deck adds a mission cost chip. Figures are token estimates at public model list prices, not subscription invoices or provider bills.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### RUN-08: Compute-aware scheduling and verification

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium reports host memory, load and disk, auto-hibernates idle sessions under pressure, and provides named advisory resource leases. The merge-queue panel was removed; a shipping queue remains behind the Shipping flag. Concurrency limits and bounded test queuing were not established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. Count-based concurrency (--max-concurrent), wait-any wakeups, container CPU/RAM caps, proxy backpressure, and kill/sweep cancellation with resurrect/remote recovery. No host-aware scheduling, check reuse, fairness, or shared-limit model.

## Human collaboration and control

### TEAM-01: Live human collaboration

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The issue UI displays owner and visibility read-only and deliberately omits sharing controls. Backend share handlers and a Members settings section with invites and admin or member roles exist; they do not establish a finished human collaboration workflow. Docs say small teams can share an instance but the interface prioritizes one operator.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### TEAM-02: Roles and access boundaries

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium defines member/admin instance roles and admin-only membership management. The released client authentication uses password-backed sessions and paired-device tokens without enterprise SSO.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

### TEAM-03: Approvals and temporary access

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Agent-session management requests go through an operator approval broker with approve and deny; the privacy docs say lifecycle commands and automation requests may require operator approval. Harness permission prompts appear as a Permission needed state; credential copying during pairing is a per-grant opt-in. Command-level policy enforcement beyond the harness own modes was not established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### TEAM-04: Decision and activity history

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Issue actions, approval steps, comments and mail are recorded server-side. Issue activity events, including approval steps, are pruned by the server's janitor once they are older than 14 days or fall outside the newest 50,000 rows. That policy does not define all content retention, export or tamper-evident audit guarantees.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### TEAM-05: Review experience and guidance

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Review is a documented loop: issue stage review, diff and checks, artifacts, offers with merge or send-back buttons, and a Tray of review-ready work. Release 0.3.0 adds quoting text from a reply or review finding into the next message and a full-height reading view with an outline. The board has a key map with a help sheet. Guided-review quality and narrow-screen use were not measured.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. Dashboard-centered review: waiting-first surfacing, diff/patch evidence with syntax highlighting, PR check links, keyboard-first navigation with mouse option, and commit/merge/sweep actions. No comments, effort data, or guided next-action engine.

### TEAM-06: Colleague takeover and continuity

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The durable issue, session transcript, artifacts and mail persist for any later agent, and a live session can be handed to another machine in an edge feature. Colleague takeover by a second person was not established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-13. 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.

## Verification and delivery

### SHIP-01: Retained artifacts and outputs

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. Artifact commands store immutable server-side copies of issue-linked files, including images, video, HTML and documents, which render in the issue sidebar and offers and stay readable after the worktree is gone. Each task has an artifacts page grouped into screens, documents and reports, with filters and search. Revision linking remains untested.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### SHIP-02: Verification and spec gates

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. In the experimental Shipping path a configured validation profile runs before landing (default argv bun run test with a 10 minute timeout) and a failed validation holds the order. Lint, type, CI and spec conformance gates and independent review requirements were not found as product-enforced policy.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### SHIP-03: Git and pull request workflow

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Issues own branches and worktrees, and issue actions rebase, open a pull request with gh (pr create --fill) and merge, subject to a merge-style setting (ff-only by default, with auto-rebase before merge). Podium does not resolve branch conflicts, and PR review comments and CI response were not established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### SHIP-04: Merge and deployment authority

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The operator accepts work through offers and runs the merge action under a branch merge-lock; in the experimental Shipping path approval is frozen to an exact head and delivery lands on a local target branch by default. Release and deployment are not product features found in the sources.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### SHIP-05: Completion evidence and rollback

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Shipping orders record approved base and head SHAs, tested integration SHA, landed ref and validation result in a durable delivery receipt, and stale approvals hold the order. Shipping is experimental. The pr action records a PR URL on the issue. Build and deployment links and rollback were not found.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### SHIP-06: Batch review and high-volume shipping

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. The shipping service records revision-specific approval, configured validation and delivery receipts. The Shipping panel is an experimental edge toggle, off by default; the separate Queues panel was removed.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

## Ownership, privacy and economics

### OWN-01: Source and license

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The public repository is licensed Apache 2.0, and the website presents Podium as an open-source agent development environment. Hosted extensions and hosted-service terms are not established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. MIT-licensed Rust binary and repository (LICENSE + Cargo.toml at pinned v0.1.282); public source on GitHub; no component or hosted-service exceptions.

### OWN-02: Hosting and exit

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Local desktop and self-hosted installs run on user-controlled machines with a documented state directory. The docs describe stopped full-state backup and automatic pre-migration database-only snapshots retaining three copies. Those snapshots omit artifacts, transcripts, uploads, configuration and secrets; no portable structured export/import contract was established.
- **workmux**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### OWN-03: Data handling and telemetry

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-21. Docs state repositories and native harness credentials stay on machines you control and server state lives in a documented directory. Since 0.2.0 a daily usage report is on by default and can be turned off; crash reports stay opt-in. Usage reports carry an install id, schema version, Podium version, OS, architecture, bucketed install age and machine count, session counts per harness and whether issues were used. Crash reports carry the same install id, versions, OS and architecture, a fixed error type and up to 20 stack frames, each with a Podium source file path, line and function when there is one; error messages and frames outside Podium are dropped. Neither tier sends prompts, transcripts, your code or paths outside the Podium source tree. Model-provider handling is the harness own. Hosted analytics and website analytics are separate paths.
- **workmux**: Sourced (sourced); support: partial. Checked 2026-11-12 (10 days old); not separately cross-checked. 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.

### OWN-04: Price and included usage

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. No Podium price is published: podium.do/pricing returns 404 and the docs list billing as not implemented. The software is open source and free to download; model and compute costs are the user's own.
- **workmux**: Sourced (sourced); support: partial. Checked 2026-11-12 (10 days old); not separately cross-checked. 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.

### OWN-05: Scenario cost and controls

- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### OWN-06: Availability and support

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium is pre-1.0. Stable v0.3.1 (2026-11-06), an update fix, follows v0.3.0 (2026-11-05), v0.2.0 (2026-10-11) and v0.1.0 (2026-08-21), with edge and dev prerelease channels. Windows and Linux desktop are Experimental, the native iPhone app is in private beta and hosted Podium is unconfirmed. Support runs through GitHub issues, Discord and private vulnerability reporting.
- **workmux**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### OWN-07: Enterprise assurance

- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **workmux**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

### OWN-08: Useful free tier and evaluation access

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium is open-source Apache-2.0 software, and the download page calls it free and open source. Download links for macOS, Linux and Windows redirect to GitHub release assets without a login (observed by HTTP requests; not installed). No Podium charge is documented for self-hosting; agent provider usage is separate. The native iPhone app is private beta and hosted access is unconfirmed.
- **workmux**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.

### OWN-09: Pricing transparency

- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **workmux**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-12 (10 days old); agent cross-checked 2026-11-12. 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.
