A Claude Code session is waiting on you...
Official homepage and documentation: podium.engelking.dev
Run a few sessions at once and it happens fast. One is stopped at a permission prompt. One has filled its
context window. A subagent failed ten minutes ago and nothing told you. The only way to find out is to
click through every terminal, and that takes more effort than the work itself.
Podium is a single pane of glass for Claude Code. Whether it's just you or your whole team, every session
shows up in one browser tab, so you can see what all of them are doing at a glance. Each session appears
within about two seconds of its first prompt and leaves when it ends, with no refresh.
There are other tools like this. Podium started as something I built for myself, because I run several
Claude Code sessions at once and was tired of clicking through terminals to find the one that needed me. It
turned out to be useful enough to share. I haven't compared it with every similar tool, so if another one fits
how you work better, use that one. If you try Podium and something is missing, I'd like to hear about it.
For every session you see:
- its model, effort and plan, and the git branch or worktree it works in
- the agents it launched (subagents and forks), and what each one costs
- how full each context window is, and how often one blew out
- why anything failed
Podium watches. The one thing it can send is an answer to a session that waits on you (a question, a plan,
a tool's permission prompt, a message, /clear or /compact), and only once the server's Admin and the
session's owner have both turned that on. It never types into a terminal.
Run it for yourself on one machine, or point a whole team's sessions at one server and the console groups
the wall by person. The Claude Code mod, podium-reporter, sends the data.
New here? The user guide walks through setup and reading the console, and the
documentation table below lists everything else.
Cost in Podium is an estimate from token counts and a price table. The table starts as Anthropic's list
prices and you can change any price in Admin > Model prices. It is never a bill.
Quick start
Requires Node 24 and npm.
npm install
npm run dev # server on http://127.0.0.1:4317, Vite UI on http://localhost:5173
Open http://localhost:5173/#/. With nothing reporting yet, the wall says how to start a session.
To see it with simulated sessions instead of real ones, in a second terminal:
npm run podium:sim -- --sessions 5 --chaos
--chaos adds sessions that go silent, more failures and more context blowouts. --help lists the
other options (--url, --speed, --seed, --duration, --agents, --token, --person, --unnamed, --print). Stop it
with Ctrl-C; it ends every session it started, and they leave the console a few seconds later. If the
server has a token (podiumctl start sets one), pass it: --token "$(podiumctl token)".
To see the people view, give the simulator people with a token each from Admin:
--person "Ed E.=<Ed's token>" --person "Priya N.=<Priya's token>" --unnamed. Sessions go to the people in
turn, each on a laptop and every third one on a build box; --unnamed keeps a share of sessions with no name,
which show under Admin when they send the admin secret with --token.
To serve the built UI and the API without a container, npm run build and then npm run start -w server
(http://127.0.0.1:4317). To run it as a managed service, see Running the server.
Documentation
podium.engelking.dev is the official homepage and documentation site for Podium, with a menu, search and a version picker. The files below are the same ones, and they read fine on GitHub too.
| Read | To |
|---|
| Introduction | What Podium is, what it does and does not do, and where to read next |
| User guide | Set Podium up, read the console and use Admin |
| Running the server | Run it with podiumctl, let a team report to one server, put it behind a reverse proxy or turn on built-in TLS, and change its settings |
| The reporter mod | Install podium-reporter, set its options and see what leaves a session |
| Orchestrator messaging | Let your own orchestrators on different machines message each other through Podium: setup, rights, limits, Traffic, troubleshooting and an end-to-end test |
| Session recording and replay | Record a session whole and play it back: the three yes answers, what is and is not captured, the notice, retention, limits and who can read it |
| Gotchas | Sharp edges that are easy to hit, including why one machine shows several rows on the Reporters page |
|
Community
Questions, show-and-tell and release news live in the Podium Discord server. The
Code of conduct applies there. Bugs and feature requests go in
GitHub Issues, and a security problem never goes in Discord: report it
privately as described in the security policy. How to join and
how the server is run is in Community.
Podium is released under the MIT License.
