Documentation
Working together

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.

3 min read

"Share this session" can mean three things. You want a teammate to read a conversation that already finished. You want someone to follow one that is still running. Or you want the team's sessions visible without anyone deciding to share each one. Codecast does all three, and each starts from the session itself.

The Share session popover: Link access set to Restricted or Anyone, with Copy link and Send to chat
The share button in a conversation's header. For a session in a team workspace, a What the team sees section sits above Link access.

Share a session with your team

Open the session and click the share button at the right of its header. In a team workspace, What the team sees has three settings:

  • Hidden: only you can see it, and it stays out of the team feed.
  • Summary: the team feed shows the title and a summary of the work, not the conversation.
  • Full: the team can read the whole conversation, live while it runs.

If the session lives in a repository you already share, the popover says so (Shared automatically) and links to the repository's setting. To share every new session with a team without doing it one by one, use Share all new sessions in full, or set it per repository in Settings → Sync & Privacy (Team sessions covers that).

Share a link

Under Link access:

  • Restricted: only people who can already see the session can open the link. Use it to point a teammate at a session.
  • Anyone: anyone with the link can read it, no sign in needed. The share button turns into a globe so you can tell at a glance that the session is public.

Then click Copy link, or Send to chat to post it in a team chat channel. Someone who opens a public link sees the conversation read only, with no composer, and a Sign in button if they have an account.

Before you make a session public, read it for anything private: tokens, customer names, internal links. Agents print what they see.

Share a few messages

Often one answer is the part worth sending. Hover a message and use Copy link to message, or click Share message to pick several: tick the messages you want, then Copy share link or Send to chat. Tick Link full conversation if the reader should be able to open the whole thing (this makes the conversation public).

Whoever opens the link sees just those messages, who shared them and when, and the session's title, with View full conversation when you linked it.

Watch a session while it runs

A session you can see in codecast is live: new messages, commands and file changes appear as the agent writes them, on the web, in the Mac app and on your iPhone. So "watch this" is the same link as "read this". If the session needs input, the person who runs it can answer from any of those places.

How this compares to other tools

Three needs, four tools. Most tools answer one need well and leave the other two blank.
  • Claude Code's own sharing works for sessions that ran in the cloud at claude.ai/code. You set a session to Team or Public and send the link; the reader sees it as it was when they opened it.
  • Lore turns one conversation into a shareable thread, for Claude Code, Codex, Cowork and Amp.
  • Remote Control lets you follow and steer one running Claude Code session from claude.ai or the Claude app, while it runs.
  • Codecast records every session on every machine as it happens, for the folders you choose, and keeps them afterwards to search and link to.

They work together: a session you steer with Remote Control is still an ordinary Claude Code session on your machine, so codecast records it like any other. For more on that pairing, see Codecast vs Claude Code Remote Control.

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.
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.
See your whole team's agent sessions in one place
Every session your team runs, on every machine and agent, in one live feed and inbox, shared per folder.
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.
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 into one queue 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