How to continue a Claude Code or Codex session with your team
You do not have to start over to bring your team in. Friday lists the Claude Code and Codex sessions already on your machine, and you can pick one and continue it, with the memory it built, in a shared session your teammates can join.
What is Friday Work?
Friday Work is a multiplayer AI workspace for coding teams. Your people and your coding agents work in one live session: the same task, the same record, the same tools. It is a desktop app for Windows and Mac.
- Teammates join a session by link, watch every step, suggest changes and take control when it is their turn.
- Claude Code, Codex and Cursor run on your own machine and your own accounts, side by side in one session, with Friday’s own agent when you want it.
- Continue a Claude Code or Codex session you already have, instead of starting over.
- Plan, Manual or Auto: you decide what an agent may do, and approve its commands as a team.
- Connect GitHub, Slack, Linear and 50+ more tools over MCP once, and choose which agents may use them.
- Free to start. Pro is $20 a month ($18 a month billed yearly).
Why continue an existing session?
The hard part of a long agent session is the context in it: what the agent read, what it ruled out, what you agreed. Starting a new session to share it throws that away. Continuing the one you have keeps it.
How do you bring a session into Friday?
- Link your machine. Friday finds Claude Code and Codex on your computer.
- Open the list of sessions your coding agent already has and pick the one you were in.
- Friday shows the room what was said, then continues that conversation, so your next instruction lands in the session it already had.
- Invite your team by link, as editors or viewers.
- Teammates watch each step, suggest changes, or ask to take control.
Work from the session lands on a new branch named after what you asked for.
What comes with the session, and what does not?
| Item | Claude Code and Codex |
|---|---|
| The conversation and the memory the tool built | Continued, so the agent still has it |
| Where it is stored | On your machine. Friday reads the files to list them and does not copy the conversation elsewhere |
| Your agent definitions | Import from Claude Code, Cursor and Codex, as private agents you can then share |
| Cursor sessions | Not imported. Cursor’s command line keeps no transcript Friday can read, but Cursor works as a live agent in a session |
What can your team do once they are in?
- Watch every step as it happens, including tool calls and file changes.
- Suggest a redirect for the driver to send.
- Ask for control, which the driver approves or hands over, depending on the session.
- Catch up from a short digest instead of reading the whole history.
Common questions
Does importing copy my conversation to Friday?
No. Friday reads the session files on your machine to list them and resumes the session by its id. It does not copy the conversation anywhere.
Can I import a Cursor session?
Not today. Cursor keeps no transcript Friday can read. You can still add Cursor to a session as a live agent, and import its agent definitions.
Can teammates continue my session on their machine?
They join the shared session and steer it. The agent keeps running on the machine it was linked on.