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

# kodo 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; 33 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.

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

## Access and agent choice

### ACC-01: Client access

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Terminal CLI on Windows, macOS and Linux (CI matrix covers all three) plus a loopback local web dashboard and an HTML log viewer for inspecting runs; no desktop app, mobile app or editor extension.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium ships desktop, CLI and browser clients, including phone-browser control. The native iPhone app is private beta; the complete download offering contains no native Android app.

### ACC-02: Agent and model choice

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Seven session backends launched or driven locally: Claude Code (claude-agent-sdk), Cursor CLI, OpenAI Codex CLI, Gemini CLI, Kimi (ACP), Kiro and OpenCode; orchestrator model via pydantic-ai providers or a CLI backend. Mixed-harness teams are native.
- **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

- **kodo**: Sourced (sourced); support: supported. Checked 2026-11-17 (5 days old); not separately cross-checked. Reuses installed agent subscriptions (Claude Max/Pro, Cursor, ChatGPT, Gemini free tier, Kiro) through each native CLI login, supports API keys for the orchestrator, and local Ollama for the orchestrator only. No vendor credits.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports native coding-agent logins and managed provider credentials. Claude subscriptions (via native login or a managed setup-token) and local ChatGPT/Codex login are supported paths, alongside Anthropic and OpenAI API keys. Docs list billing and hosted metering as not implemented product claims.

### ACC-04: Onboarding and project prerequisites

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Install with `uv tool install kodo-agent`, install at least one agent backend CLI, set an orchestrator API key, then run `kodo` interactively or with --goal. Works on any directory; Git is optional but recommended and needed for parallel worktree stages.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Programmable through the CLI (--json, non-interactive flags, --resume, runs/logs subcommands), a Python library API, and the local dashboard REST/SSE routes; no external MCP server, webhooks or stable-API commitment.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. kodo itself is an MCP client only through its backends; it adds an internal team MCP bridge for CLI orchestrators and has no plugin system. Team roles accept custom system prompts; instruction files are read natively by each backend.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. CLI is a Python 3.13 package (setuptools, uv tool install); the web dashboard is a plain HTML/CSS/JS page served by a stdlib HTTP server. No native, Electron, Tauri or mobile client.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Work enters as a goal (inline text, goal file, interactive interview with optional Claude refinement) or as test/improve/fix-from modes. No issue-tracker import, Git or chat triggers, and no external tracker relationship.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium issue records are native and authoritative with stable references, CLI creation and editing, and agent-driven filing from conversation. The in-product assistant has Linear search, create and move tools when a key is configured, but no import or two-way tracker sync was found.

### PLAN-02: Durable task plans

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Intake produces a GoalPlan of ordered stages each with a description and acceptance criteria, stored as goal-plan.json per run; stages can be edited through the dashboard and advisors can append stages. No revision history.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Issue brief, acceptance criteria, state paragraph and todos persist on the durable issue record. Release 0.3.0 removed the separate design and notes fields and appended their text to the brief. On the human issue page the title, description and acceptance are editable and the brief is read-only; agents edit the brief and other fields through issue commands.

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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Stages are an ordered list with optional parallel_group; no epic hierarchy, blockers or readiness model. Stages run sequentially unless grouped, and groups run in git worktrees with a persist_changes merge-back.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Per-run summaries bridge cycles; the project can carry .kodo/config.json, .kodo/team.json and .kodo/test-coverage.md; agents read repository CLAUDE.md/AGENTS.md through their own CLIs. No cross-run semantic memory.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. v0.3.0 routes Podium issue instructions and relay environment through terminal and engine session launch. Claude stream sessions use appended instructions and boundary callbacks; Codex server sessions use developer instructions, Grok ACP uses rules, and OpenCode uses the prompt system field. Claude and Codex boundary hooks can re-prime after compaction. Transcript mirroring is on by default; full-text indexing needs the command-palette flag, which defaults off. Agent profiles can carry markdown instructions. Curated memory, skills and memory correction or deletion controls remain unestablished. No instruction-delivery or compaction scenario was run.

