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

# Lody 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; 37 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.

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

## Access and agent choice

### ACC-01: Client access

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-17. Desktop installers cover macOS Universal, Windows x64 and Linux x86-64; native iOS/Android apps, a hosted web app and the lody CLI expose the workspace. The hosted web client has a production phone renderer selected from mobile browser user agents independently of native app shells. Editor extensions are absent; external-editor launchers are separate.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-17. Nine built-in ACP providers plus every ACP Registry runtime and Custom ACP launch commands; Lody launches provider servers, negotiates capabilities and reuses machine-side logins. Mixed-harness sessions run side by side and coordinate through a primary agent.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Existing agent subscriptions and API/env credentials stay on the machine and are reused at zero markup; Lody sells no tokens. A Lody account is required for cloud workspaces while local-only use and lody review work without sign-in.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Quick Start covers install, sign-in, project add, agent-config test and first session; plain directories, local Git repos and GitHub repos are all supported. The daemon onboards BYO servers; no vendor-managed compute onboarding exists.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. The lody CLI manages the full session lifecycle with --json output, and Lody hosts its own session-tools MCP server (stdio + HTTP) while acting as an MCP client. No public REST API, SDK, or webhook receiver exists.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Workspace MCP catalog with OAuth and per-transport negotiation feeds agents; custom ACP commands, AGENTS.md/skills/roles imports and keychain-backed auth are product-managed while runtime behavior is inherited from the harness.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Desktop is an Electron app (pinned source); mobile ships as native iOS/Android apps whose client code post-dates the pinned release. No hybrid wrapper is documented.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Sessions start locally from composer, prompts, schedules or the CLI; GitHub issues/PRs inject context via @ while GitHub stays authoritative for tracker state; session IDs are durable and PR comment sync is two-way.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Rounds pair each agent turn with its diff and stay revisable through history, restore and steering; durable cross-session plan objects with acceptance criteria do not exist as product entities.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Parent/child structure exists as forks, side chats, child tabs and delegated conversations with preserved lineage, but no epics, blockers, readiness or enforcement objects exist; scoping guidance is advisory.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Repo instruction files, mentionable skills, browsable project files and per-session memory persist; handoff carries context to teammates. Provenance, staleness controls and cross-session memory are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. In-UI text search, a session browser panel, and image/file multimodal inputs are product features; indexing, retrieval grounding and review-time enforcement belong to the underlying runtimes, not Lody.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Sessions act as durable tasks with archive/restore, search, metadata and PR linkage, dispatchable on send or schedule, without requiring GitHub. Prioritization, labels, assignment, filtering and idea parking do not exist as product features.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Agents operate on the same durable session IDs humans use — creating, reading, messaging, cancelling and spawning child conversations with results returned and human-visible attribution — gated by workspace and machine sharing. Claims, dependencies and conflict handling are not product concepts.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. No living product specifications exist: documents and document sandboxes are explicitly planned for the future, and shared docs remain on the planned team-features list.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Independent sessions run concurrently in isolated worktrees with team-visible statuses; workspace session caps and host-machine capacity bound scale. No hands-on concurrency run was performed.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Humans join via membership and handoff; agents receive work through composer selection, saved roles and delegation prompts without locks or queues. Machine sharing gates who can run where.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. A product-owned MCP layer lets any session act as coordinator: create, message, steer and cancel other sessions across machines and harnesses with retained relationships and visible progress. Provider-native subagents surface through declared extension capabilities.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Schedules, manual tasks and one-shot sends run on an owning machine with serialized overlap handling and single catch-up; agents may propose but never create schedules. PR merge/close events drive auto-archive; no generic event triggers exist.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Stop, resume, steering, actionable permission prompts and best-effort notifications span desktop, mobile, web and CLI with retained history. Session-level pause and escalation paths are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. The home session list with statuses, PR states, diff stats and filters is the fleet view, backed by attention signals and retained history. Dependencies, workload planning and error/fixture chrome are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Roles, natural-language configuration, per-agent model/effort controls and retained delegation lineage make execution visible and reconfigurable without mandatory presets. Mid-run model changes and auth friction details are only partly established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Agents execute on the user's own machines (desktop or BYO server/VM) connected by the daemon; the vendor cloud only relays and stores workspace data. Work survives the controlling client and continues from any device while the execution machine stays online.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Each session gets its own Git branch and worktree directory for file separation; credentials stay machine-local in the OS keychain. No container, VM or OS-sandbox boundary exists, and worktrees are not a security boundary.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Client disconnects, restarts and offline stretches recover through daemon persistence, catch-up sync and worktree recreation from kept branches. Crash-recovery semantics and multi-day guarantees are only partly documented.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Per-project setup/cleanup scripts with LODY_* env vars prepare every worktree; secrets arrive via agent-config env and keychain. Snapshots, managed services, collision handling and automatic repair are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Free-plan turn caps and schedule serialization bound usage; rate limits and quota states surface visibly with a scheduled-continue path. Timeouts, retries and spend controls are internal or provider-side, not Lody budgets.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Live terminal output, log files, failure states, PR checks, per-member usage trends and session export are all observable; presence reconnects keep views consistent. Traces, project rollups and performance claims are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Token, context, quota and machine-resource usage is visible per session and broken down by model and member, but money never attaches: Lody bills only the workspace while providers bill their own accounts.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Parallelism is bounded by host capacity, plan session caps, an internal ACP startup queue and serialized schedules, with cancellation and restore for recovery. Resource-aware limits, fairness and verification reuse are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-17. Team sessions are visible, commentable and hand-off-able with attribution and plan-scoped membership; execution needs the machine online, not the original owner. Simultaneous co-prompting, ordering and conflict handling are not established. A separately invited workspace teammate can open the existing live session and send the next prompt to the same agent with its conversation, worktree and diffs. This establishes shared-human sequential prompting, not simultaneous prompt conflict guarantees.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Owner/Admin/Member workspace roles with invite, edit, remove and revocation flows; Enterprise adds SSO and access controls. Per-project and per-task roles plus SCIM provisioning do not exist.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Per-session permission modes gate agent actions with mobile approval prompts, Full Access defaults and safer scoped modes, enforced by the product and E2E machine policy. Per-type approval matrices, lifetimes and multi-approver identity are not detailed.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Attributed history persists across users and sessions with export paths; retention ends at user deletion with a 30-day clearance SLA. Formal decision links and an integrity model are not established, and the word audit is not used.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Reviewers locate work through statuses and notifications, read round diffs beside evidence, comment, request changes and ship via Create PR and merge, with keyboard shortcuts and mobile review support. Effort analytics and missed-evidence detection are absent.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. A teammate takes over the identical live session — conversation, decisions, artifacts, worktree and runtime context — after invite plus machine/project sharing, with attribution and documented loss modes. Ownership transfer and cross-harness session migration are not established.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Round and whole-conversation diffs, images, previews, validation outputs and shareable HTML review reports persist per session with task and revision links. Documents, recordings and cross-task galleries do not exist.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Tests, lint, types and CI run through agents and surface in-session with review loops available, but every gate is optional and unenforced; spec conformance cannot exist without product specs.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Branches, worktrees, commits, PR creation, review comments, CI response and merge run product-integrated through the GitHub App. Rebase and conflict handling are agent-side and undocumented as product flows.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. PRs merge from Lody (optionally as the GitHub user) with branch cleanup; approvals surface as comments and reviews without a distinct approve authority, and release or deploy authority does not exist.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Task-to-commit/PR links, delivery status and retained review evidence persist per session; rollback and stale-approval invalidation do not exist (the only revert in-tree is internal session-create cleanup).
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. The session list with per-item summaries, grouping, review threads and per-session ship actions supports high-volume review item by item; risk filters, merge queues, revision-locked approvals and check deduplication do not exist.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Pinned release tree (CLI, desktop, packages, docs) is Apache-2.0; native mobile client code post-dates the pin with upstream credit, and the vendor sync backend stays closed.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Apache source, workspace export with JSON/offline support, Markdown/HTML portability and email-driven account deletion cover exit; vendor services (Convex sync, GitHub App, push) are required for cloud workspaces while local-only use and lody review work independently.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. LoroHub LLC collects account, device, log and conversation data processed by named subprocessors with export/deletion rights; E2E workspaces restrict reads to authorized devices, while standard workspaces are readable by members and Lody servers. Telemetry is disclosed (PostHog/Sentry/GA) with no documented opt-out or first-run consent.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-17. Prices are USD: Free is $0 forever; Plus is $10 per seat per month billed monthly, or $8 per seat per month billed yearly; Enterprise is custom. Free includes 2 workspaces, 200 sessions per workspace, 30 turns per session and up to 3 members. Lody charges for the collaboration workspace, while users supply agent/model accounts at zero markup.
- **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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. One developer: $0 (Free) or $96/year (Plus yearly); two: $0 or $192/year; five: Plus $480/year (Free caps at 3 members). Model and compute costs are BYO and unknown; no fixed task/token/hour assumptions are published.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

### OWN-06: Availability and support

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Publicly downloadable with email/Discord/X support (typically days, no commitment), active releases (v0.109.0 on 2026-10-30, pushes through 2026-11-13) and email-driven export/deletion. No staged rollout, status history, or deprecation program is documented.
- **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

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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Free plan is ongoing ($0, no trial clock) with mobile, BYOK, 3 members, scheduled tasks and handoff-capable sharing; two-person collaboration fits, five-person needs Plus. Card requirements and paid-evaluation needs are not documented.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium 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

- **Lody**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-13 (9 days old); agent cross-checked 2026-11-13. Pricing states per-seat subscription units with included limits and zero token/compute markup, but the monthly-cadence figure, minimum commitment, cancellation mechanics and tax handling are missing: partially specified.
- **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.
