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

# Podium vs vibe-tree

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

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

## Access and agent choice

### ACC-01: Client access

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Electron desktop app (macOS arm64/x64, Windows x64, Linux x64), a React PWA served by the standalone server (usable from phone browsers), a `vibetree` CLI and the server API. No native iOS/Android app or editor extension. A Windows launch crash is reported (issue 136).

### ACC-02: Agent and model choice

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Harness-agnostic terminal launcher: any CLI agent (Claude Code, Codex CLI, Gemini CLI, Aider, opencode named by the project) runs in a PTY per worktree. No model providers or API are embedded; activity detection is tuned to Claude Code prompts.

### ACC-03: Subscriptions, API keys and 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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Uses whatever login or key the launched agent CLI has; the project states users bring their own agent subscriptions. No vendor credits, account or key handling in VibeTree.

### ACC-04: Onboarding and project prerequisites

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Install the desktop app (or run the server), open a Git repo, create a worktree and launch an agent command in its terminal. Requires an existing Git repository; no remote or account needed. Docker VM deployment is documented.

### ACC-05: Programmable access

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The podium CLI covers issue create, show, update, claim, dependencies, artifacts, session send/status/read/stop and review actions, and the server exposes the same issue commands as a bearer-token MCP tool endpoint. No documented public HTTP API, SDK or webhooks were found.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The `vibetree` CLI and the server REST/WebSocket API (the same API the web app uses) can create and remove worktrees, list sessions and agent states, start shells and type into them; there is no SDK, MCP server or webhooks.

### ACC-06: External tools and extensions

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. VibeTree has no MCP, plugin or tool layer of its own; agent CLIs bring their own MCP and plugin support. It offers lifecycle hooks, an agent preset and an IDE launcher.

### ACC-07: Client implementation

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Desktop is Electron (Vite React renderer, embedded Express/WebSocket server on loopback); web client is a React PWA (Vite, vite-plugin-pwa); no mobile app.

## Planning and context

### PLAN-01: Intake and 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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Intake is typing a branch name (worktree) and a prompt to an agent terminal, or `vibetree run <branch> "prompt"`. No issue import, tracker or Git-event triggers.

### PLAN-02: Durable task plans

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. No plans: tasks are prompts typed into agent terminals; the project agent preset and hooks are the only persisted setup.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Flat list of worktrees per project; no epics, hierarchy, blockers or readiness.

### PLAN-04: Shared context and 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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Agents read their own repo instruction files; VibeTree stores only a per-project agent command and hook scripts in `.vibetree/` and keeps terminal scrollback. No memory or shared-context feature.

### PLAN-05: Architecture and API awareness

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. No code search, indexing, retrieval or multimodal input; the product runs terminals and shows Git diffs.

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

- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes native issue creation with an optional start flag, separate dispatch, editing, comments, labels, assignment, search, board filters, archive, sibling ordering and an issue tree. Issue records have their own identity separate from sessions and stages are durable. The idea-to-mission scenario was not run. v0.3.0 refuses an agent close or done update while issue sessions are computing unless --confirm-interrupt is supplied; guidance says to request review and close only on user instruction.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No issue or idea backlog; the work list is the Git worktree list per project with a live agent-state badge.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agents are plain terminal programs without VibeTree tools; the REST/WebSocket API lets scripts create worktrees and type into sessions, but there are no issue IDs or fields.

### PLAN-08: Living product specifications

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. No living product specifications.

## Coordination and automation

### COORD-01: Parallel work

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. One PTY session per worktree and terminal run concurrently; a fleet badge shows working, needs input, done and idle; no stated concurrency limit.

### COORD-02: Ownership and dispatch

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No assignment, claims or queues; the user chooses which worktree and terminal to use. Sessions are deterministic per worktree path and terminal ID so a reconnect reuses the same shell rather than duplicating it.

### COORD-03: Inspectable delegation and communication

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. No product-owned delegation: agents are independent terminal programs. Their own subagent features are not surfaced.

### COORD-04: Unattended triggers

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. A desktop-only command scheduler queues a command or prompt for a terminal after a delay, once or repeating; no cron, event triggers or completion conditions; it stops when the app closes.

### COORD-05: Intervention and attention

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Stop by terminating a session; resume by reattaching; steer by typing in the terminal; desktop notification and web sound when an agent needs input; question detection uses heuristics for Claude Code-style prompts.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. A worktree sidebar with live state badges (idle, working, needs input, done) and unstaged-change counts, plus a welcome table of worktree states; no epics, dependencies or history timeline.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No presets beyond the project agent command; any terminal workflow can be used. Orchestration is manual.

## Execution and reliability

### RUN-01: Laptop-independent execution

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The published Podium execution choices are local user machines and a user-owned VPS or paired machine. No vendor-operated agent host is in the complete download offering.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agent work executes where the VibeTree server runs: the user's machine (desktop) or a user-managed host running the standalone server/Docker. No vendor cloud; sessions keep running on the server after clients disconnect.