### PLAN-05: Architecture and API awareness

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No code index or retrieval layer; agents search through their own CLIs. kodo adds a coach/advisor and an architect reviewer role but no architecture-conflict detection tied to a maintained model.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No native issue management; work items are per-run stages, and `kodo issue` only opens a pre-filled GitHub issue for kodo itself.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Agents have no access to a shared durable issue store; stage plans and run files are private to the run.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No living product specification: acceptance criteria are per-stage, and mission.md/docs in the kodo repo are its own maintainers documents.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. One run executes cycles sequentially; stages in the same parallel_group run concurrently in separate git worktrees, capped by KODO_MAX_PARALLEL (default 2). A terminal progress table, the dashboard and the log viewer show agents and stage status.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. The orchestrator assigns work to named team roles through dispatch tools; stages are assigned by the planner. There are no human assignees, queues, claims or routing rules.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Product-owned orchestration: an orchestrator model (API, or Claude Code/Gemini/Codex/Cursor/Kimi CLI with an MCP bridge) delegates to team agents, each with its own backend, model and turn budget, and receives their reports. Verification roles are separate agents. An optional coach/advisor adds messages.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No scheduler, event trigger or recurring task. README recommends external cron for overnight non-interactive runs, which is a manual workaround.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Stop by interrupting the CLI; resume with --resume. Steering is limited to appending lines to human_feedback.txt (with --coach); the dashboard feedback and stop endpoints are unimplemented stubs. No notifications.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Chat and native CLI views share a session. v0.3.0 defaults human controller chat to steer and immediately types it into running Claude Code, Codex, Grok and OpenCode TUIs that declare native busy-input queuing; undeclared harnesses wait for a boundary, and compaction waits. Mail and automation keep when-ready delivery. Stop, resume, questions, decision issues and offers remain available. This is inspected implementation, not a cross-harness runtime parity result.

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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. The dashboard and viewer show runs, stages, cycles, agent events and stats for one run at a time with a run list; no cross-epic fleet board.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Workflow is a fixed staged loop (goal, improve, test, fix-from) with configurable teams, effort and model per agent set in JSON or flags before the run; roles and relationships are visible in the live table and the retained log. There is no natural-language reconfiguration during execution.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Runs wherever the CLI runs: your machine or any host or VPS you start it on. kodo has no managed cloud, hosted control plane or detach-and-reconnect service; a run lives in the foreground process and is resumed from logs.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Agents work in the shared project directory by default; parallel stage groups use separate git worktrees and branches that are merged back. No container or VM isolation; Claude runs with bypassPermissions and can access the whole machine.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Runs persist event logs and plans; `kodo --resume` finds incomplete runs and continues, resuming agent sessions where the backend supports it (Claude, Cursor, Codex, Gemini CLI, Kimi, Kiro). Crashes lose the in-flight agent turn; stale worktrees are cleaned.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. kodo does not manage dependencies, caches, snapshots, services or ports: agents install what they need in the project. The test mode prompts testers to build their own fixtures and report blocked workflows.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Per-agent max_turns and timeout_s, adaptive idle timeout (300 s) with a 75 minute cap, per-cycle exchange and run cycle limits, Claude fallback model, and error-pattern detection for subscription/rate-limit failures. No token or spend caps.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes retryable errors, optional auto-continue with backoff, bounded waits and provider quota. Claude stream and hosted headless drivers enforce a supplied turn deadline, with no deadline when timeoutMs is absent. The one-shot headless server runner supplies its budget, default ten minutes. Agent spawns have a daily per-issue budget. Operator-configurable task-wide turn, token and spend caps remain unestablished; quota display is not enforcement.

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

- **kodo**: Sourced (sourced); support: partial. Checked 2026-11-17 (5 days old); not separately cross-checked. Structured log.jsonl events, conversations per agent, live terminal table, dashboard stats and viewer; token and cost per session with API versus virtual buckets. No success-rate statistics beyond what the log shows.
- **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

