Codex keeps your session on your own computer, so a teammate cannot join it. To share one, link your computer to Friday, continue your Codex session there, and send your teammate a link. They watch each step in a browser without signing up. A teammate who signs in as an editor can also suggest redirects and take control when it is their turn. Your Codex stays on your own plan.
Can you share a Codex session?
Codex is built around one person working with one agent. The usual ways to show a teammate what it did are a screen share, a pasted transcript, or a branch and pull request. Each gives them a view of the result, but the teammate cannot act inside your session. OpenAI’s documentation describes sharing plugins and environments with a workspace, not a running thread. We found nothing in Codex’s documentation that lets a second person join one live, so check OpenAI’s docs for anything newer.
The common failure is the paste. A teammate who starts a fresh Codex session from your notes re-reads the same files and retries what you already ruled out.
How do you share a Codex session in Friday?
Friday runs your own Codex on your computer and opens the session to your team.
- Link your computer to Friday with one command, or let the desktop app do it. Friday finds Codex, Claude Code and Cursor on your machine.
- Pick the Codex session you already have and continue it in the same folder, so Codex resumes with its own context and Friday shares its latest messages with the session.
- Choose what Codex may do: plan only, ask before each command, or run on its own (Plan, Manual and Auto).
- Press Share in the session header and send the Watch live link. A viewer opens it in a browser with no account and no install. Send an editor link to someone who should steer.
- Steer together. An editor suggests a redirect, the driver sends it to Codex, and anyone who can edit can ask for control.
Codex runs under your own login and plan, and Friday never meters it. Your teammates do not need Codex at all unless they want to drive an agent from their own computer. See how to continue a session with your team for the import step in detail.
What can your teammate do once they are in?
| Link type | What the teammate can do | Plan needed |
|---|
| Viewer | Read every step, including earlier messages and file changes, with no account | Free on every plan |
|---|
| Editor | Sign in, then read, suggest redirects, ask for control, upload files | Team, from $15 a seat a month |
|---|
The person driving Codex sees a teammate’s suggestion and decides whether to send it. When the driver is away, a teammate can take over and carry on with the whole session in front of them. Late joiners get a short digest of what changed while they were gone.
What does sharing Codex add beyond a link?
- Hand-off between tools. Move the task from Codex to Claude Code or Cursor with the whole record, or to a teammate.
- Automatic hand-off at a limit. When a coding tool stops because it ran out of usage, Friday hands the task to another agent that can take it; if none can, it resumes when the limit resets or asks a person.
- Smart routing. In Codex, Auto can pick the model for each message.
- A record. Every step is kept, and anyone with access can replay it.
For a measured look at what a hand-off saves, see the hand-off benchmark, which includes its limits.
What should you know before you share?
Your Codex keeps running on the computer you linked, so that computer has to stay on while it works. Friday stores the session record so that your team can read it, and anyone who can open the session can read all of it, earlier messages included. Treat the link as carefully as the work. The security page lists what is stored and what is not finished yet.
Solo is free for one person, and anyone can watch for free. Teammates who steer with you need Team, with Team Basic at $15 a seat a month and a 7-day Team Basic trial for a new team, starting when a teammate who can edit first joins or you invite one to edit, or when you first run Friday’s agent.