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

# OpenChamber 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

43 criteria sourced for both products; 29 criteria also agent cross-checked for both. 48 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.

- OpenChamber source checks: 2026-11-08 to 2026-11-13. Details: https://podium.do/compare/agents/products/openchamber/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/openchamber-vs-podium/
- Machine-readable JSON: https://podium.do/compare/agents/openchamber-vs-podium/data.json
- Methodology: https://podium.do/compare/agents/methodology/

## Access and agent choice

### ACC-01: Client access

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. OpenChamber has macOS, Windows and Linux desktop clients, a web/PWA client, VS Code extension and a CLI/server. Desktop bundles a matching OpenCode CLI; web/VS Code use an installed OpenCode CLI. Native iOS uses TestFlight beta and Android is a Canary APK. Phone apps can view sessions, reply and manage work; Safari/Chrome phone browsers can install the PWA. These clients connect to the user server.
- **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

- **OpenChamber**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. The core workspace uses OpenCode to run coding agents. Model/provider selection through OpenCode does not establish another named harness by itself. The optional Claude Code integration uses the official Claude Agent SDK with the installed Claude Code CLI and supported sign-in. This is distinct from ordinary OpenCode provider configuration. OpenChamber v2.7.0 lists Antigravity as a quota provider reading OpenCode Antigravity account files. That does not establish an Antigravity coding-harness adapter. The scoped native session adapters have no integration for Codex, Cursor Agent, Gemini CLI, Pi, Grok, Aider or Antigravity harness sessions.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The Claude Code integration reuses Claude Pro or Max through the local Claude Code CLI sign-in without API keys. Setup can install the CLI and sign in. OpenCode stores provider API keys and device-flow sign-ins. Custom OpenAI-compatible providers are configurable; signing into a model provider is separate from a native agent subscription.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Desktop bundles OpenCode; CLI/Web requires Node.js 24.14+ and an installed OpenCode. Users start a local server protected with a UI password before connecting devices.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Product CLI commands expose status, connect QR links, tunnels, startup control, logs, stop and update. A stable public session API was not inferred merely from the internal web app.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Users configure local command or remote URL MCP servers with headers/environment settings, scoped personally or per project. Servers can be disabled without deletion. Extensions can add git hosts, trackers, tools, UI and notification destinations. Local services require explicit permission in extension settings.
- **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

- **OpenChamber**: 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**: 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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Git host issues and PRs become context for a new worktree/session; the message is not sent automatically. Supported hosts include GitHub, GitLab, Gitea, Forgejo and Gerrit changes.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Plans are editable Markdown files retained at project level, imported from text/Markdown and optionally moved into the repository. Agents update checklist steps, and the UI shows progress from the Steps section.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Agents can link todos to a plan and add dependencies on other todos in that plan. Ready-todo queries return unfinished items with completed prerequisites; standalone todos have no 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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Project notes can be pinned into a session. Optional memory is off by default, scoped About you or Project, editable and forgettable, with agent-led tidy-up and visible changed markers.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Changes Walkthrough groups code-related edits, reads code/docs/tests and anchors its explanation to exact diff content; outdated or uncovered changes are labeled. This is explanation, not a code-quality verdict.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The native project todo checklist persists across sessions, supports checked completion and ordering, and can dispatch an item into current/new/worktree sessions. It is separate from external tracker items and the chat-session list.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The managed-server project knowledge tool lets agents read and edit the same notes, plans and todos humans see, link dependencies and query ready work. It is unavailable with an external OpenCode server or VS Code extension.
- **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

- **OpenChamber**: 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**: 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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Multi-run starts several model sessions from one prompt, optionally each in its own worktree/branch. A failure to start one session does not prevent the rest from launching.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The native control tool creates sessions, sends prompts or follow-ups and can create worktree sessions. New-session prompts return immediately unless followed later.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. An agent can create a child session with a selected model, list status, read the latest assistant response and send follow-ups. These tools belong to OpenChamber-managed OpenCode installations, not external servers or VS Code.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Native scheduled tasks send prompts in new sessions once, daily, weekly or by cron, optionally as goals. The OpenChamber server must stay running. Repository loop files require local enablement and renewed approval after material changes.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Stop and Pause abort the current turn and pause a goal; Resume re-arms it. Completion, blocking or exhausted budget emits one final notification while permission/questions/errors remain visible.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The In work sidebar groups ongoing sessions and worktrees, shows status and news, and permits marking work done or returning to it. No measured six-task navigation scenario was run.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Natural-language requests can create another model session, an isolated worktree or a schedule, and inspect results later. Project paths and arbitrary shell actions are outside this tool.
- **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

