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

# Machinist vs Podium

> 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; 36 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.

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

## Access and agent choice

### ACC-01: Client access

- **Machinist**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Embedded React web app served by the control plane (Home, Work, Automations, Runners, job chat page), the machinist CLI, MCP from Claude Code or Codex, and GitHub mentions; binaries for Linux and macOS only; no desktop or phone app and no editor extension.
- **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.

### ACC-02: Agent and model choice

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Claude Code and Codex only, as fixed harness commands; agents are folders (playbook, model, subagents, skills) per harness; a job may chain agent and script stages but all agent stages use one harness; no custom harness yet.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Credentials live on runners: Anthropic/Bedrock/Vertex/Foundry env, OPENAI_API_KEY, Claude setup-token or login and ChatGPT login (local runners only); no vendor credits; local models not documented.
- **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.

### ACC-04: Onboarding and project prerequisites

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Build with Go or install a release, machinist init, set github.handle and repositories, set runner credentials and GH_TOKEN, start control plane and runner, create a token and sign in; every job ends in a branch and PR on a GitHub repository; no directory-only or managed-cloud path.
- **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.

### ACC-05: Programmable access

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. CLI, an authenticated HTTP API, and five MCP tools (assign, get, list, answer, cancel tickets) served at /mcp; GitHub mentions for intake; bearer tokens; no SDK or outbound webhooks; API stability is early-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.

### ACC-06: External tools and extensions

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The agent runs with the repository’s own project settings; MCP servers are strict-config disabled for Claude runs; subagents and skills come from factory agent folders; Machinist itself is an MCP server rather than an MCP client.
- **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.

### ACC-07: Client implementation

- **Machinist**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Go control plane with an embedded React and Vite web app (committed production build); no desktop or mobile app.
- **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.

## Planning and context

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Work enters from the web app box (text, issue number or link), a GitHub mention by someone with write access, MCP assign_ticket, or a cron automation; tickets are native, the control plane polls GitHub each minute for comments, PR state, reviews and checks; no Linear or Jira.
- **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.

### PLAN-02: Durable task plans

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The ticket log holds the request, agent reports, human comments and CI pointers across runs; agents are told to push often; jobs list stages; no editable plan, acceptance criteria or revision history.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Tickets are flat with six states; a job is a linear stage list (no branching, loops or parallel stages); no epics, parent/child tickets or dependencies.
- **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.

### PLAN-04: Shared context and memory

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Playbooks and subagent/skill files in factory agent folders, repository settings loaded by Claude (project settings only), per-ticket log; no cross-session memory manager.
- **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.

### PLAN-05: Architecture and API awareness

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No code search, indexing or knowledge features in Machinist; agents use their own tools and gh against a fresh clone.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Work page lists tickets with status tabs and a chat-style job page for replies; assign by box, GitHub, MCP or schedule; cancel; no labels, priorities, assignment to people, search, archive or 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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agents in Claude Code or Codex can assign, read, list, answer and cancel tickets over MCP using stable ticket IDs shared with the web app; the runner agent itself reads the ticket log; no claims, dependencies or children.
- **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.

### PLAN-08: Living product specifications

- **Machinist**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No living product specification features; factory files and the ticket log are the only persistent artefacts.
- **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.

## Coordination and automation

### COORD-01: Parallel work

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Runners hold slots and run many tickets concurrently across local and Kubernetes runners; the Runners page shows busy slots, waiting runs and wait time; Home and Work show running, needs-you and done states.
- **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.

### COORD-02: Ownership and dispatch

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Runners claim runs by polling when they have a free slot and leases (10 minutes) prevent duplicates; a request_id and one active ticket per issue prevent duplicate tickets; no human or agent assignment.
- **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.

### COORD-03: Inspectable delegation and communication

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. A job chains agent and script stages in one clone; a fresh reviewer agent comments on the first PR; subagents are provided to the harness through agent folders; the control plane never starts agents and exposes no cross-agent messaging.
- **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.

### COORD-04: Unattended triggers

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Cron automations in factory files (5-field schedule with timezone), polling for GitHub comments, reviews and checks each minute; missed runs collapse and an automation never waits for a person; runs on the control plane regardless of client.
- **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.

### COORD-05: Intervention and attention

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Cancel stops a ticket and leaves its PR open; agents ask questions and wait (needs_you); people answer in web, MCP or on GitHub; max turns without human and run timeouts stop runaway work; no pause, no notifications.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Home shows what is running, what needs you, pass rate and tokens for 14 days; Work lists jobs with status tabs; Runners shows capacity; no parent/child or dependency views.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Jobs and agents are plain files; new work uses default_agent and a job picker is a documented gap; reviewers per file; natural language only in the ticket text; changes need a restart and live relationships are limited to ticket runs and stages.
- **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.

## Execution and reliability

### RUN-01: Laptop-independent execution

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agents run on runners you control: a local daemon on a Mac or VM, or one gVisor Job per run on Kubernetes; the control plane holds state and runners dial out, so work continues without the client; no vendor cloud.
- **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.