### RUN-02: Workspace and process isolation

- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. One Git worktree and branch per task; a PTY per session. No per-agent container, VM or OS sandbox; the whole server can run in Docker. A worktree is not a security boundary.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sessions persist across client disconnects with bounded in-memory scrollback; they do not survive a server restart (disk persistence is a roadmap item); a crashed agent leaves the shell.

### RUN-04: Development environment reliability

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Lifecycle hooks (`post-create`, `pre-remove`) let users install dependencies, copy .env files and stop services per worktree; VibeTree detects dev-server URLs for a preview pane. No dependency caching, port allocation or snapshots.

### RUN-05: Limits and failure handling

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No time, turn, token or spend limits; hooks time out after 120 seconds; idle sessions on the standalone server are reaped after 24h.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Live agent state (idle, working, needs input, done) derived from terminal traffic, per-worktree git status counts, and bounded scrollback; no logs, traces, usage statistics or failure reasons.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No model cost, token or compute tracking.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No compute-aware scheduling; sessions run as host processes with no CPU/RAM limits or queues.

## Human collaboration and control

### TEAM-01: Live human collaboration

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Single-operator tool: one shared password or per-device pairing; several clients can attach to the same terminal session, but there are no identities, comments, presence or attribution.

### TEAM-02: Roles and access boundaries

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No roles, SSO or membership; access is a single password, a loopback token (desktop) or revocable paired devices.

### TEAM-03: Approvals and temporary access

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No product approvals: permission prompts are the agent CLI's and appear in the terminal; VibeTree detects them for notifications. Default standalone mode is unauthenticated unless configured.

### TEAM-04: Decision and activity history

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No activity or decision history beyond terminal scrollback and Git history.

### TEAM-05: Review experience and 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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. A changes dock shows staged and unstaged diffs per worktree with maximize mode; a selected file can be sent as a note to the agent; keyboard shortcuts exist; phone web layout; no review queue or approvals.

### TEAM-06: Colleague takeover and continuity

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The same server session can be reattached from another device with the same credential, giving full takeover of terminal and worktree state; there is no identity transfer or handoff record.

## Verification and delivery

### SHIP-01: Retained artifacts and outputs

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Retained outputs are the Git worktree files, staged/unstaged diffs on demand and bounded terminal scrollback; a browser preview pane shows running dev servers while they run. No gallery, screenshots, recordings or reviewer outputs.

### SHIP-02: Verification and spec gates

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. No product-run verification: users run tests inside terminals; hooks can run scripts on create/remove only.

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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Product-managed Git: create/remove worktrees with new branches, list worktrees, status, staged and unstaged diffs; branch deleted on removal. Committing, pushing and PRs happen in the agent terminal; no rebase or conflict workflow.

### SHIP-04: Merge and deployment authority

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No approval, merge, release or deploy authority in the product.

### SHIP-05: Completion evidence and rollback

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No completion evidence or rollback features; deleting a worktree and its branch discards an experiment.

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

- **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.
- **vibe-tree**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. No batch review or shipping queue; reviewers open each worktree's changes dock in turn.

## Ownership, privacy and economics

### OWN-01: Source and license

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. MIT license for the monorepo (desktop app, server, web, CLI, core packages) at v0.2.0; no closed or hosted components.

### OWN-02: Hosting and exit

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Fully self-hosted: desktop app or standalone server/Docker on user hardware, no vendor account or service, data lives in Git worktrees on the host. No export/import features; history is Git.

### OWN-03: Data handling and telemetry

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The site states no cloud component and no telemetry; bounded search found no telemetry, analytics or updater code. Code and terminal data stay on the user's machine or their own server; agent providers receive code per their policies. A privacy-documentation issue is open.

### OWN-04: Price and included usage

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Free and open source (MIT) with no paid plan or hosted service; agent subscriptions are bought separately.

### OWN-05: Scenario cost and controls

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Scenario cost is $0 for VibeTree for one, two or five developers; agent subscriptions, model costs and optional VM hosting are separate and unmodeled here.

### OWN-06: Availability and support

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Single-maintainer open-source project at v0.2.0 (2026-07-24); support via GitHub issues; no response commitments; latest commit 2026-07-25 and several unresolved issues including a Windows launch failure.

### OWN-07: Enterprise assurance

- **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.
- **vibe-tree**: 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

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Everything is free: MIT open source, free download, no trial or card; two-person collaboration, issue management and managed remote compute do not exist, but a BYO-host Docker deployment and BYO agent subscriptions work for free.

### OWN-09: Pricing transparency

- **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.
- **vibe-tree**: Agent cross-checked (agent-cross-checked); support: supported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Fully transparent: free, no paid plans, no markups; third-party agent costs are separate.