- **OpenChamber**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. OpenChamber can run as desktop app or CLI/server on a workstation or the user's own server. Its goal loop runs in that server, so closing the browser tab or locking the phone leaves the agent working; the desktop app or openchamber process must stay running. The scoped startup code provisions a local/user-hosted OpenCode process; Private Relay carries traffic and is not vendor execution.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The published Podium execution choices are local user machines and a user-owned VPS or paired machine. No vendor-operated agent host is in the complete download offering.

### RUN-02: Workspace and process isolation

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-10. A worktree session has its own checkout and branch to isolate concurrent edits; optional multi-run isolation creates one per model. Nongit folders do not get worktree isolation.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.

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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Archived worktrees preserve sessions, uncommitted changes and branch data for restore, but ignored files such as node_modules and .env are not retained. Active sessions prevent archive removal.
- **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

- **OpenChamber**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. Project setup commands run after worktree creation and on restore. Ignored dependencies/secrets must be reconstructed by setup; separate-worktree uncommitted edits are not copied automatically.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Goals have optional token budgets, an automatic-continuation cap and stop on turn errors. Blocking requires three consecutive stuck audits. Raising a budget and resuming is explicit.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The UI shows working, waiting, finished and failed sessions with approvals, schedules, provider limits, token use and costs. These are documented statuses; reconnect consistency has not been tested.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Usage shows provider windows, model breakdown and pace; the agent usage tool can query those provider numbers and resets. This is provider allowance visibility, not a reconciled task invoice.
- **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

- **OpenChamber**: 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**: 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

- **OpenChamber**: Sourced (sourced); support: partial. Checked 2026-11-13 (9 days old); not separately cross-checked. Native browser and paired-device clients can access the same server identity. This establishes multi-device access; distinct-human shared prompting remains unestablished.
- **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

- **OpenChamber**: Sourced (sourced); support: partial. Checked 2026-11-13 (9 days old); not separately cross-checked. The scoped native authentication uses a shared server password, passkeys and device credentials. The inspected modules have no named workspace/organization human roles or SAML/OIDC team SSO integration.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. OpenCode permission rules allow, deny or ask. OpenChamber Ask every time, Safety net or Accept everything determines who answers ask; deny remains blocked. Safety net requires a classification provider and holds requests on uncertainty or timeout.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Agent-created notes are labeled and stale whole-document replacements can be refused against the prior text. This is not a tamper-resistant audit log.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. A guided walkthrough groups related edits into ordered stops with code anchors, shows outdated/uncovered areas and supports line/file comments into chat. It is available on desktop, tablet and phone, excluding VS Code.
- **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

- **OpenChamber**: 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**: 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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Preview places the running app beside chat and can send element screenshots, styles and errors as agent context. Diffs and guided walkthroughs retain review context. A cross-task artifact gallery was not established.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. A separate model auditor compares the latest turn to the goal, continuing until done, blocked or budget/turn limits. It only sees the objective and latest reply, so this is not a general test/CI/spec approval gate.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The Git panel can create/update PRs, mark drafts ready and merge, with equivalent merge requests or Gerrit changes per host. Issues/PRs can start scoped worktree sessions.
- **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

- **OpenChamber**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. Users merge from the PR panel; Gerrit Submit waits for the change submit requirements. Worktree Integrate brings commits to another branch and can ask the agent to resolve conflicts. No production deployment authority was tested.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Walkthrough explanations are bound to exact code content. Changed anchors are marked Outdated and new uncovered changes are listed rather than silently reusing a verdict. This is not an approval-invalidating merge gate.
- **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

- **OpenChamber**: 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**: 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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The OpenChamber application source is MIT licensed at the pinned revision. OpenCode and optional provider plugins retain separate component terms.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The full workspace/server can run on a user workstation or own server; optional Private Relay and tunnels provide connectivity rather than replacing the user runtime.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-10. A Send anonymous usage reports switch in Settings turns off usage reporting, and Enterprise mode forces it off. Enterprise mode also restricts conversation-content features to configured OpenCode providers and can pin relay endpoints and trusted extension repositories through an administrator policy file.
- **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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The source application is available under a free-of-charge MIT grant. User model/provider usage and runtime hardware remain separate costs.
- **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

- **OpenChamber**: 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-06: Availability and support

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. OpenChamber v2.7.0 was published November 8. Mobile remains TestFlight/Canary access; public issues cover sidebar visibility, composer gestures and mobile shortcuts. Issue reports were not reproduced.
- **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

- **OpenChamber**: 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

- **OpenChamber**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The core application is free MIT software with user-hosted execution. Model and own-compute charges are excluded; mobile evaluation uses the documented beta/nightly channels.
- **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

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