- **kodo**: Sourced (sourced); support: partial. Checked 2026-11-17 (5 days old); not separately cross-checked. Per-session and orchestrator cost in two buckets, API (real spend from the orchestrator API) and Virtual (subscription-covered cost that the Claude SDK reports), plus input/output tokens; aggregated per run. Native Kimi and Kiro do not report usage.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Concurrency is bounded by KODO_MAX_PARALLEL (default 2) and per-agent turn/timeouts; no CPU/RAM awareness, queues 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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Single-user local tool. The loopback dashboard is not shared; no comments, presence or multi-user prompting.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No organizations, roles, SSO or provisioning; access is whoever can run the CLI or reach the loopback dashboard.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No kodo approval system: Claude agents run in bypassPermissions mode and Codex in workspace-write; the README warns they can access any file. Safer behaviour is only whatever each backend CLI offers.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Append-only log.jsonl with timestamped events per run (agents, tool calls, errors, cost) and saved conversations; local files, no user attribution, export, retention or integrity guarantees.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Review is by reading logs/viewer and the resulting Git diff in your own tools; kodo has reviewer agents (architect, testers) but no diff or review UI, request-changes flow or keyboard/narrow-screen guidance.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Review is a documented loop: issue stage review, diff and checks, artifacts, offers with merge or send-back buttons, and a Tray of review-ready work. Release 0.3.0 adds quoting text from a reply or review finding into the next message and a full-height reading view with an outline. The board has a key map with a help sheet. Guided-review quality and narrow-screen use were not measured.

### TEAM-06: Colleague takeover and continuity

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No colleague takeover: runs live on one host in one user directory; another person with the same files could resume a run with --resume, but there is no ownership transfer, attribution or shared runtime.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Retained outputs are run logs, conversations, summaries, reports (including tester and reviewer outputs) and a coverage file; code changes live in the working tree or branches. No screenshot/recording gallery or previews.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Verification is orchestrator-directed: done() asks testers, a browser tester and the architect to verify and parses an ALL CHECKS PASS signal; the README states there is no enforced independent gate. No built-in lint/type/CI gate and no spec conformance.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Local Git only: worktrees and branches for parallel stages, --no-ff merges with agent-assisted conflict resolution, and an agent-run auto-commit (never pushes). No PR creation, review comments or CI response.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No approve, merge-authority, release or deploy workflow beyond local merges of kodo-created stage branches.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Delivery evidence is commits created by auto-commit and log events; no task-to-PR, build or deployment links, rollback or stale-approval invalidation.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No batch review queue: each run reports its own summary; kodo issue and the viewer do not group, filter or approve completed work.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Open source under MIT (LICENSE and pyproject); single Python repository (CLI, dashboard, viewer, benchmark harness). No hosted service or closed extension.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Fully local: install the package, bring your own backends and keys. Run data is plain JSON/JSONL/Markdown under ~/.kodo/runs; no vendor account, so nothing needs cancelling.
- **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

- **kodo**: Sourced (sourced); support: partial. Checked 2026-11-17 (5 days old); not separately cross-checked. Code, prompts and logs stay local and go to whichever model providers your backends and orchestrator use. kodo has no telemetry SDK; an opt-in KODO_TRACE_UPLOAD=1 uploads redacted run traces to a maintainer-owned GCS/Firestore project.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Free and open source (MIT) with no kodo price; users pay their model providers and subscriptions (Claude Max/Pro, Cursor, ChatGPT, API tokens).
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No catalog scenario pricing: kodo has no platform fee and the README gives one example (Gemini Flash orchestrator about $0.13 per run, workers on subscription). Team and compute scenarios are not modelled because workloads are not defined.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Pre-1.0 open-source project (Beta classifier, PyPI 0.5.1 on 2026-06-23); default branch active through 2026-09-26 with unreleased changes; support through GitHub issues (including an automated CI-assistant workflow). No SLA or status page.
- **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

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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. Free open-source tool (MIT); a zero-cost route exists with Gemini CLI plus a free Google API key or Ollama for the orchestrator. Everything else depends on the agent subscriptions you already hold.
- **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

- **kodo**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-17 (5 days old); agent cross-checked 2026-11-17. No kodo pricing: free MIT software; model and subscription costs are third-party. Classification: no paid plan (transparent: nothing to charge).
- **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.
