Documentation
Working together

See your whole team's agent sessions in one place

Every session your team runs, on every machine and agent, in one live Activity page and inbox, shared per folder.

4 min read

Every coding agent your team runs already keeps a full record of its session on the machine that ran it: Claude Code, Codex, Cursor, OpenCode, pi, Grok and Gemini all do. Nobody else can see those records. Codecast puts the sessions in one place for the whole team, live, without anyone changing how they run their agents.

Each teammate installs Codecast once (Getting started). From then on, every session they start in a terminal, an editor, tmux or over SSH shows up in Codecast as it happens. You choose which of your folders the team can see, and everything else stays yours.

Two ways to look at the same sessions

Activity, under Team in the sidebar, is every session the team can see, newest activity first, across machines and agents. Now at the top lists who is working at this moment. Team and Mine switch between everyone's work and yours. Click teammates' faces to see only their sessions, pick a project from the project menu, or press Needs someone to see only the sessions waiting on a person. People and Projects at the right group the list by who or by repository. Each filter is part of the page's address, so a filtered view can be sent to someone.

The Activity page: Alex Rivera, Maya Ortiz and Sarah Chen's sessions on the webhook retries work, newest first, with their faces above as filters
Activity shows what the team's sessions did, filtered here to one project.

Inbox files your sessions by who has to act next:

SectionWhat is in it
DecisionsQuestions agents are waiting on you for (Decisions)
Needs YouBlocked on you: a question, a permission prompt, a finished turn to review
DoneDelivered. Read it when you have time
WorkingThe agent is still going
DormantWaiting on something scheduled, such as a test run or a reply
The inbox with sessions under Needs You, Done and Working, and one conversation open beside it
The inbox files sessions by who acts next, from every machine and every agent.

Open any session to read the whole conversation as it unfolds: messages, commands, file changes as diffs. Looking at a teammate's stuck session and helping with it happen in the same place, on the web, in the Mac app or on your phone.

The phone inbox with the team's sessions filed under Needs You and Working
The same inbox on the phone.

Choose what the team sees

Sharing is set per folder, so you decide once. Your work repository can be visible to the team while your personal experiments stay private, on the same account.

When you join a team, the What teammates see step asks which repositories you work in with that team. You can change it any time in Settings → Sync & Privacy, under Sharing:

  • Every repository and folder Codecast has seen is listed under the team it is shared with, with how many sessions it holds. The rest sit under Private — only you or Never shared — locked by you.
  • Click a repository's share control and pick Only me, a team, or Never share.
  • When you pick a team, the panel shows exactly who will see what: how many teammates, how many sessions, and over which dates. Choose whether the share covers Everything, past sessions included, starts From today on, or starts Since a date, and untick any session you want to keep private. Nothing changes until you press Share with and the team's name.
  • Never share locks a folder, so nothing in it reaches a team even if a folder around it is shared.
Sync & Privacy, Sharing: the webhooks repository shared with Acme, a scratch folder under Private — only you, and the share control open
Each repository and who it is shared with.
The share review for a repository: 2 teammates, 14 sessions, and From today on selected
The review before a share takes effect.
Five sessions on one account. The closest folder setting wins, a clone follows its repository, and anything nothing covers stays private.

Copies of a repository follow its setting, including the worktrees some agents create outside your project folder. For a single session, the share button in the conversation header sets what the team sees of it: Hidden, Summary or Full. See Share a session.

What sharing makes possible

Because every session lands in one place, the record keeps paying off after the work is done:

  • Search every past session on the team from the search box at the top of the app.
  • Ask any agent how the flaky deploy got fixed last month. It searches the team's sessions and answers with links to them (Memory).
  • Trace a line of code back to the conversation that wrote it (Which session wrote this line).

When something is off

