To replay a coding agent session, run the agent in Friday, which records every step, then open the session or send its Replay link. The person who opens it can read what the agent did from the start, and they do not need an account. Plans keep the record for 30 days on Solo and 365 on Team.
Why replay a session?
- To find out what an agent did overnight, and where it went wrong.
- To show a teammate how a feature was built, step by step.
- To review a change by reading the run behind it, not only the diff.
- To keep a record of who asked for what, and what the agent ran.
A chat transcript in one agent’s terminal ends when the terminal closes, and it stays on one machine. A replay keeps the whole run in one place that a link can open.
How do you replay one?
- Run your coding agent in a Friday session. Every step is recorded as it happens.
- Open the session to wind it back to any moment that mattered: an instruction, a change, a commit or a change of driver.
- To let someone else watch, press Share in the session header and send the Replay link.
The Replay link opens in a browser, with no account and nothing to install. It is read-only.
What is kept in the record?
Every action is logged with the person who asked for it, what the agent did, what each tool returned and when. After a run, a receipt lists the commands it really ran and whether they passed.
| Solo | Team Basic | Team Pro | |
|---|---|---|---|
| How long the record is kept | At least 30 days | At least 365 days | At least 365 days |
Older sessions are not removed automatically yet.