Blog

What your team sees

Sharing your Claude Code sessions with a team is a great idea right up to the session where you pasted a customer's data. Codecast answers with two dials, a preview before every share, and one settings page that shows the whole picture.

the codecast team6 min read

The question everyone asks on day one

A team that adopts codecast gets the thing it came for in an hour: everyone's agent sessions, in one inbox, searchable, steerable from a phone. Then somebody asks the question that decides whether the tool stays installed. Which of my sessions can they read? The honest answer has to be per folder, per team, and per session, because a laptop runs agents on the work repository, on a side project, and on a scratch folder full of pasted secrets, and those three should not share a rule.

This week we shipped that answer as one page. Open Settings, then Sync & Privacy, and you get everything that uploads from this machine and what each team can see of it:

The top of the Sync and Privacy settings page: a card offering to decide with an agent that reads folders and session titles and asks before changing anything, a Sync all folders toggle turned on, and the Sharing section explaining that everything is private until a repository is shared with a team and that a share covers all checkouts and worktrees
The Sync & Privacy page: the setup agent, the sync toggle, and the sharing rule in one sentence.

Two settings decide everything, and the page shows both. Sync is whether a folder's sessions upload at all; on this machine the Sync all folders switch is on, so every folder does, and they land private. Sharing is who can open what uploaded. On the machine that writes this blog, one folder is shared with a team, the codecast repository itself: every session in it, from December, across every checkout and worktree, because a rule covers a repository and not a path. The rest is private, which is the default for a new folder and the state you get without doing anything.

Two dials, not one

The folder rule says which sessions a team may see. A second dial, set per team, says how much of them. It is a dropdown on the team's header, with four levels:

  • Full access. Teammates can read your full sessions.
  • Summary. Teammates see titles and short summaries: what you worked on and how it went, not the conversation itself.
  • Activity only. Teammates see workspace names and session counts. Like a status light.
  • Hidden. Teammates see none of your work. You still see what they share.

The middle two are the ones a new team wants and most tools do not have. Activity is the office you can see across: your teammates know you are working and in which repository, and nothing else. Summary is the standup without the meeting: what each session was about, one line, and the transcript stays yours. A team can start at summary on its first day and move to full when it trusts the record. Raising the level asks which sessions it covers, Only new sessions or All sessions, past and future, so nobody widens the past by accident.

Here are both dials together, further down the same page: the team's level on the group header, and the repository's rule on the row beneath it, with the count and date span of what that rule exposes:

The Codecast team group on the Sync and Privacy settings page: 8 teammates, 1 shared, teammates see the whole conversation and can open 11,305 sessions from Dec 9, 2025 to today with 2 sessions hidden by hand, a Full level dropdown, and beneath it the codecast repository row with its own Codecast team dropdown, a sync toggle, and links to view as the team and review
One team, one repository. The header carries the team's level; the row carries the folder's rule and what it exposes.

See before you share

The count on that row is the part that matters. A share is a decision about thousands of transcripts you did not reread, so the page tells you what a share would expose before it does anything. Click a folder's sharing control, pick a team, and before anything changes a band spells it out: which team, how many teammates, what level they will see, how many sessions, and the dates they span. Here it is for a private folder on this machine, picked and then cancelled: nineteen sessions from Aug 26 on, and one that stays hidden because it was hidden by hand.

The share preview on the Sync and Privacy page: Codecast (4 teammates) will see the whole conversation for platform; 19 sessions, Aug 26 to today, 1 session hidden by hand stays hidden; the choices Everything, past sessions included, From today on, and Since a date; and below it a list headed Untick a session to keep it private
The preview a share shows before you confirm it. Nothing changes until you press the share button.

Under it are the choices that make a share fit: Everything, past sessions included, From today on, or Since a date, so the past can stay private while the future is shared. Below those is the folder's session list, where you untick any session to keep it private. Only then does the button, which names the team (Share with Codecast), do anything. The same preview prints in a terminal with cast sharing share <folder> --dry-run, for scripts and for agents.

Down to the session

Rules are about folders, and the exceptions are about sessions. Inside a shared repository, any single session can be held back, whatever the folder's rule says: the Share button in a session's header opens a popover where What the team sees goes from Full down to Summary or Hidden for that one session. On this machine a session titled Codecast sharing setup is kept private, in a repository whose rule shares the other eleven thousand. That is the shape of the thing: a wide rule, and exact exceptions.

There is one more choice for folders that must never be shared, whatever anyone does later: Never share, next to Only me and the team names on the folder's sharing control. A folder set that way is listed as locked by you, and no rule from any checkout of the repository can share it until you unlock it yourself. It is the setting for client work.

Or let an agent decide with you

The settings page opens with an offer, the Decide with an agent card at the top of the screenshot above. An agent will read your folder names and session titles, recommend what should sync and what each team should see, and ask before it changes anything. The conversation it has with you stays private, which is the only acceptable property for a conversation about what to keep private.

So the first team day goes like this: install, everything uploads private, share the work repository with the team at the level the team is ready for, keep the odd session out by name, and lock the folder that should never travel. Then your teammates see your sessions, and only the ones you meant.

Codecast is where your team sees, steers, and remembers every coding agent session — any agent, any machine.

The counts, dates and the kept-private session are from the author's machine on 2026-09-24, read from the Sync & Privacy page and the matching cast sharing output; nothing shown changed a setting. All three screenshots are the Sync & Privacy settings page in the codecast web app, cropped to the page header, to one team's group, and to the share preview; the other teams' groups and the private folder rows are outside the crops. The preview was opened on a private folder and cancelled.

Taking longer than usualOffline · reloads when back