### RUN-02: Workspace and process isolation

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Each run starts from a fresh clone on a fixed branch machinist/<ticket id>; local runs are an OS process with a private home and allowlisted env (concurrent runs under one user can read each other); Kubernetes runs are gVisor Jobs with an egress proxy and no service-account token.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Runs outlive control-plane restarts via stored 10-minute leases renewed every 30 seconds; a lost runner’s ticket continues on any runner after the lease expires and unpushed work is lost; reports and branch are the durable state.
- **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.

### RUN-04: Development environment reliability

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Environment comes from runner config allowlists and a Secret on Kubernetes; each run starts clean from a fresh clone; no caches, snapshots, service or port management.
- **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.

### RUN-05: Limits and failure handling

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Run timeout (default 60m) and max turns without human (default 5) are enforced; provider spend limits are external; no Machinist token or spend caps.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Each run keeps its report, stages, tokens and cost; Home shows pass rate and tokens for 14 days; ledger gives cost, questions and feedback rounds per ticket; usage is daily totals not split by person, job or agent.
- **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.

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

- **Machinist**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Cost and tokens recorded per run and summed per ticket in the ledger and shown on Home; harness-reported where available; no per-person, per-agent split, alerts or export.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Runner slots limit concurrent runs and the Runners page shows queue wait; no CPU/RAM awareness, deduplicated checks or fairness policy.
- **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.

## Human collaboration and control

### TEAM-01: Live human collaboration

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. One control plane lets anyone with a token see every job, answer questions and open PRs; replies in the job chat page and GitHub comments are the discussion; no presence, co-prompting controls or permissions.
- **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.

### TEAM-02: Roles and access boundaries

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No accounts, roles or SSO: one kind of token for people and runners, revocable by name; mentions require GitHub write access.
- **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.

### TEAM-03: Approvals and temporary access

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agents run with harness permission checks disabled; the boundary is the OS user or gVisor Job and the GitHub login with branch protection; agents ask humans questions; merges happen only if an automation uses an agent allowed to merge.
- **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.

### TEAM-04: Decision and activity history

- **Machinist**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Ticket log and ledger retain requests, reports, comments, cost and feedback rounds with the assigning token name; SQLite state is operator-owned and mutable; no export or integrity model.
- **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.

### TEAM-05: Review experience and guidance

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Review happens on the GitHub PR; a fresh reviewer agent posts one advisory comment; the web app shows pr_ready and links to the PR; no diff or review UI in Machinist.
- **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.

### TEAM-06: Colleague takeover and continuity

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Anyone signed in can answer or cancel the same ticket, and the ticket continues from the pushed branch and ticket log on any runner; no ownership transfer or attribution beyond token names.
- **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.

## Verification and delivery

### SHIP-01: Retained artifacts and outputs

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Each run keeps its report, stages, stdout/stderr events, tokens and cost; the branch and PR carry code; reviewer comments are posted on the PR; no artifacts, screenshots, recordings or gallery.
- **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.

### SHIP-02: Verification and spec gates

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Script stages are gates an agent cannot skip (failure ends the run), a fresh reviewer comments on the PR as advice, CI failures start follow-up runs; verification is whatever the job’s scripts run.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Fixed branch per ticket from a fresh clone; the agent pushes and opens one PR with gh; the control plane finds the PR, follows reviews and checks, and continues on the same PR after feedback or CI failure; rebase and conflicts are the agent’s.
- **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.

### SHIP-04: Merge and deployment authority

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Machinist never merges a PR unless an automation uses an agent allowed to; humans approve and merge on GitHub; branch protection and the login’s permissions are the authority controls.
- **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.

### SHIP-05: Completion evidence and rollback

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Ticket links to branch and PR, states pr_ready and done on merge, ledger counts commits and merges; no build, deployment, rollback or stale-approval handling.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Work table with a pr_ready tab and a Home list; each PR is reviewed on GitHub; no batch review tooling.
- **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.

## Ownership, privacy and economics

### OWN-01: Source and license

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. MIT license on the whole repository (control plane, runners, CLI, web app); the repository is the only component; the default branch is a redesign unreleased since v0.4.0.
- **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.

### OWN-02: Hosting and exit

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Whole product self-hosts with SQLite and plain factory files; no vendor account or service; back up tickets.db; no export or import tooling.
- **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.

### OWN-03: Data handling and telemetry

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Code, prompts and credentials stay on your control plane and runners; model credentials live on runners; prompts go to the harness provider; no telemetry found in the code; agents can read credentials.
- **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.

### OWN-04: Price and included usage

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Free MIT software with no paid plan; model and compute costs are the operator’s.
- **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.

### OWN-05: Scenario cost and controls

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Software cost is $0 for any team size; costs are model credentials and your own compute; no workload pricing from Machinist.
- **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.

### OWN-06: Availability and support

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Early-access software with fast change: latest release v0.4.0 (2026-08-31) while main has 203 later commits; support by GitHub issues and email with a seven-day acknowledgement for security reports; only the latest release and main receive security fixes.
- **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.

### OWN-07: Enterprise assurance

- **Machinist**: 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.
- **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.

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

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Free open-source software; self-hosting costs hardware and model credentials; no trial or paid tier.
- **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.

### OWN-09: Pricing transparency

- **Machinist**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Not applicable beyond free: no price, plan or commitment; model and compute costs are external.
- **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.
