Player profile
Podium
Podium is an Apache-2.0 app that keeps issues, sessions, and agent terminals in one task system, with a daemon running each harness in a real terminal.
Profile
Where it fits
The install docs support a macOS desktop app on Apple silicon and Intel, and a headless Linux bundle on x86_64 and ARM64. The Linux installer is curl -fsSL https://podium.do/install.sh | sh, and it places the bundle under ~/.local/share/podium. Hosted Podium is listed for people who already have access from the Podium team, with production availability unconfirmed. An unconfigured install starts all-in-one on port 18787 and prints a setup URL. Default state lives in ~/.podium. Setup registers a git repository and checks that a harness is installed and logged in. The docs say a public server can reach repositories, terminals, and agent credentials on paired machines, and they tell you to require authentication and TLS or keep the server on a private network. With password protection on, the form asks for Email and Password. The docs say to enter user:sole in the Email field and the Podium password in the Password field.
The architecture page separates four pieces. The server stores issues, dependencies, sessions, messages, settings, and artifact copies. A daemon on each machine launches the harness in a pseudo-terminal and connects outward over WebSocket, so a remote daemon does not need an inbound public port. The desktop and web clients attach to that state. Closing the client does not end the session. The harness list on that page is Codex, Claude Code, Grok, OpenCode, Cursor, or Pi. Files and credentials stay on the machine. During pairing, credential copy is limited to Claude Code or Codex, from an online machine owned by the same user. The implemented mobile clients show attention, issues, sessions, and terminals. The same page says the reviewed sources do not confirm a supported native iPhone release, and that the /mobile web build is an unsupported compatibility path.
The delegate guide picks a placement before the agent starts. Review or research stays as another session on the same issue, and the example prompt tells that session to work read-only. Required implementation is a child issue. podium issue create --start creates the worktree and the agent, and the guide says not to spawn again for that child. Work that can ship later is a top-level issue related as discovered-from. Coordination mail is addressed to an issue, with podium mail send in the guide. Podium does not serialize two agents editing one worktree. An advisory lease from podium lock acquire expires and does not enforce access. Merges use podium merge-lock. The README shows the same issues on a board and in a team view, with a coordinator, running tasks, and tasks blocked by other tasks.
From the source
What the public materials show
Builder web analytics
Measure outcomes from Podium-run agent work
Podium keeps agent work on shared issues and worktrees. Separately configured product analytics can show the observed user-facing results of a change a person ships after that work.
This is an optional measurement workflow, not a native Podium integration with Agent Analytics. Configure product tracking and authorized analytics access separately; the listing does not install tracking or report Podium session activity.
First loop to measure
- Podium prepares a change and a person reviews it before it ships
- the reviewed change is deployed to a separately instrumented project
- a human or an authorized agent reads observed product outcomes
- the team uses that evidence to choose the next task
How to install Agent Analytics on Podium
If product tracking and analytics access are already configured, inspect the deployed change over an appropriate observation window. Report measured outcomes, missing evidence and limitations. Do not infer causation from before-and-after movement or treat Podium session activity as product usage.