How to share a Claude Code session with your team
You can share a Claude Code session as a read-only link, or run it in a shared session that teammates join, watch and steer live. A link shows what happened. A shared session lets people take part while it happens.
Can you share a live Claude Code session?
Not with Claude Code on its own. Its share links give a read-only view of the conversation. Teammates can read it, but they cannot type into it or steer the agent. Developers have asked for live, multi-user sessions in a request on the Claude Code repository.
That is fine when you only need to show someone what happened. It is not enough when a teammate needs to help.
What are the ways to share a session?
| Method | What teammates get | Good for |
|---|---|---|
| Share link | A read-only copy of the conversation | Showing what happened |
| Exported transcript | A static file, with the live context gone | Handoff notes |
| Screen share or tmux | A live view, with one person in control | A quick look together, when everyone is online |
| Shared session in Friday | A live session they can join, watch and steer | Working on the same task together |
How do you share a Claude Code session in Friday?
Friday runs your own Claude Code on your machine and opens the session to your team.
- Friday links your machine for you and finds Claude Code, Codex and Cursor on your computer.
- Continue your session. Pick the Claude Code session you were already in from the list.
- Invite your team. Share the session by link as an editor or a viewer.
- Steer together. Teammates watch each step, suggest changes, or ask to take control.
The agent works in the folder you choose, in the mode you choose: plan only, edit files, or edit files and run commands. It runs on your own account, and Friday never meters it.
What can teammates do in a live session?
- Watch every step as it happens, including tool calls and file changes.
- Suggest a redirect. The agent picks it up at its next step.
- Request control, or take over where the session allows it.
- Interrupt a run without restarting it.
- Read what happened before they joined, and catch up from a short digest.
When is a read-only link enough?
If you only want a record, such as a bug report, a code review note or an example for a teammate, a share link or an exported transcript is simpler. Use a shared session when more than one person needs to act.
Common questions
Does this work with Codex and Cursor?
Yes. Friday finds Claude Code, Codex and Cursor on your machine, and you can run them in the same session.
Does it cost extra?
Your own Claude Code runs on your account and is never metered by Friday. The Free plan allows 3 people in a session, Pro allows 10, and Max has no limit.
Who can read the session?
Anyone who can open it can read all of it, including earlier messages. Editors can steer. Viewers can only read.