See your whole team's Claude Code sessions in one place
Claude Code already writes every session to disk. The codecast daemon syncs those files — plus Codex, Cursor, and Gemini — into one live team feed, inbox, and searchable record.
Every Claude Code session your team runs already writes a complete transcript to disk — Claude Code keeps JSONL history files under ~/.claude/projects/, and Codex, Cursor, and Gemini keep equivalents of their own. The sessions are recorded; they just aren't anywhere anyone can see them. Codecast turns those files into one live dashboard for the whole team.
The mechanics
Each teammate runs the installer once:
curl -fsSL https://codecast.sh/install | sh
cast login
That starts a local daemon that watches the agents' own history files and syncs each conversation to your team's workspace as it happens — no change to how anyone runs their agents. A session started in a terminal, tmux, an IDE terminal, or over SSH is picked up the same way, because the daemon reads what the agent writes, not how it was launched.
From then on, two surfaces answer the question this page is named for:
- The feed (
codecast.sh/feed) — every team-visible session, newest first, across all machines and agents. Who is working on what, right now and historically. - The inbox (
codecast.sh/inbox) — the same sessions sorted by who acts next: working, needs input, done. A session stuck on a permission prompt surfaces at the top, and you can answer it from the web, the desktop app, or the iOS app.
Opening any session shows the full conversation live — messages, tool calls, diffs — and you can type into it from there, so "looking at a teammate's stuck session" and "unblocking it" are the same motion.
What "team-visible" means
Visibility is per directory, not all-or-nothing. Each repo path maps to a team (or stays private); a session inherits the mapping of the directory it runs in. Work in ~/src/product can be team-visible while ~/personal/experiments stays yours — same daemon, same account. Sessions can also be shared individually by link.
Beyond watching
Because every session lands in one place, the record compounds:
cast search "auth refactor"— full-text search across every past session on the team.cast ask "how did we fix the flaky deploy?"— ask questions across that history.cast blame src/api.ts:120— trace a line of code to the conversation that wrote it.- Agents themselves get the same access (see Agent memory), so a fresh session can consult what any teammate's agent already solved.
Scope of the answer
Codecast's dashboard covers Claude Code, Codex CLI, Cursor, and Gemini sessions on any machine a teammate runs the daemon on. If you need usage analytics — spend, acceptance rates, seat activity — Anthropic's own analytics dashboard (claude.ai/analytics) is the right tool; codecast is about the sessions themselves: seeing them, steering them, and remembering them.