---
schema_version: 7
rubric_version: "0.3"
canonical_url: "https://podium.do/compare/agents/coder-agents-vs-podium/"
data_url: "https://podium.do/compare/agents/coder-agents-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"
---

# Coder Agents 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.

- Coder Agents source checks: 2026-11-16. Details: https://podium.do/compare/agents/products/coder-agents/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/coder-agents-vs-podium/
- Machine-readable JSON: https://podium.do/compare/agents/coder-agents-vs-podium/data.json
- Methodology: https://podium.do/compare/agents/methodology/

## Access and agent choice

### ACC-01: Client access

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Browser chat interface on the Coder dashboard Agents page plus an HTTP API and an experimental coder exp chat CLI; the coder CLI installs on Linux, macOS and Windows. There is no native desktop or mobile app for Agents and no Agents-specific editor extension; developers use their usual editor against the workspaces the agent produces.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Coder Agents embeds its own Go agent loop in the control plane and is not a wrapper for Claude Code or Codex; it can also delegate to external harnesses (Claude Code, Codex) as experimental ACP subagents running in the workspace. Model providers: Anthropic, OpenAI, Google, Azure OpenAI, Bedrock, OpenAI-compatible, OpenRouter, Vercel AI Gateway with custom base URLs.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Admin-configured provider API keys (deployment-wide), optional per-provider user API keys (BYOK), model access through AI Gateway budgets, and local or self-hosted models through OpenAI-compatible endpoints. ACP harnesses use their own credentials, including whatever subscription login the harness supports. Vendor credits do not exist for the model itself; Agent Hours are purchased from Coder for AI Premium.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Requires a running Coder deployment, at least one template and an LLM provider key; admin configures providers and models in Admin settings > AI; users then open the Agents page and prompt; the agent selects a template and provisions a workspace automatically. Git and GitHub/GitLab external auth drive repo access; no local-directory mode.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. REST API under /api/v2/chats (list, create, watch, files, projects, model configs) with API keys; experimental coder exp chat CLI; Go SDK (codersdk); built-in MCP server (local stdio and remote HTTP with OAuth2) exposes Coder workspace tools to other assistants; CI and webhook triggering is expected through the API. The headless-agents API is listed under the AI Premium plan on the pricing page.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. MCP client through admin-approved external MCP servers and workspace .mcp.json, skills from workspace .agents/skills and ~/.coder/skills, instruction files (AGENTS.md, CLAUDE.md, .cursorrules), project instructions and memory, ACP harnesses and templates as extension points. Authentication for MCP servers and per-plan MCP access are controlled by admins.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Web UI inside the Coder dashboard (React/TypeScript site) and a Go control plane; no desktop or mobile Agents clients.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Intake via prompts and attachments, API calls from CI and GitHub webhooks, and chat creation from other tools; no native issue import or two-way sync with external trackers.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Plan mode ("Plan first") lets the agent investigate and write a chat-specific plan file under .coder/plans, propose it for review with propose_plan and ask structured questions; plans persist in the chat and an Implement plan action resumes in normal mode. No acceptance-criteria field or revision history beyond the file.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sub-agents form a one-level hierarchy under a root chat (sub-agents cannot spawn more); no epics, blockers or readiness model.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Admin system prompt, project instructions, skills and durable project memory (early access), workspace instruction files and skills snapshots pinned per chat with refresh, chat history in the database; per-user and per-org scopes; retention and auto-archive controls.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Code search and edits through workspace tools (read_file, execute, edit_files), web_search when enabled, MCP tools, image and PDF attachments, computer-use sub-agent with virtual desktop; no repository index, citations or architecture checks.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Chats, projects, search with filters (including pr_status), pinning, archive, auto-archive, sharing; there is no issue tracker: tasks were migrated to chats.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No shared issue records; agents operate on chats, workspaces and sub-agents.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No living product specification; project instructions and memory are context, not maintained specs.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Many chats run in parallel; Community and Premium licenses allow five concurrently active agents deployment-wide (queued beyond that); chatd defaults to 5 concurrent root agents and 10 concurrent subagents; AI Premium removes the cap against purchased Agent Hours. Sidebar lists chats with 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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Work is queued when the concurrency pool is full; the root agent assigns work to sub-agents; no human assignment or claims.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Product-owned delegation: root agents spawn general, explore and computer-use sub-agents in parallel, optionally on a chosen model, with list_agents, wait_agent, message_agent and interrupt_agent; sub-agents cannot create workspaces or spawn more. Experimental ACP subagents add external harnesses. Results return via wait_agent; sub-agent chats are viewable by link.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No scheduler in Coder Agents; API calls from CI or webhooks can start chats as user-built automation; auto-archive and retention jobs are maintenance only.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Queued follow-up messages, interrupt, stop sub-agents, plan approval, structured questions, chat archive, resume; notifications for shared chats; compaction on demand.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Chat sidebar with projects, pinned and shared sections and search; no fleet board with blocked, awaiting 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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No mandatory workflow: describe the work, the agent chooses template and creates a workspace; Plan first mode, per-spawn model choice, admin-set system prompt, live sub-agent chats and retained transcripts.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The agent loop runs in the self-hosted control plane and tools run in Coder workspaces on infrastructure you operate (Kubernetes, VMs, cloud); chats and workspaces continue when the browser disconnects and can be continued from any device. There is 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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Each agent works in a Coder workspace provisioned from an admin template (container, pod or VM depending on template); workspace isolation per user; optional template pattern puts the agent in a separate pod with network policy (early stage); no git worktree isolation described.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Chat state persists in the Coder database so conversations survive workspace stop, delete or rebuild; the agent can resume in a new workspace from the last git branch; context compaction; queued messages; no automatic process re-attachment.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Environment setup is owned by Coder templates (Terraform), including dependencies, services and secrets; the agent only chooses a template and parameters; no agent-specific cache or port handling.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Deployment limits for steps per turn, generation retries, queued messages and attachments; exponential-backoff retry of classified transient provider errors; execute tool waits 10s by default; Agent Hours and concurrent-agent caps (5 on Community/Premium); AI Gateway per-user monthly budgets; context compaction thresholds and advisor limits.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Audit logs, chat debug logging and retention, AI Gateway monitoring and audit, Agent Time reporting to admins, in-app usage warnings, GitHub and PR status in chats; native per-chat cost pages were removed in favor of AI Gateway reports.
- **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

