To watch a teammate’s coding agent live, they send you a link to their Friday session. You open it in a browser and see every step as it happens: messages, tool calls and file changes. You do not need an account, and watching is free on every plan. You can read earlier steps too, and replay the session later.
Why would you watch someone else’s agent?
- To catch a wrong turn before it costs an hour.
- To learn how a stronger engineer prompts and steers.
- To follow an engineer’s onboarding by watching real sessions.
- To see where a teammate’s work stands without asking.
- To prepare for taking the session over.
A teammate’s agent normally lives in their terminal, where nobody else can see it. Screenshots and a call only cover the moments you are both there.
How do you watch?
- The teammate runs their Claude Code, Codex or Cursor in a Friday session on their own computer.
- They press Share in the session header and send you the Watch live link. The same menu has a Replay link, and links show a preview when pasted into chat.
- You open the link in a browser. There is no account to make and nothing to install.
- You see the session as it runs, read-only. A short digest says what changed if you arrive late.
A slim bar on the page offers Try Friday free, if you want a session of your own. The desktop app for Windows and Mac is optional.
What can a viewer see and do?
| Viewer | Editor | |
|---|---|---|
| Account needed | No | Yes, sign in |
| Read every step, including tool calls and file changes | Yes | Yes |
| Read what happened before joining | Yes | Yes |
| Suggest a redirect to the driver | No | Yes |
| Ask for control of the agent | No | Yes |
| Cost | Free on every plan | Team, from $15 a seat a month |
The session owner can change what editors may do. To move from watching to steering, ask for an editor link and sign in.
Can you watch a run later?
Yes. Every session keeps a record of each step, and you can wind it back to any moment. That helps when something broke overnight, or when a new teammate wants to see how a feature was built. How long the record is kept depends on the plan: history is kept for at least 30 days on Solo and at least 365 on Team Basic. Nothing deletes older sessions automatically yet.
What should the person sharing keep in mind?
Anyone who can open the session can read all of it, including earlier messages, so treat the link as carefully as the work. The agent keeps running on the computer it was linked on, so that machine has to stay on while it works. The session record is stored by Friday so your team can read it. The security page says what is stored and what is not finished yet.
If the teammate wants your help and not just your eyes, see Claude Code collaboration, and for passing the work on, hand off a coding agent session.