Podium
Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.
Product websitepodium.do Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- Yes
- Phone
- Phone browser
- Command line
- Yes
- Agents
- Claude Code, Codex, Cursor Agent, OpenCode, Pi and Grok
- Your subscription
- Works with your own plan
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- Worktree
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- Yes
- Built-in issues
- Yes
- Pull requests
- Yes
- Review screen
- Yes
- Team
- Roles
- Self-hosting
- Yes
- Licence
- Apache-2.0
- Price from
- Free
- How it charges
- No paid plan and bring your own key
- Paid plans from
- Not listed
Receipts
- Checked
- Findings
- 48 published · 37 cross-checked by a second agent · read them all
- Sources
- 152 public pages on 3 sites: github.com, podium.do, api.github.com
- Screenshot
- podium.do, retrieved · first party marketing · shows appearance, not capability
- Data
- /products/podium.json · .md
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
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.
Source and scope for Where you use itAgents it runs
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.
Source and scope for Agents it runsAccounts and subscriptions
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.
Source and scope for Accounts and subscriptionsWhere agents run
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.
Source and scope for Where agents runHow work is kept apart
Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
Source and scope for How work is kept apartParallel work
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.
Source and scope for Parallel workScheduled runs
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.
Source and scope for Scheduled runsGit and pull requests
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.
Source and scope for Git and pull requestsLicence and source
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.
Source and scope for Licence and sourcePrice
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.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes |
| Desktop OS: Windows | Yes |
| Desktop OS: Linux | Yes |
| Web client | Yes |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | Yes |
| CLI | Yes |
| Coding agents: Claude Code | Yes cross-checked |
| Coding agents: Codex | Yes cross-checked |
| Coding agents: Cursor Agent | Yes cross-checked |
| Coding agents: Gemini CLI | No |
| Coding agents: OpenCode | Yes cross-checked |
| Coding agents: Pi | Yes cross-checked |
| Coding agents: Grok | Yes cross-checked |
| Coding agents: Aider | No |
| Coding agents: Antigravity | No |
| Use my subscription | Yes cross-checked |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | No |
| Workspace isolation: Git worktree | Yes |
| Workspace isolation: Container | No |
| Workspace isolation: VM or microVM | No |
| Parallel runs | Yes cross-checked |
| Coordinator | Yes cross-checked |
| Native issue tracking | Yes cross-checked |
| Unattended triggers | Yes |
| Shared prompting | Unknown |
| Team roles | Yes |
| SSO | No |
| Pull request workflow | Yes cross-checked |
| Review interface | Yes |
| Product license: Apache-2.0 | Yes. Apache-2.0 cross-checked |
| Product license: MIT | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: Elastic License 2.0 | No. Apache-2.0 cross-checked |
| Product license: Custom terms | No. Apache-2.0 cross-checked |
| Product license: Proprietary | No. Apache-2.0 cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Yes cross-checked |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | Yes cross-checked |
| Pricing model: Free plan | No |
| Pricing model: Subscription | No |
| Pricing model: Per seat | No |
| Pricing model: Usage-based | No |
| Pricing model: Per machine or compute | No |
| Pricing model: Bring your own key | Yes cross-checked |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes |
| Open-source license | Yes. Apache-2.0 cross-checked |
| Any desktop app | Yes |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | Yes |
Filter receipts
Desktop OS: macOS: Yes
Desktop OS: macOS
Typed value: Yes.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Podium packages/pty/vendor/podium-host/src/windows.rs
Finding: The tag includes a Windows ConPTY host and authenticated named-pipe transport. Implementation only; release status comes from the v0.3.0 assets.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium .github/workflows/desktop-release.yml
Finding: The desktop release workflow includes a windows-x86_64 target, matching the x64-setup.exe asset in v0.3.0.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
Desktop OS: Windows: Yes
Desktop OS: Windows
Typed value: Yes.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Podium packages/pty/vendor/podium-host/src/windows.rs
Finding: The tag includes a Windows ConPTY host and authenticated named-pipe transport. Implementation only; release status comes from the v0.3.0 assets.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium .github/workflows/desktop-release.yml
Finding: The desktop release workflow includes a windows-x86_64 target, matching the x64-setup.exe asset in v0.3.0.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
Desktop OS: Linux: Yes
Desktop OS: Linux
Typed value: Yes.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Podium packages/pty/vendor/podium-host/src/windows.rs
Finding: The tag includes a Windows ConPTY host and authenticated named-pipe transport. Implementation only; release status comes from the v0.3.0 assets.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium .github/workflows/desktop-release.yml
Finding: The desktop release workflow includes a windows-x86_64 target, matching the x64-setup.exe asset in v0.3.0.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
Web client: Yes
Web client
Typed value: Yes.
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.
- Browser: Browser web client served by the Podium server (local or VPS).
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Cli: podium CLI is part of every install with documented command groups.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
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.
- Mobile apps: The native iPhone client is in private beta and is not public; the complete phone-client list contains no native Android app.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Podium: Three ways to use Podium; Every app connects to every Podium
Finding: The complete published execution choices are the user computer and the user VPS. Phone and browser clients connect to either one; the download page offers no Podium-operated execution host. Its phone choices are a phone browser and a native iPhone private beta, with no native Android client.
Phone access: Phone browser: Yes
Phone access: Phone browser
Typed value: Yes.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Browser: Browser web client served by the Podium server (local or VPS).
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Notifications: Web, ntfy and Telegram notifications exist but are an edge-visibility Notifications feature that defaults off; the docs list notifications among non-baseline features.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
CLI: Yes
CLI
Typed value: Yes.
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.
- Browser: Browser web client served by the Podium server (local or VPS).
- Cli: podium CLI is part of every install with documented command groups.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
Coding agents: Claude Code: Yes cross-checked
Coding agents: Claude Code
Typed value: Yes.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Model providers: Models come from each harness own catalog; agent spawn checks --model and --effort against a live model catalog. Managed provider keys exist for Anthropic and OpenAI (coding) and OpenRouter (background assistant role only).
- Session integration: Podium launches each real harness CLI in a pseudo-terminal and keeps the process available for reconnection; a driver contract with headless drivers is available behind the runtime-drivers flag, which defaults off.
- Mixed harness operation: Spawn takes a --harness per child, and profiles can list candidates across harnesses. CLI help lists claude-code, codex, grok, opencode and cursor, not pi. Docs say handoff and model behavior differ by harness. No mixed-harness task was run.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
Coding agents: Codex: Yes cross-checked
Coding agents: Codex
Typed value: Yes.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Model providers: Models come from each harness own catalog; agent spawn checks --model and --effort against a live model catalog. Managed provider keys exist for Anthropic and OpenAI (coding) and OpenRouter (background assistant role only).
- Session integration: Podium launches each real harness CLI in a pseudo-terminal and keeps the process available for reconnection; a driver contract with headless drivers is available behind the runtime-drivers flag, which defaults off.
- Mixed harness operation: Spawn takes a --harness per child, and profiles can list candidates across harnesses. CLI help lists claude-code, codex, grok, opencode and cursor, not pi. Docs say handoff and model behavior differ by harness. No mixed-harness task was run.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
Coding agents: Cursor Agent: Yes cross-checked
Coding agents: Cursor Agent
Typed value: Yes.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Model providers: Models come from each harness own catalog; agent spawn checks --model and --effort against a live model catalog. Managed provider keys exist for Anthropic and OpenAI (coding) and OpenRouter (background assistant role only).
- Session integration: Podium launches each real harness CLI in a pseudo-terminal and keeps the process available for reconnection; a driver contract with headless drivers is available behind the runtime-drivers flag, which defaults off.
- Mixed harness operation: Spawn takes a --harness per child, and profiles can list candidates across harnesses. CLI help lists claude-code, codex, grok, opencode and cursor, not pi. Docs say handoff and model behavior differ by harness. No mixed-harness task was run.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
Coding agents: Gemini CLI: No
Coding agents: Gemini CLI
Typed value: No.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
Coding agents: OpenCode: Yes cross-checked
Coding agents: OpenCode
Typed value: Yes.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Model providers: Models come from each harness own catalog; agent spawn checks --model and --effort against a live model catalog. Managed provider keys exist for Anthropic and OpenAI (coding) and OpenRouter (background assistant role only).
- Session integration: Podium launches each real harness CLI in a pseudo-terminal and keeps the process available for reconnection; a driver contract with headless drivers is available behind the runtime-drivers flag, which defaults off.
- Mixed harness operation: Spawn takes a --harness per child, and profiles can list candidates across harnesses. CLI help lists claude-code, codex, grok, opencode and cursor, not pi. Docs say handoff and model behavior differ by harness. No mixed-harness task was run.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
Coding agents: Pi: Yes cross-checked
Coding agents: Pi
Typed value: Yes.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Model providers: Models come from each harness own catalog; agent spawn checks --model and --effort against a live model catalog. Managed provider keys exist for Anthropic and OpenAI (coding) and OpenRouter (background assistant role only).
- Session integration: Podium launches each real harness CLI in a pseudo-terminal and keeps the process available for reconnection; a driver contract with headless drivers is available behind the runtime-drivers flag, which defaults off.
- Mixed harness operation: Spawn takes a --harness per child, and profiles can list candidates across harnesses. CLI help lists claude-code, codex, grok, opencode and cursor, not pi. Docs say handoff and model behavior differ by harness. No mixed-harness task was run.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
Coding agents: Grok: Yes cross-checked
Coding agents: Grok
Typed value: Yes.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Model providers: Models come from each harness own catalog; agent spawn checks --model and --effort against a live model catalog. Managed provider keys exist for Anthropic and OpenAI (coding) and OpenRouter (background assistant role only).
- Session integration: Podium launches each real harness CLI in a pseudo-terminal and keeps the process available for reconnection; a driver contract with headless drivers is available behind the runtime-drivers flag, which defaults off.
- Mixed harness operation: Spawn takes a --harness per child, and profiles can list candidates across harnesses. CLI help lists claude-code, codex, grok, opencode and cursor, not pi. Docs say handoff and model behavior differ by harness. No mixed-harness task was run.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
Coding agents: Aider: No
Coding agents: Aider
Typed value: No.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
Coding agents: Antigravity: No
Coding agents: Antigravity
Typed value: No.
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.
- Harnesses: Claude Code, Codex, Grok, OpenCode, Cursor and Pi (docs, harness enum, site). The README lists the first five. Release 0.2.0 says Pi is fully supported.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
Use my subscription: Yes cross-checked
Use my subscription
Typed value: Yes.
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.
- Agent subscriptions: Native Claude subscription and local ChatGPT/Codex login use provider plan capacity. Managed Claude setup-token is also offered.
- Api accounts: Managed Anthropic API keys drive Claude Code and OpenAI API keys drive Codex.
- Account switching: Users choose native or supported managed accounts. Rotating several subscription logins across agents is explicitly Coming soon.
- Provider restrictions: Managed credentials have explicit harness pairings; OpenRouter is not offered as a managed coding account because the shipped coding CLIs do not consume that key.
- Do not generalize subscription compatibility to every plan or harness. Provider limits and terms still apply. No reseller or pricing claim is inferred. Settings code was read, not exercised.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Podium apps/web/src/features/settings/sections/accounts.tsx
Finding: Accounts settings show native logins and managed accounts. Rotating several subscription logins remains labelled Coming soon.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
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.
- Local: The macOS desktop app runs server, daemon and web UI locally. Experimental Linux and Windows desktop builds offer the same local choice.
- Byo remote: User-owned Linux host via the headless installer or machine pairing.
- Self hosted: Headless install on Linux x86_64 and ARM64.
- Provisioning: Installer, setup UI and single-use pairing command.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: payer, resources, region, expiry.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
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.
- Local: The macOS desktop app runs server, daemon and web UI locally. Experimental Linux and Windows desktop builds offer the same local choice.
- Byo remote: User-owned Linux host via the headless installer or machine pairing.
- Self hosted: Headless install on Linux x86_64 and ARM64.
- Hybrid: One server with several paired daemons; work is placed on a chosen machine.
- Provisioning: Installer, setup UI and single-use pairing command.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: payer, resources, region, expiry.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
Where agents run: In the vendor's cloud: No
Where agents run: In the vendor's cloud
Typed value: No.
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.
- Managed cloud: The complete published host choices are the user computer and user VPS, both operated by the user.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: payer, resources, region, expiry.
-
Podium: Three ways to use Podium; Every app connects to every Podium
Finding: The complete published execution choices are the user computer and the user VPS. Phone and browser clients connect to either one; the download page offers no Podium-operated execution host. Its phone choices are a phone browser and a native iPhone private beta, with no native Android client.
Workspace isolation: Git worktree: Yes
Workspace isolation: Git worktree
Typed value: Yes.
Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
- Branch: An issue can own a Git branch.
- Worktree: Issue-backed work uses a linked worktree; Podium can recreate a hibernated session worktree from its branch.
- Filesystem: Worktrees separate issue files; an agent can still reach whatever its host account can read. Same-machine workspace fetch returns the live writable path.
- Code separation: Worktrees isolate concurrent changes; Podium will not resolve branch conflicts or decide when overlapping changes are safe to merge. No two-change test run.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: network.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
Workspace isolation: Container: No
Workspace isolation: Container
Typed value: No.
Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
- Container: The daemon and PTY backends provision no containers.
- Vm: The daemon and PTY backends provision no virtual machines.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: network.
-
Podium: packages/pty/src/backends/index.ts
Finding: The released terminal backend launches native harness processes through the host PTY. Inspection of the daemon launch paths and packages/pty for Docker, Podman, container, microVM, QEMU and Firecracker provisioning found no product-managed container or VM isolation. Git worktree separation and provider/host permissions are separate.
Workspace isolation: VM or microVM: No
Workspace isolation: VM or microVM
Typed value: No.
Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
- Container: The daemon and PTY backends provision no containers.
- Vm: The daemon and PTY backends provision no virtual machines.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: network.
-
Podium: packages/pty/src/backends/index.ts
Finding: The released terminal backend launches native harness processes through the host PTY. Inspection of the daemon launch paths and packages/pty for Docker, Podman, container, microVM, QEMU and Firecracker provisioning found no product-managed container or VM isolation. Git worktree separation and provider/host permissions are separate.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
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.
- Concurrent sessions: Each session is its own harness process in a pseudo-terminal; one issue can retain several sessions.
- Documentation read; no concurrency run. Agents sharing one workspace need explicit file ownership per the docs.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
Coordinator: Yes cross-checked
Coordinator
Typed value: Yes.
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.
- Roles: The caller becomes the parent of the spawned child session; no product-enforced reviewer or implementer role was established.
- Model harness effort: spawn takes --harness, --model, --effort and --profile; profile candidates supply a setup when flags do not.
- Messages: podium mail send addresses issues or sessions with optional expected response and interrupt urgency.
- Results return: await returns the child ack or settle result or a still-working status snapshot; durable mail carries findings.
- Cross harness: Cross-harness spawning is documented in the README and CLI help.
- Orchestration owner: Podium product commands and its task system orchestrate; children are separate Podium sessions rather than provider-native subagents.
- Activation: podium agent is in the stable command reference; some orchestration features (workflows) are edge-flagged and default off.
- Authentication: Each harness uses its own native authentication (docs); the authorization model gives agents a constrained capability.
- Live progress: A child is a full session shown with a seat on the deck, and agent status reads its state.
- Retained results: Child sessions keep their record and transcript after stopping and issue mail is durable; retrieval of a finished reviewer findings was not tested.
- Followup: session send --wake and mail send can message or resume a child after it parks.
- Invocation: podium agent spawn with --issue or --new and a prompt.
- Documentation and source read; no delegated task, child result or follow-up was executed. Harness support differs.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
-
Podium packages/model/src/authz/issue-authz.ts
Finding: Issue authorization policy defines viewer, worker and admin roles mapped to read, write and manage actions with closed scope kinds (all, none, subtree, owned, self). Source comment at lines 58-62 says the current scope is all and subtree is the reserved per-issue extension. The operator is unconstrained and agents carry a constrained capability. Commands carry actor and on-behalf-of fields.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium packages/issue-client/src/deck.ts
Finding: podium issue deck prints the same snapshot: counts by state, phases, tasks, session seats with harness, model and effort, unmet blockers and proposals.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
-
Podium apps/server/src/modules/issues/service/seat.ts
Finding: A session seat decides whether it may talk to the user or must ask a coordinator. Below-coordinator sessions are pointed at issue mail.
-
Podium apps/server/src/modules/messages/handlers/spawn-agent.ts
Finding: Agent-initiated spawns take a budget of 10 per target issue per UTC day, shared with mail-triggered spawns. Human-principal spawns are exempt.
Native issue tracking: Yes cross-checked
Native issue tracking
Typed value: Yes.
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.
- Create: create command.
- Edit: update command.
- Discuss: issue comment records checkpoints and issue mail carries messages; a threaded human discussion UI was not established.
- Prioritize: Priority metadata.
- Label: label command.
- Assign: Assignee update and claim.
- Search: search command (text, status, priority, type, label).
- Filter: The issue board has a filter control and CLI search filters by text, status, priority, type and label; issue list takes only a repository path. Not used hands-on.
- Archive: archive command.
- Reopen: No dedicated reopen command exists. Updating a closed issue to an open stage reopens it and emits issue.reopened (source; not run).
- Project epic views: tree and children commands, a board, and the flight deck showing phases, tasks, seats, blockers and proposals for a mission. Usability untested.
- Idea parking: Operator issues start in backlog and agent proposals in proposed, shown on the deck; creation does not require starting an agent.
- Explicit dispatch: Separate start command and optional start flag.
- Task session separation: Docs state an issue is a durable record separate from sessions and may retain several sessions.
- Metadata: Title, description, brief, acceptance, priority, labels, assignee, stage, type, parent, dependencies and agent profile. Task colors were dropped in 0.3.0.
- Durable states: Stages proposed, backlog, planning, in_progress, review, shipping, done with close reasons.
- External tracker requirement: No external tracker is required: Podium issue records are native and authoritative.
- Source inspection establishes implementation at v0.3.0; hands-on behavior remains unverified.
- The working-session close guard is an overridable source-level check, not proof that human approval is required for every close.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/model/src/entities/issue.ts
Finding: Issue records are distinct replicated entities with durable fields and projections; this is a domain model rather than terminal tab metadata.
-
Podium apps/server/src/modules/issues/registry.ts
Finding: Issue registry retains create, share, reparent and ship operations. Agent top-level create produces Proposed work. attachSession checks only input.targetId, so it does not guard the implicit current-issue anchor. The close and update-done guard refuses constrained callers while an issue session is computing unless confirmInterrupt is true; operator scope all bypasses it.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Podium apps/server/src/modules/issues/service/crud.ts
Finding: CRUD create defaults stage to backlog and audience to human. claim is an update of assignee and stage with no exclusivity check of its own. Moving a closed issue back to an open stage emits issue.reopened.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium apps/web/src/features/issues/IssuesFilters.tsx
Finding: The issue board has a filter control alongside CLI search by text, status, priority, type and label.
Unattended triggers: Yes
Unattended triggers
Typed value: Yes.
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.
- Schedules: Automations support cron and one-time schedules and are fired by the server-hosted janitor. The Automations UI is feature flagged and off by default.
- Source inspected only; no automation was created or fired. The feature is experimental, edge-listed and default off.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium automations/scheduler.ts
Finding: Server-owned scheduler ticks every 30 seconds after a 20 second boot delay, single-flight, inert until an enabled automation exists; schedule kinds are cron and once (model automation.ts line 48).
Team roles: Yes
Team roles
Typed value: Yes.
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.
- Organization roles: Instance members are member or admin; member routes require admin. Hosted organization roles are not confirmed in production.
- Membership: Settings Members offers invite links, optional email and member removal. Docs say hosted code includes accounts, organizations, invitations and device sessions, with production availability unconfirmed.
- Unauthorized access: Member routes answer 403 unless the actor is admin (source). A wider access test was not run.
- Revocation: An admin can remove a member through the member routes. The effect on live sessions was not established.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Podium apps/server/src/member-routes.ts
Finding: Member routes list members, create invites and change or remove membership, and answer 403 unless the actor has the admin role.
-
Podium apps/web/src/features/settings/sections/members.tsx
Finding: Settings has a Members section with invite links, optional invitation email, member or admin role and member removal. Which installs reach it and how it behaves were not tested.
SSO: No
SSO
Typed value: No.
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.
- Sso: Bounded inspection of the released server authentication and member routes found no SAML/OIDC enterprise SSO path.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.
-
Podium: apps/server/src/auth-route.ts
Finding: The released client authentication routes use password-backed member sessions, cookies and paired mobile bearer tokens. Bounded inspection of the server authentication and membership code for SAML/OIDC/SSO found no enterprise single sign-on path. Coding-agent provider OAuth logins are separate.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
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.
- Worktrees: Linked worktree per issue; the worktree GC setting defaults to propose cleanup after 14 days.
- Pull requests: issue action pr runs gh pr create --base <parent> --head <branch> --fill and records the printed URL on the issue; mergeStyle can be pr; requires the GitHub CLI.
- Rebase: issue action rebase, and autoRebaseBeforeMerge defaults on.
- Product state: Issue stage, branch, parent branch and git action results are product state.
- Docs and source read; no draft PR fixture completed.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/model/src/settings/preferences.ts
Finding: Settings defaults: auto-continue off; worktree GC mode propose after 14 days; git workflow mergeStyle ff-only, pr or ask (default ff-only) and autoRebaseBeforeMerge default true.
-
Podium apps/daemon/src/repo-op.ts
Finding: Daemon repo operations include a guarded gh pr create --base <parent> --head <branch> --fill, used by the issue action pr.
-
Podium apps/server/src/modules/issues/service/workflow.ts
Finding: issue action pr records the URL printed by gh on the issue as prUrl.
Review interface: Yes
Review interface
Typed value: Yes.
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.
- Pending reviews: Issues in review stage and offers appear in the Tray; the board shows stages.
- Change understanding: Reviewers inspect changed files and Git diff; a Git panel is an edge flag.
- Evidence navigation: Issue artifacts render in the issue sidebar and offer cards show up to three artifacts.
- Request changes: Offers carry a send-back action with typed feedback that revises the issue. Text from a reply or review finding can be quoted into the next message.
- Shipping guidance: Offers recommend merge actions; the merge uses merge-lock.
- Docs read; no review fixture timed.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
Product license: Apache-2.0: Yes. Apache-2.0 cross-checked
Product license: Apache-2.0
Typed value: Yes. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: MIT: No. Apache-2.0 cross-checked
Product license: MIT
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: GPL-3.0: No. Apache-2.0 cross-checked
Product license: GPL-3.0
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: GPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: GPL-3.0-or-later
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: AGPL-3.0: No. Apache-2.0 cross-checked
Product license: AGPL-3.0
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: AGPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: Elastic License 2.0: No. Apache-2.0 cross-checked
Product license: Elastic License 2.0
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: Custom terms: No. Apache-2.0 cross-checked
Product license: Custom terms
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Product license: Proprietary: No. Apache-2.0 cross-checked
Product license: Proprietary
Typed value: No. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
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.
- Self hosting: Self-hosted headless server and local desktop are documented.
- Vendor dependencies: Agents require each harness provider account; releases and updates come from GitHub with stable entrypoints on podium.do; usage telemetry is on by default and goes to a Podium relay unless turned off; Podium Connect can publish a public-URL server location to connect.podium.do. It is on by default once a public URL exists and one switch turns it off.
- Account independence: The documented install path needs no hosted Podium account; the optional password sign-in is local to the instance. Hosted accounts exist in code, and their production availability is unconfirmed.
- Docs read; no export, import or cancellation test.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
Telemetry opt-out: Yes cross-checked
Telemetry opt-out
Typed value: Yes.
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.
- Prompts: Transcripts are mirrored into the state directory on the server and are never sent by telemetry.
- Logs: Logs are kept in the state directory; podium logs export-crash writes recent crash events to a file for support.
- Subprocessors: Telemetry vendor PostHog Cloud behind a Podium-operated relay is named; hosted analytics use PostHog; the marketing site uses Google Analytics 4.
- Telemetry disclosure: A telemetry contract lists every field, destination and vendor. Usage reports hold counts and buckets. Crash reports hold an error type and up to 20 Podium source file, line and function frames.
- Telemetry defaults: Usage reports are on by default, sent about a minute after first start and then once a day. Crash reports are off unless turned on. Public docs, source and the telemetry document agree. The relay drops IP addresses.
- Telemetry controls: podium telemetry on/off/show/reset-id, Settings Privacy, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off.
- Consent prompt: The telemetry document at v0.3.0 and the install docs say setup does not ask; it is a setting.
- Docs and source read; no network capture. Public privacy, install, configuration and availability docs, revised on 2026-11-06, now agree with docs/TELEMETRY.md and consent.ts at v0.3.0. The 0.2.0 and 0.3.0 release notes do not mention this change. Podium Connect is on by default for servers with a public URL: it registers an installation id and public key and publishes that URL to connect.podium.do. It has its own switch, PODIUM_CONNECT, and is documented outside the telemetry contract. Podium does not state training use or residency.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
Free access: Yes cross-checked
Free access
Typed value: Yes.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
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.
- Ongoing free: The software is Apache-2.0 and the site marks it free to access; no paid tier is listed.
- Early access: The native iPhone app is in private beta; hosted Podium access is unconfirmed in public sources.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
Pricing model: Free, no paid plan: Yes cross-checked
Pricing model: Free, no paid plan
Typed value: Yes.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Pricing route returned 404 on 2026-11-06. No price table was found on the checked official pages. This is a bounded search result, not a claim that pricing cannot exist elsewhere.
Pricing model: Free plan: No
Pricing model: Free plan
Typed value: No.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
Pricing model: Subscription: No
Pricing model: Subscription
Typed value: No.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
Pricing model: Per seat: No
Pricing model: Per seat
Typed value: No.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
Pricing model: Usage-based: No
Pricing model: Usage-based
Typed value: No.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
Pricing model: Per machine or compute: No
Pricing model: Per machine or compute
Typed value: No.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
Pricing model: Bring your own key: Yes cross-checked
Pricing model: Bring your own key
Typed value: Yes.
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.
- Agent subscriptions: Native Claude subscription and local ChatGPT/Codex login use provider plan capacity. Managed Claude setup-token is also offered.
- Api accounts: Managed Anthropic API keys drive Claude Code and OpenAI API keys drive Codex.
- Account switching: Users choose native or supported managed accounts. Rotating several subscription logins across agents is explicitly Coming soon.
- Provider restrictions: Managed credentials have explicit harness pairings; OpenRouter is not offered as a managed coding account because the shipped coding CLIs do not consume that key.
- Do not generalize subscription compatibility to every plan or harness. Provider limits and terms still apply. No reseller or pricing claim is inferred. Settings code was read, not exercised.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
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.
- Model cost: Agents run on the user's own provider subscriptions or API keys; the docs list billing and hosted metering as not implemented.
- Compute cost: Agents run on user-controlled machines; no Podium compute is offered in the documented path.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
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.
- Local: The macOS desktop app runs server, daemon and web UI locally. Experimental Linux and Windows desktop builds offer the same local choice.
- Byo remote: User-owned Linux host via the headless installer or machine pairing.
- Self hosted: Headless install on Linux x86_64 and ARM64.
- Hybrid: One server with several paired daemons; work is placed on a chosen machine.
- Provisioning: Installer, setup UI and single-use pairing command.
- Client disconnect: Docs say disconnecting a client does not end the session; the daemon keeps the process for reconnection. Not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: payer, resources, region, expiry.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
Open-source license: Yes. Apache-2.0 cross-checked
Open-source license
Typed value: Yes. Apache-2.0.
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.
- Client license: Apache License 2.0 for repository source.
- Server license: Apache License 2.0 for repository source.
- Source visibility: Public GitHub repository.
- Source revision: Public tag v0.3.0 resolves to commit ec6ff505f69aeb358eb744596e70e984996c2e42. Files cited here matched unauthenticated raw GitHub fetches and the local read-only clone.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
Any desktop app: Yes
Any desktop app
Typed value: Yes.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Podium packages/pty/vendor/podium-host/src/windows.rs
Finding: The tag includes a Windows ConPTY host and authenticated named-pipe transport. Implementation only; release status comes from the v0.3.0 assets.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium .github/workflows/desktop-release.yml
Finding: The desktop release workflow includes a windows-x86_64 target, matching the x64-setup.exe asset in v0.3.0.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
Any phone client: Yes
Any phone client
Typed value: Yes.
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.
- Desktop os: macOS 11 or later (Apple silicon and Intel) is the stable packaged desktop. Linux x86_64 AppImage and Windows x64 installer are published with v0.3.0 and labelled Experimental. The README Windows wording is superseded; docs add that a release can publish without the Windows build.
- Browser: Browser web client served by the Podium server (local or VPS).
- Mobile browser: The download page presents a phone browser path on iPhone or Android with Add to Home Screen, reached over Tailscale or an HTTPS address and paired with a QR code. Docs separately call the /mobile web build an unsupported compatibility path.
- Notifications: Web, ntfy and Telegram notifications exist but are an edge-visibility Notifications feature that defaults off; the docs list notifications among non-baseline features.
- Cross device continuity: Docs say disconnecting a client does not end the session and clients reattach to the same server state and terminal. The site says every Podium app connects to every Podium server. Moving one task between desktop and phone was not tested.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
podium:ACC-01: 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.
podium:ACC-01
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.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: editor_extensions.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium apps/mobile/package.json
Finding: Mobile source uses Expo and React Native. Source presence does not establish app-store availability.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Finding: Documented first-task loop: podium status, issue create, issue start --agent (creates branch and worktree), follow with issue show and session status, review evidence, close or merge. Requires a configured instance, a registered Git repository and one installed, authenticated harness.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Finding: Notification service pushes attention notices through web clients, ntfy topics and Telegram chats; gated by the notifications feature flag (edge visibility, default off).
-
Podium packages/pty/vendor/podium-host/src/windows.rs
Finding: The tag includes a Windows ConPTY host and authenticated named-pipe transport. Implementation only; release status comes from the v0.3.0 assets.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium .github/workflows/desktop-release.yml
Finding: The desktop release workflow includes a windows-x86_64 target, matching the x64-setup.exe asset in v0.3.0.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
-
Podium docs: feature availability
Finding: Live page lists usage reports on by default and crash reports opt-in, says each release also builds an experimental Windows x64 installer, and still says reviewed sources do not confirm native iPhone distribution.
-
Podium: Three ways to use Podium; Every app connects to every Podium
Finding: The complete published execution choices are the user computer and the user VPS. Phone and browser clients connect to either one; the download page offers no Podium-operated execution host. Its phone choices are a phone browser and a native iPhone private beta, with no native Android client.
podium:ACC-02: 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. cross-checked
podium:ACC-02
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.
- Support is read from docs and source; no harness session was started. Custom adapters were not found. Capabilities differ per harness (handoff, usage, subagent visibility). Pi support is the vendor release wording; its adapter declares narrower capabilities.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium packages/model/src/entities/agent.ts
Finding: Harness agent kinds: claude-code, codex, grok, opencode, cursor, pi.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
podium:ACC-03: 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. cross-checked
podium:ACC-03
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.
- Do not generalize subscription compatibility to every plan or harness. Provider limits and terms still apply. No reseller or pricing claim is inferred. Settings code was read, not exercised.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Podium apps/web/src/features/settings/sections/accounts.tsx
Finding: Accounts settings show native logins and managed accounts. Rotating several subscription logins remains labelled Coming soon.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
podium:ACC-04: 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.
podium:ACC-04
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.
- Documentation read only; no install was timed or run.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Finding: Documented first-task loop: podium status, issue create, issue start --agent (creates branch and worktree), follow with issue show and session status, review evidence, close or merge. Requires a configured instance, a registered Git repository and one installed, authenticated harness.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
-
Finding: Layered troubleshooting; an issue cannot start if blocked by an open dependency, machine offline, repository absent, harness not logged in, or worktree conflict; crash export command.
-
Podium apps/daemon/src/repo-op.ts
Finding: Daemon repo operations include a guarded gh pr create --base <parent> --head <branch> --fill, used by the issue action pr.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
-
Podium apps/daemon/src/repo-op.ts
Finding: The daemon clone operation runs git clone -- <originUrl> <path>. In this file only prCreate uses gh.
-
Podium public guide: reference/feature-availability
Finding: Hosted production cutover is unconfirmed; hosted workspace requests create pending records requiring manual provisioning. Billing, hosted metering and durable cloud lifecycle are not implemented product claims. Experimental workflows/specs/automations/shipping are not baseline.
podium:ACC-05: 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. cross-checked
podium:ACC-05
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.
- Source inspection of the MCP endpoint and CLI registry at v0.3.0; nothing was executed.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
-
Podium apps/server/src/mcp-route.ts
Finding: Server exposes a minimal stateless tools-only MCP endpoint over HTTP JSON-RPC (initialize, tools/list, tools/call), bearer-token gated, intended for loopback use by harness agents.
-
Podium apps/server/src/issue-mcp.ts
Finding: Issue MCP tools are generated from the shared ISSUE_COMMANDS registry as issue_<command> tools, so CLI and MCP operate on the same issue commands.
podium:ACC-06: 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. cross-checked
podium:ACC-06
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.
- Only the Podium tool surface and profile import/export are established. Nothing was executed.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium apps/server/src/mcp-route.ts
Finding: Server exposes a minimal stateless tools-only MCP endpoint over HTTP JSON-RPC (initialize, tools/list, tools/call), bearer-token gated, intended for loopback use by harness agents.
-
Podium apps/server/src/issue-mcp.ts
Finding: Issue MCP tools are generated from the shared ISSUE_COMMANDS registry as issue_<command> tools, so CLI and MCP operate on the same issue commands.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
-
Podium v0.3.0: apps/server/src/mcp-route.ts
Finding: The accessible /mcp server accepts tools-only JSON-RPC POST behind a bearer/x-podium-mcp-token, with opaque per-thread identity and fail-closed start-capable tool calls. This is an MCP server, not proof of an external MCP client registry.
podium:ACC-07: 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. cross-checked
podium:ACC-07
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.
- Source inspection establishes implementation at v0.3.0; measured responsiveness is not covered. The mobile implementation is not a public app-store release.
-
Podium apps/desktop/src-tauri/Cargo.toml
Finding: Desktop source uses Tauri 2 and platform plugins. Tauri does not make all UI controls platform-native.
-
Podium apps/mobile/package.json
Finding: Mobile source uses Expo and React Native. Source presence does not establish app-store availability.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
podium:PLAN-01: 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. cross-checked
podium:PLAN-01
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.
- Source inspection establishes implementation at v0.3.0; hands-on behavior remains unverified.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/model/src/entities/issue.ts
Finding: Issue records are distinct replicated entities with durable fields and projections; this is a domain model rather than terminal tab metadata.
-
Podium apps/server/src/modules/issues/service/hierarchy.ts
Finding: addDep accepts only blocked-by, related, discovered-from, supersedes and duplicates, refuses any other type, refuses self-dependencies and cycles, and refuses a blocked-by edge on a phase. Reparent keeps the issue row.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Finding: When a Linear API key is configured the in-product superagent gets linear_search, linear_create and linear_move tools that call the Linear GraphQL API; these are assistant tool calls, not a sync of Podium issues.
podium:PLAN-02: 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. cross-checked
podium:PLAN-02
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.
- No executed restart or revision-history scenario. Do not claim automatic plan maintenance or formal plan approval.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium apps/server/src/modules/issues/registry.ts
Finding: Issue registry retains create, share, reparent and ship operations. Agent top-level create produces Proposed work. attachSession checks only input.targetId, so it does not guard the implicit current-issue anchor. The close and update-done guard refuses constrained callers while an issue session is computing unless confirmInterrupt is true; operator scope all bypasses it.
-
Podium apps/web/src/features/issues/issue-page/IssueBody.tsx
Finding: On the issue page, title, description and acceptance are editable inline; the brief is shown read-only, collapsed and labelled as written for the agent. Design and Notes were folded into the brief and removed.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
podium:PLAN-03: 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. cross-checked
podium:PLAN-03
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.
- End-to-end multi-day parent behavior remains a separate question.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/model/src/entities/issue-dep.ts
Finding: Dependencies are durable replicated edges with from/to IDs and a relationship type.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/issues/registry.ts
Finding: Issue registry retains create, share, reparent and ship operations. Agent top-level create produces Proposed work. attachSession checks only input.targetId, so it does not guard the implicit current-issue anchor. The close and update-done guard refuses constrained callers while an issue session is computing unless confirmInterrupt is true; operator scope all bypasses it.
-
Podium apps/server/src/modules/issues/service/hierarchy.ts
Finding: addDep accepts only blocked-by, related, discovered-from, supersedes and duplicates, refuses any other type, refuses self-dependencies and cycles, and refuses a blocked-by edge on a phase. Reparent keeps the issue row.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Finding: Layered troubleshooting; an issue cannot start if blocked by an open dependency, machine offline, repository absent, harness not logged in, or worktree conflict; crash export command.
-
Podium apps/server/src/modules/issues/service/deck.ts
Finding: Server deck snapshot rolls task state words and counts up from leaf tasks and joins seats, blockers and proposals. Rollup is a derived view; hierarchy.ts notes a phase never closes by itself.
-
Podium packages/model/src/entities/issue-vocabulary.ts
Finding: Issue types are task, phase and decision. Epic, milestone, automation, bug, feature, chore, story and spike are retired, with labels replacing the kind words. Only the user closes a decision. Dependency types are fixed to blocked-by, related, discovered-from, supersedes and duplicates, with a CHECK constraint.
-
Finding: Live page documents blocked-by as the default dependency type and the only type that makes an issue blocked; the blocks type is no longer shown.
podium:PLAN-04: 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.
podium:PLAN-04
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.
- Source and docs inspected; no injected context, compaction or recall scenario observed.
- Docs describe transcripts as mirrored and indexed, while source gates the full-text index on the command-palette flag; without it search falls back to LIKE. Skills, provenance, correction, deletion and freshness controls remain search-scoped unknowns.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium docs/agents/podium-specs.md
Finding: Inspected v0.3.0 implementation: format, human decisions, superseded status, CLI command reference. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/modules/specs/service.ts
Finding: Inspected v0.3.0 implementation: 53–62 inputs; service methods and repo-root validation; no feature flag gate. Availability is scoped in the linked criterion record.
-
Finding: CLI help lists spec only when Specs is enabled; direct spec command dispatch remains unconditional.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Podium packages/harness/src/issue-system-pointer.ts
Finding: The always-on issue-system pointer reaches agents through session instructions. It names podium issue deck, the coordinator claim, Podium-Issue commit trailers, artifacts, offers and the review-before-close rule. Server close checks are separate and can be overridden with confirmInterrupt.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Podium packages/harness/src/driver/families/boundary-hook.ts
Finding: Shared Claude/Codex hook codec maps SessionStart, UserPromptSubmit and PreCompact to driver boundary context. SessionStart with source compact rearms before priming. Codex does not use PreCompact for additionalContext. Source inspected, not observed in this pass.
-
Podium packages/harness/src/driver/families/claude-sdk/protocol.ts
Finding: Claude stream engine receives appended instructions and in-band boundary callbacks. The turn deadline is armed only when timeoutMs is supplied.
-
Podium packages/harness/src/driver/families/codex/runtime.ts
Finding: Codex server-family sessions pass session instructions to their host as developer instructions.
-
Podium packages/harness/src/driver/families/grok-acp/runtime.ts
Finding: Grok ACP sends instructions through _meta.rules. Comments describe upstream CLI measurement; this research pass inspected code and did not repeat that measurement.
-
Podium packages/harness/src/driver/families/opencode/runtime.ts
Finding: OpenCode sends session instructions as the prompt system field. Adopted sessions have a separate context path; no blanket cross-harness takeover guarantee follows.
-
Podium apps/daemon/src/control/session.ts
Finding: The daemon carries Podium instructions and relay environment through terminal and engine launch. Terminal reattachment goes through runtime.adopt and a registered handle. A surviving process is required; this is not proof of recovery from worker death.
-
Podium packages/runtime/src/config.ts
Finding: Transcript mirroring defaults on, with environment, file and Settings precedence.
-
Podium apps/server/src/modules/memory/lake.ts
Finding: Server code mirrors daemon transcript bytes. Full-text indexing depends on the command-palette flag (see v030-search-flag). Conversation recall does not establish curated memory, repository-code search or memory correction and deletion controls.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
-
Podium apps/server/src/store.ts
Finding: The command-palette flag decides at boot whether full-text indexing of conversations and transcripts exists. It is edge-visibility and default off; with it off, search falls back to LIKE.
-
Podium apps/server/src/relay.ts
Finding: The spec pointer is registered with featureEnabled(specs), so agents are told about the spec CLI only with the flag on.
-
Podium v0.3.0: docs/agents/podium-specs.md
Finding: Experimental specs guidance permits only explicit human decisions/context and directs an agent to flag contradictions, mark superseded decisions and retain stable SP references. This is agent guidance, not an enforced approval or drift-detection engine.
podium:PLAN-05: 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.
podium:PLAN-05
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.
- Only attachment storage is documented; no scenario run.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Podium apps/server/src/store.ts
Finding: The command-palette flag decides at boot whether full-text indexing of conversations and transcripts exists. It is edge-visibility and default off; with it off, search falls back to LIKE.
-
Podium v0.3.0: apps/server/src/modules/superagent/tools.ts
Finding: Assistant tools expose ranked internal sessions/issues/comments/conversation/transcript/settings results with identifiers and snippets. Conversation/full-text search tools are removed when the default-off command-palette flag leaves indexing disabled. They do not search repository code or external knowledge.
podium:PLAN-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. cross-checked
podium:PLAN-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.
- Source inspection establishes implementation at v0.3.0; hands-on behavior remains unverified.
- The working-session close guard is an overridable source-level check, not proof that human approval is required for every close.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/model/src/entities/issue.ts
Finding: Issue records are distinct replicated entities with durable fields and projections; this is a domain model rather than terminal tab metadata.
-
Podium apps/server/src/modules/issues/registry.ts
Finding: Issue registry retains create, share, reparent and ship operations. Agent top-level create produces Proposed work. attachSession checks only input.targetId, so it does not guard the implicit current-issue anchor. The close and update-done guard refuses constrained callers while an issue session is computing unless confirmInterrupt is true; operator scope all bypasses it.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Podium apps/server/src/modules/issues/service/crud.ts
Finding: CRUD create defaults stage to backlog and audience to human. claim is an update of assignee and stage with no exclusivity check of its own. Moving a closed issue back to an open stage emits issue.reopened.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium apps/web/src/features/issues/IssuesFilters.tsx
Finding: The issue board has a filter control alongside CLI search by text, status, priority, type and label.
podium:PLAN-07: 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. cross-checked
podium:PLAN-07
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.
- Source reachability read at v0.3.0. No live attachment, child creation or enforcement test was performed.
- Direct agent attach --id to a Proposed target is blocked. Operator attachment and qualifying spawn-time cwd ownership are different entry routes. Spawn-time binding now also needs mayJoinIssue to pass. A bare cwd capability fallback does not itself provide the persisted attachment.
- newSubissue does not spawn another process. It attaches the existing session to a human-audience backlog child, which is why it cannot be described as universally inert. Other active sessions may require a replacement coordinator.
- The confirmInterrupt close guard does not fix the proposed-parent attach path. Concurrent-edit handling and attribution-display behavior remain untested.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/model/src/entities/issue.ts
Finding: Issue records are distinct replicated entities with durable fields and projections; this is a domain model rather than terminal tab metadata.
-
Podium apps/server/src/modules/issues/registry.ts
Finding: Issue registry retains create, share, reparent and ship operations. Agent top-level create produces Proposed work. attachSession checks only input.targetId, so it does not guard the implicit current-issue anchor. The close and update-done guard refuses constrained callers while an issue session is computing unless confirmInterrupt is true; operator scope all bypasses it.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Podium apps/server/src/issue-mcp.ts
Finding: Issue MCP tools are generated from the shared ISSUE_COMMANDS registry as issue_<command> tools, so CLI and MCP operate on the same issue commands.
-
Podium packages/model/src/authz/issue-authz.ts
Finding: Issue authorization policy defines viewer, worker and admin roles mapped to read, write and manage actions with closed scope kinds (all, none, subtree, owned, self). Source comment at lines 58-62 says the current scope is all and subtree is the reserved per-issue extension. The operator is unconstrained and agents carry a constrained capability. Commands carry actor and on-behalf-of fields.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Podium apps/server/src/modules/sessions/session-start.ts
Finding: Session start uses explicit input.issueId, otherwise soleOwnerForCwd(input.cwd) when mayJoinIssue passes for the owner, and stores the chosen issue. New since 652072f: the ownership check. It has no Proposed-stage check.
-
Podium apps/server/src/modules/issues/access-index.ts
Finding: Cwd binding chooses the sole owning issue worktree from worktreeOwnerCandidates and excludes registered repository roots. It does not filter stage. A Proposed issue needs an existing recorded qualifying worktree for this route.
-
Podium apps/server/src/modules/sessions/session-meta-ops.ts
Finding: The explicit session issue ID is persisted without a Proposed-stage check. attachSession now reads it from the session record through readSessionIssueId.
-
Podium apps/server/src/modules/issues/service/attention.ts
Finding: With newSubissue and no targetId, attachSession uses the explicit current session issue as parent, calls CRUD create directly and attaches the existing session. A real parent requires confirmRehome; other active sessions can trigger the coordinator-replacement guard. No Proposed-stage check appears in this path.
-
Podium apps/server/src/modules/issues/service/crud.ts
Finding: CRUD create defaults stage to backlog and audience to human. claim is an update of assignee and stage with no exclusivity check of its own. Moving a closed issue back to an open stage emits issue.reopened.
-
Podium apps/server/src/modules/sessions/session-authz.ts
Finding: A known relayed session gets worker scope for its explicit issue subtree, falling back to issueForCwd, or none.
-
Podium apps/server/src/application/issue-attach-orchestrator.ts
Finding: The authenticated attach orchestrator carries the principal through a transaction into attention.attachSession; it adds no Proposed-stage check.
-
Podium packages/model/src/entities/issue-vocabulary.ts
Finding: Issue types are task, phase and decision. Epic, milestone, automation, bug, feature, chore, story and spike are retired, with labels replacing the kind words. Only the user closes a decision. Dependency types are fixed to blocked-by, related, discovered-from, supersedes and duplicates, with a CHECK constraint.
-
Podium apps/server/src/issue-authz.ts
Finding: The server gate refuses a constrained capability writing an existing issue outside its subtree unless --outside-scope is passed. A scope of all returns without a subtree check.
podium:PLAN-08: 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.
podium:PLAN-08
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.
- Label the Specs UI and agent guidance as experimental and default-off. Do not claim automatic drift detection, guaranteed compliance or automatic spec-based shipping veto.
- Docs call spec commands default-off and not baseline; source shows the flag gates UI, help text and agent pointer only, while command dispatch and the server service are ungated. Both hold, so the answer says experimental and default-off with the CLI usable directly.
- Revision history is limited to marking decisions superseded; approvals and drift detection are not described.
- Spec reads and writes run on the server host: the specs service accepts only registered repository roots that exist on that host, so a repository present only on another paired machine is refused (the source calls this prototype scope).
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium docs/agents/podium-specs.md
Finding: Inspected v0.3.0 implementation: format, human decisions, superseded status, CLI command reference. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/modules/specs/service.ts
Finding: Inspected v0.3.0 implementation: 53–62 inputs; service methods and repo-root validation; no feature flag gate. Availability is scoped in the linked criterion record.
-
Finding: CLI help lists spec only when Specs is enabled; direct spec command dispatch remains unconditional.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Podium apps/server/src/relay.ts
Finding: The spec pointer is registered with featureEnabled(specs), so agents are told about the spec CLI only with the flag on.
-
Podium v0.3.0: docs/agents/podium-specs.md
Finding: Experimental specs guidance permits only explicit human decisions/context and directs an agent to flag contradictions, mark superseded decisions and retain stable SP references. This is agent guidance, not an enforced approval or drift-detection engine.
podium:COORD-01: 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. cross-checked
podium:COORD-01
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.
- Documentation read; no concurrency run. Agents sharing one workspace need explicit file ownership per the docs.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium packages/issue-client/src/deck.ts
Finding: podium issue deck prints the same snapshot: counts by state, phases, tasks, session seats with harness, model and effort, unmet blockers and proposals.
-
Podium apps/server/src/modules/messages/handlers/spawn-agent.ts
Finding: Agent-initiated spawns take a budget of 10 per target issue per UTC day, shared with mail-triggered spawns. Human-principal spawns are exempt.
podium:COORD-02: 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. cross-checked
podium:COORD-02
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.
- Docs and source read; two workers contending for one task were not tested.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/shipping/queue.ts
Finding: Inspected v0.3.0 implementation: queue grouping, validation cache scope, dependency components. Availability is scoped in the linked criterion record.
-
Podium apps/web/src/app/RightRail.tsx
Finding: Right rail panels are Task, Superagent, Git, Files, Shell, Messages and Shipping. The Queues pane and merge-queue flag are gone. Shipping stays feature-gated.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
-
Podium apps/server/src/modules/issues/service/crud.ts
Finding: CRUD create defaults stage to backlog and audience to human. claim is an update of assignee and stage with no exclusivity check of its own. Moving a closed issue back to an open stage emits issue.reopened.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
-
Podium apps/server/src/modules/issues/service/seat.ts
Finding: A session seat decides whether it may talk to the user or must ask a coordinator. Below-coordinator sessions are pointed at issue mail.
podium:COORD-03: 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. cross-checked
podium:COORD-03
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.
- Documentation and source read; no delegated task, child result or follow-up was executed. Harness support differs.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
-
Podium packages/model/src/authz/issue-authz.ts
Finding: Issue authorization policy defines viewer, worker and admin roles mapped to read, write and manage actions with closed scope kinds (all, none, subtree, owned, self). Source comment at lines 58-62 says the current scope is all and subtree is the reserved per-issue extension. The operator is unconstrained and agents carry a constrained capability. Commands carry actor and on-behalf-of fields.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium packages/issue-client/src/deck.ts
Finding: podium issue deck prints the same snapshot: counts by state, phases, tasks, session seats with harness, model and effort, unmet blockers and proposals.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
-
Podium apps/server/src/modules/issues/service/seat.ts
Finding: A session seat decides whether it may talk to the user or must ask a coordinator. Below-coordinator sessions are pointed at issue mail.
-
Podium apps/server/src/modules/messages/handlers/spawn-agent.ts
Finding: Agent-initiated spawns take a budget of 10 per target issue per UTC day, shared with mail-triggered spawns. Human-principal spawns are exempt.
podium:COORD-04: 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.
podium:COORD-04
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.
- Source inspected only; no automation was created or fired. The feature is experimental, edge-listed and default off.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Pure scheduler decision: occurrences more than one hour late are recorded missed and not backfilled; an automation whose previous session is still live is skipped as overlap; otherwise a session is spawned.
-
Podium automations/scheduler.ts
Finding: Server-owned scheduler ticks every 30 seconds after a 20 second boot delay, single-flight, inert until an enabled automation exists; schedule kinds are cron and once (model automation.ts line 48).
-
Podium v0.3.0: apps/server/src/modules/automations/service.ts
Finding: Scheduler records occurrence outcomes spawned/error/missed/skipped_overlap; nextRunAt re-arms after spawn attempt success or terminal error. Resume may fall back to fresh only for missing durable session or resume ref. Outcome spawned is not verified task completion.
-
Podium apps/server/src/relay.ts
Finding: At v0.3.0 the relay still constructs EventLogRetention and AutomationScheduler but no longer starts them. Comments mark both timers as retired: the janitor owns event-log pruning and automation fires.
-
Podium apps/server/src/janitor-host.ts
Finding: The janitor runs in a worker thread owned by the server process, and the server always starts it. It reads the database read-only and writes through the server's maintenance routes.
-
Podium packages/janitor/src/janitor.ts
Finding: The janitor ticks every 30 seconds by default. Each housekeeping tick runs event-log pruning, using the age and row limits from the server lease, and applies due automation fires, among other jobs.
-
Podium apps/server/src/modules/automations/service.ts
Finding: The janitor's fenced automation-fire job calls applyObservedOccurrence. The server revalidates the schedule and runs the same decideTick policy (grace, overlap, re-arm) before it spawns.
podium:COORD-05: 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. cross-checked
podium:COORD-05
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.
- Basic view switching is not the same as the separately gated draft-sync feature. No in-run amendment or approval prompt was exercised in chat and terminal modes.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/web/src/features/terminal/AgentPanel.tsx
Finding: Chat and CLI buttons select views of one session and keep the terminal mounted.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
-
Podium apps/server/src/auto-continue.ts
Finding: When a global master switch is on, sessions in a retryable errored phase receive continue on escalating backoff from 10 seconds to a 5 minute cap until they recover.
-
Podium packages/model/src/settings/preferences.ts
Finding: Settings defaults: auto-continue off; worktree GC mode propose after 14 days; git workflow mergeStyle ff-only, pr or ask (default ff-only) and autoRebaseBeforeMerge default true.
-
Finding: Notification service pushes attention notices through web clients, ntfy topics and Telegram chats; gated by the notifications feature flag (edge visibility, default off).
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Podium apps/server/src/modules/sessions/inbox.ts
Finding: A controller-origin human chat defaults to steer; other senders default when-ready. The initial prompt remains when-ready. Durability alone does not prove that a harness has consumed the prompt.
-
Podium packages/harness/src/driver/families/terminal/runtime.ts
Finding: A busy terminal with queuesBusyInput takes steer input into the native TUI queue. Undeclared harnesses downgrade to queue; compaction waits. Terminal adoption validates process identity and observation lease. No live steering or restart scenario was run.
-
Podium claude-code terminal manifest
Finding: The claude-code terminal manifest declares queuesBusyInput true. Together with the terminal driver this enables immediate typing of human steer input into a running native queue. Native consumption and timing were not observed in this research pass.
-
Podium codex terminal manifest
Finding: The codex terminal manifest declares queuesBusyInput true. Together with the terminal driver this enables immediate typing of human steer input into a running native queue. Native consumption and timing were not observed in this research pass.
-
Finding: The grok terminal manifest declares queuesBusyInput true. Together with the terminal driver this enables immediate typing of human steer input into a running native queue. Native consumption and timing were not observed in this research pass.
-
Podium opencode terminal manifest
Finding: The opencode terminal manifest declares queuesBusyInput true. Together with the terminal driver this enables immediate typing of human steer input into a running native queue. Native consumption and timing were not observed in this research pass.
-
Podium packages/model/src/entities/issue-vocabulary.ts
Finding: Issue types are task, phase and decision. Epic, milestone, automation, bug, feature, chore, story and spike are retired, with labels replacing the kind words. Only the user closes a decision. Dependency types are fixed to blocked-by, related, discovered-from, supersedes and duplicates, with a CHECK constraint.
-
Podium packages/harness/src/adapters/pi/index.ts
Finding: Pi adapter launches the native CLI with create-or-resume sessions and thinking levels as effort, and reads its stream for state. It declares no quota, no handoff and no hooks, and it does not declare queuesBusyInput.
-
Podium apps/server/src/modules/issues/service/seat.ts
Finding: A session seat decides whether it may talk to the user or must ask a coordinator. Below-coordinator sessions are pointed at issue mail.
podium:COORD-06: 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. cross-checked
podium:COORD-06
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.
- Source and release notes read; workload and navigation errors were not measured. Website panels are illustrative, not captures.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium apps/web/src/app/FlightDeckWaterfall.tsx
Finding: The waterfall component remains in the tag but its header says nothing mounts it: the flight deck redesign draws one Full view and the Timeline view was deleted. Earlier waterfall findings no longer describe the shipped deck.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium apps/server/src/modules/issues/service/deck.ts
Finding: Server deck snapshot rolls task state words and counts up from leaf tasks and joins seats, blockers and proposals. Rollup is a derived view; hierarchy.ts notes a phase never closes by itself.
-
Podium packages/issue-client/src/deck.ts
Finding: podium issue deck prints the same snapshot: counts by state, phases, tasks, session seats with harness, model and effort, unmet blockers and proposals.
podium:COORD-07: 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. cross-checked
podium:COORD-07
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.
- Source and docs read; no coordinator scenario run.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/issues/service/hierarchy.ts
Finding: addDep accepts only blocked-by, related, discovered-from, supersedes and duplicates, refuses any other type, refuses self-dependencies and cycles, and refuses a blocked-by edge on a phase. Reparent keeps the issue row.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Documented first-task loop: podium status, issue create, issue start --agent (creates branch and worktree), follow with issue show and session status, review evidence, close or merge. Requires a configured instance, a registered Git repository and one installed, authenticated harness.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
-
Podium packages/issue-client/src/deck.ts
Finding: podium issue deck prints the same snapshot: counts by state, phases, tasks, session seats with harness, model and effort, unmet blockers and proposals.
-
Podium packages/model/src/entities/agent-profile.ts
Finding: Agent profiles are named setups with ordered harness, model and effort candidates, an optional machine and markdown instructions. The first usable candidate is picked at session start, and sessions do not switch harness mid-run. Import and export use a Claude Code agent file at .podium/agents/<name>.md. People edit profiles; agents can only pick one.
-
Podium apps/server/src/modules/issues/service/seat.ts
Finding: A session seat decides whether it may talk to the user or must ask a coordinator. Below-coordinator sessions are pointed at issue mail.
podium:RUN-01: 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.
podium:RUN-01
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.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: payer, resources, region, expiry.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium: Three ways to use Podium; Every app connects to every Podium
Finding: The complete published execution choices are the user computer and the user VPS. Phone and browser clients connect to either one; the download page offers no Podium-operated execution host. Its phone choices are a phone browser and a native iPhone private beta, with no native Android client.
podium:RUN-02: Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
podium:RUN-02
Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: network.
-
Finding: Documented first-task loop: podium status, issue create, issue start --agent (creates branch and worktree), follow with issue show and session status, review evidence, close or merge. Requires a configured instance, a registered Git repository and one installed, authenticated harness.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Podium: packages/pty/src/backends/index.ts
Finding: The released terminal backend launches native harness processes through the host PTY. Inspection of the daemon launch paths and packages/pty for Docker, Podman, container, microVM, QEMU and Firecracker provisioning found no product-managed container or VM isolation. Git worktree separation and provider/host permissions are separate.
podium:RUN-03: 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. cross-checked
podium:RUN-03
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.
- No fresh worker-crash/server-restart or multi-day soak executed. Host uptime and provider limits remain requirements. Avoid claiming unlimited runtime.
-
Podium apps/web/src/features/settings/sections/hibernation.tsx
Finding: Inspected v0.3.0 implementation: 15–30 and 81–170: idle pressure, configurable idle-session target. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/modules/sessions/session-teardown.ts
Finding: Ordinary hibernation guards working and compacting agents; a separate age-backstop park path lacks that phase guard. This is not an unlimited active-session guarantee.
-
Finding: README at public tag v0.3.0 routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh. Persistent terminal, reconnection and self-hosting descriptions remain. Its Windows wording is superseded by the v0.3.0 release assets.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Finding: Backups are a stopped copy of the state root; Podium writes a database-only migration snapshot (three retained) before migrations; updater verifies release signatures; an epoch-safe restore exists but is not wired to a shipped command.
-
Podium apps/daemon/src/control/session.ts
Finding: The daemon carries Podium instructions and relay environment through terminal and engine launch. Terminal reattachment goes through runtime.adopt and a registered handle. A surviving process is required; this is not proof of recovery from worker death.
-
Podium packages/harness/src/driver/families/terminal/runtime.ts
Finding: A busy terminal with queuesBusyInput takes steer input into the native TUI queue. Undeclared harnesses downgrade to queue; compaction waits. Terminal adoption validates process identity and observation lease. No live steering or restart scenario was run.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
podium:RUN-04: 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. cross-checked
podium:RUN-04
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.
- Documentation read; no two-workspace environment test run.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: The headless installer installs missing prerequisites through apt and other supported package managers, or stops with a message when none is found.
podium:RUN-05: 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. cross-checked
podium:RUN-05
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.
- Source and docs read; no controlled failure induced. Quota display is monitoring, not an enforced limit.
-
Podium apps/server/src/modules/shipping/policy.ts
Finding: Default shipping policy lands on a local branch with fast-forward only and runs a configured validation profile (default argv bun run test, 10 minute timeout, resource lock validation:agent). The default target now resolves per repository base branch.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Podium apps/cli/src/agent-cli.ts
Finding: podium agent spawn starts a full Podium session (real PTY, visible in the UI) on an issue with --harness, --model, --effort and new --profile; the caller becomes parent; await is bounded (default 30s, max 300s). Help lists claude-code, codex, grok, opencode and cursor; it does not list pi, while the harness enum does.
-
Podium apps/cli/src/approval-cli.ts
Finding: Inside a managed session, management commands block up to 10 minutes for an operator decision; denied or failed requests exit nonzero; on timeout the request stays valid and the outcome arrives as issue mail.
-
Podium apps/server/src/auto-continue.ts
Finding: When a global master switch is on, sessions in a retryable errored phase receive continue on escalating backoff from 10 seconds to a 5 minute cap until they recover.
-
Podium packages/model/src/settings/preferences.ts
Finding: Settings defaults: auto-continue off; worktree GC mode propose after 14 days; git workflow mergeStyle ff-only, pr or ask (default ff-only) and autoRebaseBeforeMerge default true.
-
Podium apps/cli/src/quota-cli.ts
Finding: podium quota shows current plan usage limits per harness for each online daemon (account, plan, percent used, reset time), cached up to two minutes; it reports usage and is not a spend limit.
-
Podium packages/harness/src/driver/families/claude-sdk/protocol.ts
Finding: Claude stream engine receives appended instructions and in-band boundary callbacks. The turn deadline is armed only when timeoutMs is supplied.
-
Podium apps/server/src/modules/superagent/headless.ts
Finding: The one-shot headless server runner supplies timeoutMs, default 600000ms, to the daemon so its wait and enforced deadline agree. This is a source-level per-call budget, not a general operator token/spend limit.
-
Podium packages/harness/src/driver/families/headless/turn.ts
Finding: Hosted headless turns enforce a supplied timeoutMs; absent timeoutMs does not arm a turn deadline. Other lifecycle, provider and explicit-call limits remain separate.
-
Podium apps/server/src/modules/messages/handlers/spawn-agent.ts
Finding: Agent-initiated spawns take a budget of 10 per target issue per UTC day, shared with mail-triggered spawns. Human-principal spawns are exempt.
podium:RUN-06: 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. cross-checked
podium:RUN-06
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.
- Source and docs read; no worker failure or approval wait induced. Benchmark figures are a vendor claim from a bench VM, with its live half recorded as pending.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium apps/web/src/features/cost/TaskCostSection.tsx
Finding: Task cost UI prices recorded tokens from public per-model list prices and states they are not a bill. It lists every session that ran on the task with its own cost and harness, plus descendant rollups.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Finding: Layered troubleshooting; an issue cannot start if blocked by an open dependency, machine offline, repository absent, harness not logged in, or worktree conflict; crash export command.
-
Finding: Approval broker: agents request management operations through the relay, the operator approves or denies, the owning daemon executes, every step is appended to the issue activity log and the outcome is mailed to the agent; pending approvals are durable rows with no timeout.
-
Podium apps/web/src/features/usage/UsageView.tsx
Finding: Usage and analytics sheet shows what the machine agents spent at hour resolution over seven days, leading with list-price cost, with a quota ledger and per-task costs.
-
Podium apps/daemon/src/host-metrics.ts
Finding: Daemon samples host memory, load and disk; the web client shows host load and memory panels and hibernation policy reacts to pressure.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Server data access measurement
Finding: Vendor bench behind the 0.3.0 memory note. On a 4 CPU, 12 GB VM, server RSS was 326 MiB on a 4,867-issue corpus and 334 MiB on a 27,601-issue corpus, against 457 and 1,188 MiB before; boot to listen was 8% and 52% faster. SQL statements rose about 30%. The document says its live half was pending. Not reproduced by this research pass.
-
Podium apps/web/src/features/usage/UsageTasks.tsx
Finding: The usage sheet lists per-task costs from the same token records.
podium:RUN-07: 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. cross-checked
podium:RUN-07
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.
- Do not call this money actually spent or claim infrastructure cost included. Website figures are illustrative. Runtime accounting was not tested.
-
Podium packages/model/src/entities/cost.ts
Finding: Cost model holds per-task and per-session token totals, the harness each session used, own-versus-rollup schemas and recursive descendant traversal. New at v0.3.0: an addressed task comparison against a priced cohort median.
-
Podium apps/web/src/features/cost/TaskCostSection.tsx
Finding: Task cost UI prices recorded tokens from public per-model list prices and states they are not a bill. It lists every session that ran on the task with its own cost and harness, plus descendant rollups.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Podium apps/web/src/app/FlightDeck.tsx
Finding: Flight deck UI renders one mission: phases, tasks, seats, proposals and a cost chip, with sibling files for dependencies, seats and groups. No feature flag gates it. AppShell binds the toggle.
-
Podium apps/web/src/features/usage/UsageTasks.tsx
Finding: The usage sheet lists per-task costs from the same token records.
podium:RUN-08: 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. cross-checked
podium:RUN-08
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.
- Source and docs read; no capacity test run. Resource leases are advisory.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/shipping/queue.ts
Finding: Inspected v0.3.0 implementation: queue grouping, validation cache scope, dependency components. Availability is scoped in the linked criterion record.
-
Podium apps/web/src/app/RightRail.tsx
Finding: Right rail panels are Task, Superagent, Git, Files, Shell, Messages and Shipping. The Queues pane and merge-queue flag are gone. Shipping stays feature-gated.
-
Podium apps/web/src/features/settings/sections/hibernation.tsx
Finding: Inspected v0.3.0 implementation: 15–30 and 81–170: idle pressure, configurable idle-session target. Availability is scoped in the linked criterion record.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Podium apps/daemon/src/host-metrics.ts
Finding: Daemon samples host memory, load and disk; the web client shows host load and memory panels and hibernation policy reacts to pressure.
podium:TEAM-01: 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. cross-checked
podium:TEAM-01
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.
- Scope is the issue UI, member routes and backend handlers at v0.3.0. Do not infer shared-session collaboration or co-prompting from permission commands or the Members section.
-
Podium apps/web/src/features/issues/issue-page/IssueAbout.tsx
Finding: The issue About section exposes owner and visibility as read-only fields and deliberately omits sharing controls. The observer refactor does not establish a new sharing workflow.
-
Podium apps/web/src/features/issues/IssuePage.attribution.test.tsx
Finding: The issue attribution test expects no sharing controls; this pass inspected the test source without running it.
-
Podium apps/server/src/modules/issues/registry.ts
Finding: Issue registry retains create, share, reparent and ship operations. Agent top-level create produces Proposed work. attachSession checks only input.targetId, so it does not guard the implicit current-issue anchor. The close and update-done guard refuses constrained callers while an issue session is computing unless confirmInterrupt is true; operator scope all bypasses it.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Podium apps/server/src/member-routes.ts
Finding: Member routes list members, create invites and change or remove membership, and answer 403 unless the actor has the admin role.
-
Podium apps/web/src/features/settings/sections/members.tsx
Finding: Settings has a Members section with invite links, optional invitation email, member or admin role and member removal. Which installs reach it and how it behaves were not tested.
podium:TEAM-02: 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.
podium:TEAM-02
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.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.
-
Finding: Docs home: Podium runs native Claude Code, Codex, Grok, OpenCode, Cursor and Pi processes on machines you control; supported core is a local or self-hosted control system; built first for one operator supervising several agents. Its Windows matrix wording is superseded by v0.3.0 assets.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Podium packages/model/src/authz/issue-authz.ts
Finding: Issue authorization policy defines viewer, worker and admin roles mapped to read, write and manage actions with closed scope kinds (all, none, subtree, owned, self). Source comment at lines 58-62 says the current scope is all and subtree is the reserved per-issue extension. The operator is unconstrained and agents carry a constrained capability. Commands carry actor and on-behalf-of fields.
-
Podium apps/server/src/modules/sessions/session-authz.ts
Finding: A known relayed session gets worker scope for its explicit issue subtree, falling back to issueForCwd, or none.
-
Podium apps/server/src/member-routes.ts
Finding: Member routes list members, create invites and change or remove membership, and answer 403 unless the actor has the admin role.
-
Podium apps/web/src/features/settings/sections/members.tsx
Finding: Settings has a Members section with invite links, optional invitation email, member or admin role and member removal. Which installs reach it and how it behaves were not tested.
-
Podium: apps/server/src/auth-route.ts
Finding: The released client authentication routes use password-backed member sessions, cookies and paired mobile bearer tokens. Bounded inspection of the server authentication and membership code for SAML/OIDC/SSO found no enterprise single sign-on path. Coding-agent provider OAuth logins are separate.
podium:TEAM-03: 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.
podium:TEAM-03
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.
- Source and docs read; no approval flow was exercised.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Supervise a running agent session
Finding: Supervision commands: session status/read/recap/send (--wake)/continue/stop; stop refuses a dirty managed worktree unless forced; attention states (needs input, idle, working, retryable error, permission request).
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Finding: Approval broker: agents request management operations through the relay, the operator approves or denies, the owning daemon executes, every step is appended to the issue activity log and the outcome is mailed to the agent; pending approvals are durable rows with no timeout.
-
Podium apps/cli/src/approval-cli.ts
Finding: Inside a managed session, management commands block up to 10 minutes for an operator decision; denied or failed requests exit nonzero; on timeout the request stays valid and the outcome arrives as issue mail.
-
Podium public guide: guides/review-work
Finding: Review guide walks acceptance criteria/state, Git diffs, validation, artifacts and caveats, then an offer with merge and send-back feedback actions. This is single-issue guidance, not a measured six-task batch review.
-
Podium public guide: security/privacy
Finding: Daemon connects outbound; remote route should use TLS/private Tailscale. One-time pairing codes expire after one hour; native Claude/Codex credential copying is explicit per grant. This is access/pairing, not command sandboxing.
podium:TEAM-04: 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.
podium:TEAM-04
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.
- Source read only; no tamper or retention analysis.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: Approval broker: agents request management operations through the relay, the operator approves or denies, the owning daemon executes, every step is appended to the issue activity log and the outcome is mailed to the agent; pending approvals are durable rows with no timeout.
-
Podium v0.3.0: apps/server/src/modules/events/retention.ts
Finding: The event-retention service prunes podium_events older than14 days or beyond50000 rows, initially60seconds after boot then every6hours, bounded500row batches. Server relay constructs and starts it; this is separate from issue/comment/transcript retention.
-
Podium v0.3.0: apps/server/src/relay.ts
Finding: The release relay constructs EventLogRetention on store.events and registers its lifecycle. This connects retention to the shipped server rather than an isolated helper.
-
Podium apps/server/src/relay.ts
Finding: At v0.3.0 the relay still constructs EventLogRetention and AutomationScheduler but no longer starts them. Comments mark both timers as retired: the janitor owns event-log pruning and automation fires.
-
Podium apps/server/src/janitor-host.ts
Finding: The janitor runs in a worker thread owned by the server process, and the server always starts it. It reads the database read-only and writes through the server's maintenance routes.
-
Podium packages/janitor/src/janitor.ts
Finding: The janitor ticks every 30 seconds by default. Each housekeeping tick runs event-log pruning, using the age and row limits from the server lease, and applies due automation fires, among other jobs.
-
Podium packages/protocol/src/maintenance.ts
Finding: The maintenance protocol fixes event-log retention at 14 days and 50,000 rows with 500-row prune batches. The server hands these limits to the janitor in its maintenance lease.
podium:TEAM-05: 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. cross-checked
podium:TEAM-05
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.
- Docs read; no review fixture timed.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium apps/web/src/features/issues/board-shortcuts.ts
Finding: Board keys cover j/k and arrow movement, x to select, Enter to open, c to create, four property menus and a ? help sheet.
podium:TEAM-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. cross-checked
podium:TEAM-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.
- No second-user takeover tested; handoff is experimental and harness-dependent.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: CLI for creating, starting, planning, claiming, stating, todos, dependencies, spinoff attach and closing; agent-filed top-level issues land in proposed; operator-created issues start in backlog. Its --type blocks example is refused at v0.3.0, where the type is blocked-by.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Podium apps/cli/src/session-cli.ts
Finding: Session CLI: send (--wake queues and resumes a parked session), continue (errored phase only), status (no transcript text), read, recap, ask, title, handoff to another machine (target must be online; harness must support it), stop (frees worktree, keeps branch).
podium:SHIP-01: 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. cross-checked
podium:SHIP-01
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.
- Source inspection establishes implementation at v0.3.0; hands-on behavior remains unverified.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Podium docs/agents/podium-issues.md
Finding: The agent guide retains subtree write scope, explicit file ownership, issue artifacts and offers. Artifacts upload from the machine running the CLI with no issue worktree required. The Tray shows review-ready work through offers, and offer cards render the first three artifacts. Agents move work to review and offer Close; closing while sessions work needs --confirm-interrupt.
-
Podium apps/web/src/features/files/artifacts-tab.ts
Finding: Artifacts group as screens (images and video), documents and reports, with filter chips and search in ArtifactsTab.tsx.
-
Podium public guide: guides/review-work
Finding: Review guide walks acceptance criteria/state, Git diffs, validation, artifacts and caveats, then an offer with merge and send-back feedback actions. This is single-issue guidance, not a measured six-task batch review.
podium:SHIP-02: 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. cross-checked
podium:SHIP-02
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.
- Source inspected only; Shipping is experimental, edge-listed and default off, and nothing was executed. Non-Shipping merges do not run these gates.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium docs/agents/podium-specs.md
Finding: Inspected v0.3.0 implementation: format, human decisions, superseded status, CLI command reference. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/modules/shipping/policy.ts
Finding: Default shipping policy lands on a local branch with fast-forward only and runs a configured validation profile (default argv bun run test, 10 minute timeout, resource lock validation:agent). The default target now resolves per repository base branch.
-
Podium apps/server/src/modules/shipping/service.ts
Finding: Inspected v0.3.0 implementation: admit/run: frozen approval, validation locks, stale-policy checks and durable receipts. Availability is scoped in the linked criterion record.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
podium:SHIP-03: 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. cross-checked
podium:SHIP-03
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.
- Docs and source read; no draft PR fixture completed.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Finding: Documented first-task loop: podium status, issue create, issue start --agent (creates branch and worktree), follow with issue show and session status, review evidence, close or merge. Requires a configured instance, a registered Git repository and one installed, authenticated harness.
-
Understand repositories, worktrees, and machines
Finding: Repositories are registered per machine and can be cloned from a cloneable origin into ~/podium-repos; issues own a branch and linked worktree; Podium will not resolve branch conflicts; workspace fetch exposes another agent files read-only across machines.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Reference issue and session states
Finding: Issue stages proposed, backlog, planning, in_progress, review, shipping, done; session states working, idle, needs input, permission needed, retryable error, hibernated; close reasons. Its dependency list (blocks, tracks, caused-by, validates) is superseded by the fixed v0.3.0 list in v030-vocab.
-
Podium packages/model/src/settings/preferences.ts
Finding: Settings defaults: auto-continue off; worktree GC mode propose after 14 days; git workflow mergeStyle ff-only, pr or ask (default ff-only) and autoRebaseBeforeMerge default true.
-
Podium apps/daemon/src/repo-op.ts
Finding: Daemon repo operations include a guarded gh pr create --base <parent> --head <branch> --fill, used by the issue action pr.
-
Podium apps/server/src/modules/issues/service/workflow.ts
Finding: issue action pr records the URL printed by gh on the issue as prUrl.
podium:SHIP-04: 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. cross-checked
podium:SHIP-04
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.
- Source and docs read; no merge was performed.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/shipping/policy.ts
Finding: Default shipping policy lands on a local branch with fast-forward only and runs a configured validation profile (default argv bun run test, 10 minute timeout, resource lock validation:agent). The default target now resolves per repository base branch.
-
Podium apps/server/src/modules/shipping/service.ts
Finding: Inspected v0.3.0 implementation: admit/run: frozen approval, validation locks, stale-policy checks and durable receipts. Availability is scoped in the linked criterion record.
-
Finding: Delegation shapes: another session on the same issue, child issue with its own worktree, or discovered-from top-level issue; podium agent spawn/status/await; durable mail with optional expected response; advisory lock leases. States Podium does not serialize agents editing one worktree.
-
Finding: Review path: issue artifacts, stage review, diff and checks, podium offer buttons, merge under merge-lock, issue action merge closes the issue; feedback keeps it open. Its rule that artifact sources sit inside the issue worktree is superseded at v0.3.0.
-
Finding: Approval broker: agents request management operations through the relay, the operator approves or denies, the owning daemon executes, every step is appended to the issue activity log and the outcome is mailed to the agent; pending approvals are durable rows with no timeout.
podium:SHIP-05: 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. cross-checked
podium:SHIP-05
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.
- Source inspected only; Shipping is an edge feature that defaults off.
-
Podium packages/issue-client/src/commands.ts
Finding: The issue command table at v0.3.0 has 64 named commands. It creates, edits, claims, comments on, labels, archives, searches and links issues, sets state and todos, runs git actions (rebase, pr, merge, integrate), hands issues to Shipping, flags needs-human questions, subscribes agents to events and attaches artifacts. New since 652072f: deck, move, seat, labels and --profile. Removed: lint, --color, --design and --notes. --type accepts task, phase or decision. Close and update accept --confirm-interrupt.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/shipping/service.ts
Finding: Inspected v0.3.0 implementation: admit/run: frozen approval, validation locks, stale-policy checks and durable receipts. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/modules/issues/service/workflow.ts
Finding: issue action pr records the URL printed by gh on the issue as prUrl.
podium:SHIP-06: 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. cross-checked
podium:SHIP-06
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.
- Source inspection of shipping controls does not establish batch-review usability. Queue locks and cached validation apply to shipping; they are not global resource controls for arbitrary agent tests. No claim is made here about automatic repair.
-
Podium packages/protocol/src/features.ts
Finding: Feature registry at v0.3.0: draft-sync, command-palette, git-panel, messages-panel, shipping, session-handoff, workflows, specs, automations, notifications and shell-density are edge-visibility; runtime-drivers, settings-search and podium-development are stable-visibility; shipwright is hidden. Every flag defaults off. Edge flags are listed only on the edge channel; a config.json value can force any flag. The merge-queue flag was removed.
-
Podium apps/server/src/modules/shipping/policy.ts
Finding: Default shipping policy lands on a local branch with fast-forward only and runs a configured validation profile (default argv bun run test, 10 minute timeout, resource lock validation:agent). The default target now resolves per repository base branch.
-
Podium apps/server/src/modules/shipping/service.ts
Finding: Inspected v0.3.0 implementation: admit/run: frozen approval, validation locks, stale-policy checks and durable receipts. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/modules/shipping/queue.ts
Finding: Inspected v0.3.0 implementation: queue grouping, validation cache scope, dependency components. Availability is scoped in the linked criterion record.
-
Podium apps/server/src/relay.ts
Finding: The relay constructs the shipping service and a ShipwrightService. The hidden shipwright flag comment calls the repair engine dormant, so no automatic repair claim is made.
-
Podium apps/web/src/app/RightRail.tsx
Finding: Right rail panels are Task, Superagent, Git, Files, Shell, Messages and Shipping. The Queues pane and merge-queue flag are gone. Shipping stays feature-gated.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Podium public guide: guides/review-work
Finding: Review guide walks acceptance criteria/state, Git diffs, validation, artifacts and caveats, then an offer with merge and send-back feedback actions. This is single-issue guidance, not a measured six-task batch review.
podium:OWN-01: 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. cross-checked
podium:OWN-01
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.
- Root repository LICENSE establishes Apache 2.0 at v0.3.0; third-party notices and hosted-service terms are separate. Hosted parity unknown.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Public annotated tag ca1c848f97be633466d0abf161db46e9dd5659c5 peels to commit ec6ff505f69aeb358eb744596e70e984996c2e42, tagged 2026-11-05. The local read-only clone resolves v0.3.0 to the same commit, and 81 cited or sampled files matched raw.githubusercontent.com byte for byte.
podium:OWN-02: 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. cross-checked
podium:OWN-02
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.
- Docs read; no export, import or cancellation test.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Finding: Backups are a stopped copy of the state root; Podium writes a database-only migration snapshot (three retained) before migrations; updater verifies release signatures; an epoch-safe restore exists but is not wired to a shipped command.
-
Podium packages/runtime/src/config.ts
Finding: Transcript mirroring defaults on, with environment, file and Settings precedence.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Podium packages/telemetry/src/consent.ts
Finding: Absent usage consent counts as on; absent crash consent counts as off. An explicit off stays off. The comment dates opt-out usage reports to 0.2.0.
-
Podium configuration reference, Podium Connect
Finding: PODIUM_CONNECT defaults to on. A server with a public URL registers its installation id and public key once with connect.podium.do, then publishes that URL on start, on change, after a transfer and daily. Nothing is sent before a public URL exists. Off clears the published record and stops. The live configuration page retrieved 2026-11-06 does not mention Connect.
podium:OWN-03: 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. cross-checked
podium:OWN-03
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.
- Docs and source read; no network capture. Public privacy, install, configuration and availability docs, revised on 2026-11-06, now agree with docs/TELEMETRY.md and consent.ts at v0.3.0. The 0.2.0 and 0.3.0 release notes do not mention this change. Podium Connect is on by default for servers with a public URL: it registers an installation id and public key and publishes that URL to connect.podium.do. It has its own switch, PODIUM_CONNECT, and is documented outside the telemetry contract. Podium does not state training use or residency.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
-
Finding: Usage reports are on by default and sent once a day; crash reports are off unless turned on. Nothing is asked during setup. Fields are a fixed schema that excludes paths, prompts, transcripts and code. The relay drops IP addresses and forwards to PostHog Cloud. Settings, Privacy, podium telemetry off, DO_NOT_TRACK=1 and PODIUM_TELEMETRY=off turn reports off. The first report goes out about a minute after first start.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Understand how Podium runs agents
Finding: Server owns issues, sessions, artifacts; a daemon on each machine launches harnesses in real pseudo-terminals and connects outward; clients attach to live terminals and disconnecting does not end the session.
-
Understand issues, sessions, agents, and harnesses
Finding: Issues are durable work records separate from sessions; one issue can retain several sessions; stopping a process hibernates a resumable session keeping transcript and branch; harness capabilities differ by harness.
-
Finding: Stable command groups: lifecycle, work (issue, session, agent, mail, offer, worktree, workspace, lock, merge-lock), machines and access (machine, auth, quota, telemetry). Workflow, spec, automation, notification, shipping and handoff commands are behind default-off flags and not baseline.
-
Configure a Podium installation
Finding: State lives in ~/.podium; modes all-in-one, server, daemon, client, supervisor; transcriptLake default on; unlisted PODIUM_* variables are not a public contract. Its telemetry.usage default is superseded at v0.3.0: absent usage counts as on.
-
Protect Podium data and credentials
Finding: Daemons connect outward; pairing codes expire in one hour and copy Claude Code and Codex credentials only when enabled; artifacts are immutable server copies; lifecycle commands and automation requests may need operator approval; harnesses run with host account permissions; hosted PostHog and website Google Analytics and Ads are separate paths. Its statement that self-hosted telemetry is opt-in is superseded at v0.3.0 by telemetry-doc and v030-consent.
-
Finding: Layered troubleshooting; an issue cannot start if blocked by an open dependency, machine offline, repository absent, harness not logged in, or worktree conflict; crash export command.
-
Podium packages/runtime/src/config.ts
Finding: Transcript mirroring defaults on, with environment, file and Settings precedence.
-
Podium packages/telemetry/src/consent.ts
Finding: Absent usage consent counts as on; absent crash consent counts as off. An explicit off stays off. The comment dates opt-out usage reports to 0.2.0.
-
Podium docs: security and privacy
Finding: Live page now says a self-hosted host sends one anonymous usage report a day unless turned off, the default since 0.2.0, and that setup does not ask.
-
Finding: Live page now says setup does not ask about telemetry, usage reports are on by default and crash reports off. Windows desktop is Experimental; a release can publish without it.
-
Podium docs: feature availability
Finding: Live page lists usage reports on by default and crash reports opt-in, says each release also builds an experimental Windows x64 installer, and still says reviewed sources do not confirm native iPhone distribution.
-
Podium telemetry contract, report tiers
Finding: Usage reports carry schema, installId, version, os, arch, bucketed installAge and machines, session counts per harness and whether issues were used. Crash reports carry schema, installId, version, os, arch, a fixed errorType and up to 20 frames, each a path inside the Podium source tree, a line and a function when there is one. Crash reports carry Podium source lines, so they are off unless turned on. Error messages and frames outside the Podium install are dropped. The never-sent list names filesystem paths, repo names, prompts, transcripts and your code, so it does not cover the Podium source paths in crash frames. This refines the telemetry-doc record.
-
Podium packages/telemetry/src/schema.ts
Finding: The report schema defines usage reports with sessions and features records, and stack frames with file, line and optional fn. Crash reports hold at most 20 frames.
-
Podium configuration reference, Podium Connect
Finding: PODIUM_CONNECT defaults to on. A server with a public URL registers its installation id and public key once with connect.podium.do, then publishes that URL on start, on change, after a transfer and daily. Nothing is sent before a public URL exists. Off clears the published record and stops. The live configuration page retrieved 2026-11-06 does not mention Connect.
podium:OWN-04: 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. cross-checked
podium:OWN-04
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.
- podium.do/pricing returned HTTP 404 on 2026-11-06 and no plan page was found; this is a search gap, not proof that nothing is charged for hosted use.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Finding: Pricing route returned 404 on 2026-11-06. No price table was found on the checked official pages. This is a bounded search result, not a claim that pricing cannot exist elsewhere.
podium:OWN-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. cross-checked
podium:OWN-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.
- The repository had 50 GitHub stars on 2026-11-06; that is context, not a reliability measure. Only the latest release and main receive security fixes.
-
Finding: README at public tag v0.3.0 is byte-identical to the 652072f revision. It routes desktop downloads to podium.do/download and the stable installer to podium.do/install.sh, and still says Windows is coming soon, which the v0.3.0 release assets supersede. Native CLI sessions, shared issue tools, delegation and self-hosting descriptions remain.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: GitHub API reports a public Apache-2.0 repository, 50 stars, 3 forks, 7 open issues or PRs and pushed_at 2026-11-06T11:08:29Z. Popularity is context, not a capability measure.
-
Finding: GitHub releases API lists stable v0.3.0 (2026-11-05), v0.2.0 (2026-10-11) and v0.1.0 (2026-08-21), plus rolling edge and dev prereleases.
-
Finding: Changelog at v0.3.0 lists 0.2.0 (reliable chat, cost per task, Pi fully supported, experimental Windows and Linux desktop builds, safer updates) and 0.3.0 (flight deck, calmer chat and workspace, less memory, more reliable updates). Upgrade notes: automatic database backup before migrating; rollback means restoring podium.db.backup-vupdate-*; design and notes text is appended to the brief; task colors are dropped.
-
Finding: Vulnerabilities are reported privately via GitHub Security Advisories or email; acknowledgement within 7 days is stated; only the latest release and main get fixes; server is designed for loopback or an authenticated proxy; agent sessions execute real shell commands.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Stable release published 2026-11-05: flight deck, calmer chat and workspace, reduced server memory and more reliable updates. Assets include macOS arm64 and x64 dmg, Linux amd64 AppImage, Windows x64-setup.exe, headless bundles for darwin and linux (arm64 and x64), install.sh and SHA256SUMS. The memory figures in the notes are the vendor benchmark, not an independent result.
-
Finding: Stable release: more reliable chat, cost per task on the task header and usage sheet, Pi fully supported, improved mobile app, experimental Windows and Linux desktop builds, updates that show progress and roll back on failure. Sessions running during the upgrade keep running on the old terminal host.
-
Finding: Stable v0.3.1, published 2026-11-06, lists one change: fixed update failures in rare configurations. The diff from v0.3.0 is desktop payload startup, client registration and Codex rollout recovery; features.ts, packages/telemetry and docs/TELEMETRY.md are unchanged.
podium:OWN-08: 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. cross-checked
podium:OWN-08
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.
- Download paths were observed to redirect without login or payment; installation and first run were not tested.
-
Finding: Repository license is Apache 2.0. Hosted service terms and price were not established.
-
Podium apps/web/src/features/settings/sections/shared.tsx
Finding: Managed accounts cover a Claude subscription setup token, Anthropic API keys and OpenAI API keys for coding. OpenRouter is offered for the background role only because the shipped coding CLIs do not consume that key.
-
Finding: Home page offers Apple Silicon and Intel Mac downloads, a Windows x64 installer and Linux AppImage both marked Experimental, server install on a VPS, phone browser access and a native iPhone app in private beta. It names Claude Code, Codex, Cursor, OpenCode, Grok and Pi. It describes the flight deck, chat and CLI views, proposed tasks, offers, a reading mode, one artifact page per task with screenshots, recordings, documents and reports, and task cost estimates at list price. Product panels are labelled illustrative. The waterfall preview wording is gone.
-
Finding: Download page shows v0.3.0, 5 Nov 2026. macOS Apple Silicon and Intel are Stable (macOS 11 or later, signed and notarized). Linux AppImage x64 and Windows installer x64 are Experimental. The Linux server (x64 or arm64) is Stable. Phone browser works on iPhone or Android with Add to Home Screen. iPhone app is private beta (iOS 16.4 or later). Phones pair with a QR code in Settings, Connected devices. The page says free and open source.
-
Finding: Redirect-only HEAD requests on 2026-11-06 to /download/macos-arm64, macos-x64, linux-x64 and windows-x64 each answered 302 to the matching v0.3.0 GitHub release asset without authentication. The arm64 asset then answered 200 with 87,002,781 bytes and last-modified 2026-11-05. Download access was observed; installation and application behavior were not tested.
-
Finding: Separates supported core, conditional paths, preview clients, experimental features and unconfirmed hosted behavior. Page text predates 0.2.0: it still says Windows packaging is disabled in the default release matrix and calls usage telemetry opt-in, both superseded by the v0.3.0 release assets and telemetry source. Billing, hosted metering and retention controls are still listed as not implemented.
-
Finding: Install paths: macOS desktop, headless Linux x86_64 and ARM64, Linux AppImage preview, Windows experimental, hosted Podium unconfirmed. Setup registers a Git repository, detects harness login and supports Tailscale, Cloudflare quick tunnel or reverse proxy. Its opt-in telemetry step and Windows pipeline wording are superseded at v0.3.0.
-
Finding: Settings, Machines, Add machine creates a single-use hour-long pairing install command for a Linux host; verify with machine list/show/reprobe; place issues with issue start --machine; portable session handoff is not baseline stable.
-
Finding: Pricing route returned 404 on 2026-11-06. No price table was found on the checked official pages. This is a bounded search result, not a claim that pricing cannot exist elsewhere.