- **Coder Agents**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Spend per user and group through AI Gateway budgets and reports (entitlement required); native cost tracking removed; Agent Time (hours of model invocation) is measured separately for licensing; no per-chat or per-sub-agent cost display documented now.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Admission control queues agents beyond the concurrency limit (5 root, 10 sub-agent defaults); no CPU or RAM awareness or check deduplication.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Chats can be shared read-only with users or groups, with live streaming of updates and notifications; viewers cannot send messages, so no co-prompting. Projects are private to their owner.
- **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

- **Coder Agents**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Coder organizations and roles (Organization Admin, Owner, custom roles with model configuration access), multi-organization RBAC and OIDC group sync (Premium), OIDC login, SCIM 2.0 user provisioning (Premium, not fully spec-certified); agent permissions equal the submitting user; per-organization models and MCP servers.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Control-plane enforced model and tool configuration, plan mode, admin-approved MCP servers, template blocking for agents, per-user RBAC, network isolation templates; ACP subagent permission requests are auto-approved. The built-in agent does not prompt per command by default; control is by template, network and RBAC rather than per-call approval.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Premium audit logging records project, instruction, skill and memory changes and user actions; chat history persisted with retention (default 30 days archived) and debug logs; export through API; chats attributed to users.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. In-chat diff viewer for GitHub and GitLab with PR/MR status, plan proposals for review, attachments, search by PR status; no review queue or request-changes workflow.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sharing is read-only; there is no takeover by another user; chats are owned by one user and agent actions stay attributed to them.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Retained: chat transcripts, diffs in-chat, attach_file durable attachments, file attachments with expiry, plan files, PR status; no gallery of recordings or screenshots beyond computer-use sub-agent and attachments.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No built-in gate: tests and linters run through the execute tool when asked, with no required-check policy in Coder Agents; template and CI policies live outside the product.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Git work happens in workspaces under the user identity with external auth; PRs opened by the agent are attributed to the user; chats link to a PR whose state (draft, open, merged, closed) is searchable; in-chat diff viewer; GitHub and GitLab supported.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Merging and deployment are performed through the git provider and CI under the user permissions; Coder Agents does not provide merge or deploy 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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Chats link to PRs with status; no build, deployment or rollback tracking.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No batch review queue; chat list with PR-status search is the closest filter.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Coder core (control plane, dashboard, chatd, CLI) is AGPL-3.0 at v2.39.4; enterprise-licensed code under enterprise/ (audit, AI Gateway, aiseats) is source-available under LICENSE.enterprise. Coder Agents code lives in the AGPL tree (coderd/x/chatd); some governance features are entitlement-gated.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Fully self-hosted: control plane, database and agent loop run on your infrastructure with no vendor service except Agent Time usage reporting (hours only) for licensed deployments; chats and data stay in your database; export through the API; standard formats not described.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Prompts and code go from your control plane to the LLM providers you configure; chat history stays in your database; LLM keys never enter workspaces; Coder collects installation telemetry by default (opt-out with CODER_TELEMETRY_ENABLE=false) and, for licensed deployments, hourly Agent Time totals (no user data) go to Coder; retention defaults to 30 days for archived chats.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Community is free for self-hosting with up to five concurrently active agents; Premium is priced per user per year (amount not shown) and includes Coder Agents with the same five-agent pool; AI Premium is custom priced with unlimited agents against purchased Agent Hours. Model and infrastructure costs are separate.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Scenario costs cannot be priced publicly: Community software is free, while Premium and AI Premium prices are not published.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Maintained commercial open-source product with patch releases on 2026-11-16 across v2.39 and v2.38 lines, GitHub and Discord community support, SLA-backed support on Premium; several agents features are experimental or early 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 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

- **Coder Agents**: 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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Ongoing free tier: Community is free and self-hosted with up to five active Coder Agents; Premium and AI Premium paid; AI Premium trial button without stated terms.
- **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

- **Coder Agents**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Units are stated (per user per year for Premium, Agent Hours for AI Premium) but amounts are not published; AI Premium is custom.
- **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.