What you noticeWhat to do
Your sessions are missing from ActivityActivity shows Your sessions are hidden from your team. Click Share workspaces and share the repositories you work in
A teammate's sessions are missingThey haven't shared that repository yet, or their computer hasn't connected. Shared sessions appear as soon as their Codecast is running
Old sessions showed up after you sharedYou picked Everything, past sessions included. Open the repository in Sync & Privacy and change it to From today on, or untick the sessions to keep private
A folder should never reach the teamSet it to Never share in Sync & Privacy
More guides
Agent features: what your agents know how to do
Switch features on for each computer, and every new session there learns to remember, delegate, track work, show results and use your machine.
Memory: agents that look up past work
Your agents search every session you can see, across your machines, agents and team, and answer with the session they found it in.
Let Claude, Cursor and Codex read your codecast
Add codecast.sh/mcp to an agent that runs outside codecast, sign in once, and it reads your docs, tasks, plans, pages and sessions as you, read only.
Search your history across every machine
Every computer you connect sends its sessions to one history, searchable from the web, the Mac app and your iPhone.
See which agent session wrote a line
Set Blame to Sessions on any file to see the session behind each line, and open the conversation where it was decided.
Messaging between sessions
Your sessions hand each other results and answers directly, so you stop relaying text between them.
Stable context: sessions that know what's been happening
New sessions start with a short list of what you and your team worked on recently, so they pick up threads instead of starting cold.
Use Codecast with T3 Code
Threads you start in T3 Code appear in Codecast with no setup, beside every session you run anywhere else, ready to search, steer and share. What you get on top, and what stays in T3 Code.
Use Codecast with OpenCode
Sessions you run in the OpenCode TUI appear in Codecast within seconds, with no plugin. Reply to them from the app, start new OpenCode sessions there, and search them beside every other agent you use.
Share a session with your team
Choose what the team sees of a session, share it by link or a few messages at a time, and how that compares to other tools.
Pinned thread state
The agent keeps one short note on each session saying where it stands, above the composer and on its inbox card.
Decisions: asking without interrupting
Agents put the calls only you can make on one Decisions page you clear when you choose to, and each answer goes back to the session that asked.
Team chat with your agents in the room
Channels, threads and DMs where you can hand a session or a role something by mentioning it, while agents stay quiet unless they're needed.
Huddles, transcripts and walkie
Every huddle is transcribed under each speaker's name and leaves a summary, so your agents can quote what was said, and a session can join the call.
Workers, forks and switching agents
Your agent can hand work to workers that report back to it, and you can fork a conversation to try two directions from the same point.
Tasks and plans
Agents file the work they take on, post progress and close it with what they verified, and you follow it on the Tasks and Plans pages.
Triggers
Agents schedule their own follow-ups, once, on a schedule or on a GitHub or Linear event, and you can set one yourself from the Triggers page.
Workflows
A fixed sequence of agent steps, checks and approval gates that runs the same way every time and waits for you where you want a say.
Orchestration
Hand an agent a whole plan and it runs a team: implementers working in parallel, a reviewer on every task and critics on the result.
Pull requests and issues
Every pull request gets a page with its checks and threads, the session that opened it fixes what reviewers and CI flag, and Linear or GitHub issues become tasks.
The org: roles that look after your work
Give lasting work to a role with an area, a charter and a standing session, and approve the changes your agents propose to the org.
Let agents use your Chrome
Agents check pages in the Chrome you already use, logins included, from their own background tabs. Screenshots and errors come back to the conversation.
Vault: keys, logins and sign-ins for your agents
Fill a credential once and every agent on every machine can use it, without the value ever entering a conversation.
Computer use: agents in your Mac apps
Agents work in Preview, Slack, System Settings or your own desktop build, in the background, with an orange pointer that shows where they act.
Typecheck: one shared check for every agent
With Typecheck on, agents on a computer share one typecheck per project, so checks answer in seconds and a busy machine stays usable.
Skills: slash commands for the jobs you repeat
Type / in a Claude Code session to pick up work, hand it over, get a second opinion or ship a pull request, the same careful way every time.
Run sessions on other machines and in the cloud
Start a session on another computer or a cloud machine in your AWS account, move it there and back, and watch it from anywhere.
Codex Cloud tasks in codecast
Bring your Codex Cloud tasks into your inbox, start new ones with several attempts, and turn the result into a pull request or local changes.
Usage limits are a pause
When a Claude plan runs out, sessions wait for the reset or continue on another account you've saved, instead of stopping for good.
The visual canvas
Agents answer with charts, comparisons and diagrams drawn right in the conversation when a picture says it better than text.
Published pages
Agents turn reports and mockups into pages with their own link that you can share, gate, and get comments on.
Why codecast feels instant, even offline
Everything you see comes from a copy on your device that the server keeps current, so screens open at once, your edits show immediately, and nothing is lost offline.
Taking longer than usualOffline · reloads when back