Inter-office memo
- To
- Everyone who codes with an agent on a team
- From
- Mo, Chief Executive
- Date
- November 14, 2026, 1:42 PM CST
- Re
- Sharing Claude Code and Codex sessions
How to share a Claude Code or Codex session with a teammate in 2026: 9 ways compared
Claude Code’s share links and Codex’s snapshots come with your plan, but they’re read-only and don’t update. To work in one session together, Enjoy shares your computer’s conversations for every lab’s agent, and VS Code Live Share and the open-source claude-duet do it free in a terminal. On Claude Team or Enterprise, Claude Tag lets a Slack channel hand work to one @Claude.
Disclosure: Enjoy is our product. We checked every way below against its maker’s own pages on November 14, 2026, and we say where another way is the better pick, including the free ones that don’t need Enjoy.
The ways to share a Claude Code or Codex session, compared
Start with what your teammate needs. To see a session, the agent’s own share is free and enough: Claude Code has share links for cloud sessions, and Codex has read-only snapshots. To work in the same session, typing to the same agent while it runs, you need a way that shares where the agent runs: your terminal, your screen or your computer.
| Way | Best for | Price, checked November 14, 2026 | Can your teammate type? | Agents |
|---|---|---|---|---|
| Claude Code’s share links | Showing a teammate a cloud session | Included in Claude Pro ($20 a month), Max ($100), Ultra ($200), Team ($25 a seat) and Enterprise | No: a view that doesn’t update as it runs | Claude Code |
| Claude Tag, in Slack | A team handing work to one @Claude in a channel | Team and Enterprise; billed by usage to the organization, with no seat charge | Yes: anyone in the channel can tag it | Claude |
| Codex’s shared snapshots | Showing a teammate a Codex thread | Every Codex plan, from Free; Plus is $20 a month | No: a read-only snapshot | Codex |
| Enjoy | Teammates working in your conversations, live, with any lab’s agent | A monthly subscription for you and each teammate, free for 7 days (pricing) | Yes, or view only, project by project | Claude Code, Codex, Grok Build, Antigravity, Muse Code, OpenCode |
| VS Code Live Share, or tmux | A shared terminal for any command-line agent | Free | Yes, in a read/write terminal | Anything that runs in a terminal |
| claude-duet | Two people prompting one Claude Code, free | Free and open source | Yes, with the host approving each prompt by default | Claude Code |
| Tuple | Pairing on anything on screen, the desktop apps included | $30 a user a month, after a 14-day trial | Yes, by remote control | Anything on your screen |
| Cursor’s cloud agents | Teams already paying for Cursor | Teams from $30 a user a month | Follow-ups, if an admin turns them on | Cursor’s agent |
| Push the branch and export the transcript | Handing work on, not sharing it live | Free | They continue in a session of their own | Claude Code, Codex |
Prices are per month as each maker lists them, before tax. Every way except Claude Tag and Cursor’s runs your agents on your own AI plans, which their makers bill for separately.
Why a session has one driver
A Claude Code session or a Codex thread belongs to the account that started it, on the computer or cloud machine running it. A request on Claude Code’s GitHub, with 37 upvotes, puts it plainly: “There is currently no way for two different user accounts to share and collaborate on a single Claude Code session in real time.” A post on OpenAI’s forum says the same of Codex: “Codex sessions are generally operated by one developer at a time,” and developers “must share their screen or manually copy Codex prompts” to bring a teammate in.
So the ways split three ways: the agents’ own shares, which show a session; tools that share the place a session runs, so two people can type to it; and handoffs, which pass the work on.
Claude Code’s share links
Best for: showing a teammate what a Claude Code session did, from the plan you already have.
Sessions you run in the cloud, at claude.ai/code, can be shared: “toggle its visibility according to the account types below. After that, share the session link as-is.” On a Team or Enterprise account, the choices are Private and Team, and Team “makes the session visible to other members of your claude.ai organization,” and by default it checks each recipient’s repository access against their connected GitHub account. On Pro, Max and Ultra, the choices are Private and Public, which “makes the session visible to any user logged into claude.ai.”
Price: cloud sessions are “available on Pro, Max, Ultra, and Team plans, and for Enterprise users with premium seats or Chat + Claude Code seats.” Claude’s pricing has Pro at $20 a month, or $17 billed yearly, Max at $100, Ultra at $200, and Team at $25 a seat a month, or $20 billed yearly, for two seats or more.
Watch for: it’s a look, not a turn: “Recipients see the latest state when they open the link, but their view doesn’t update in real time.” Your teammate can’t pull it into a terminal either, since teleporting a session needs “the same claude.ai account used in the cloud session.” And on a personal plan, “Sessions may contain code and credentials from private GitHub repositories,” so check before you make one public.
Claude Tag, in Slack
Best for: a team on Claude Team or Enterprise that works in Slack and wants to hand work to one Claude together.
Claude Tag puts Claude in your channels: “Anyone in a Slack channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.” Slack users “don’t each need a Claude seat to work with Claude in channels.”
On Pro, Max and Ultra, the earlier Claude Code in Slack is the nearest thing. It starts a cloud session from an @mention, and Anthropic suggests it when “you’re collaborating with teammates who need visibility,” but “Each session runs under an individual user’s account.”
Price: “Claude Tag is available on Team and Enterprise plans,” and “It isn’t available on individual plans (Free, Pro, Max, or Ultra).” It adds no seat charge: channel work “draws from a usage balance, an amount in your organization’s billing currency that an Owner funds,” under a spend limit.
Watch for: it’s a public beta, it works only in Slack, and it runs “in an ephemeral sandbox, not on your computer” that “is discarded when the conversation goes idle.” It isn’t a Claude Code session on your machine: Anthropic’s own split is “team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.”
Codex’s shared snapshots
Best for: showing a teammate a Codex thread, on a Mac.
“On all Codex plans, you can create a read-only snapshot of a local Codex thread in the ChatGPT desktop app for macOS. The snapshot doesn’t give other people access to your project or computer.” Select Share, or type /share. On a personal account, “Anyone with the link can open the snapshot”; on a workspace account, “Only authenticated members of the workspace that created the snapshot can open it.” A snapshot can include “user-visible messages, reasoning summaries, image attachments, images viewed or generated by the agent, and file changes, including paths and diffs.”
Price: Codex comes with every ChatGPT plan, from Free; OpenAI’s pricing has Go at $8 a month, Plus at $20, and Business at $25 a user a month, or $20 billed yearly.
Watch for: it’s frozen and partial. “Later messages and changes don’t update the existing snapshot,” and snapshots “don’t include the original thread’s tool calls, shell commands, or tool input or output.” “You can’t fork the original thread from a shared snapshot. You can import the snapshot as an attachment and refer to it in a new thread.” The docs describe it only in the Mac app.
Enjoy
Best for: teammates working in your conversations as they happen, with any lab’s agent, from their own computer, browser or iPhone.
Enjoy runs Claude Code, Codex, Grok Build, Antigravity, Muse Code, and local models through OpenCode, on Mac, Windows and Linux. Invite a team member and pick the projects they get: Can work lets them “start conversations and make changes,” and View only lets them “read conversations and files.” “Sharing doesn’t copy your projects anywhere. Your teammate connects to your computer from their own device, and everything they do runs there.”
In a shared project, you both see the same conversations as they run. “Faces beside a shared project show who has access and who’s online. Messages show who sent them, and agent replies show who they were for,” as How sharing your computer works puts it. Your teammate can answer an agent’s questions and send the next message while you watch, or the other way round.
Price: Enjoy is one monthly subscription, and the first seven days are free, with a card to start. Inviting team members is part of it, and “Each teammate needs their own subscription too, on their own account.” See pricing.
Watch for: everything runs on your computer, so “Your computer must be on, online, and running Enjoy for anyone to join,” and while it’s off, “nothing can run.” Your teammate’s conversations “use the agents installed on your computer and the AI accounts signed in there,” so they count against your plan’s limits; see below for what the terms say. Teammates “cannot approve these requests, broaden agent permissions, or create projects on your computer,” so an agent that asks permission waits for you. Enjoy isn’t open source, and it’s a monthly subscription for each of you on top of your AI plans once the free week ends.
VS Code Live Share, or tmux
Best for: sharing the terminal Claude Code or Codex runs in, free.
Live Share, Microsoft’s free extension for “Real-time collaborative development from the comfort of your favorite tools,” has more than 24 million installs. In a session, the host can share a terminal, and “The shared terminal can be read-only or fully collaborative.” Start claude or codex in a read/write terminal, and you both type to the same agent.
Without an editor, tmux does it over SSH: “A session may be attached to one or more clients,” its docs say, so a teammate who can sign in to your machine over SSH can attach to the session your agent runs in. tmate, which used to make that one command, no longer does: “The public tmate servers (ssh.tmate.io) were shut down in July 2025, so tmate no longer works out of the box.”
Price: free.
Watch for: you share a whole terminal, not just the agent. Microsoft warns that “read/write access gives guests the same access to your terminal that you have. They can run any command on your computer that you can,” and the same goes for a tmux session. It works only for agents that run in a terminal, not the Claude or ChatGPT desktop apps, and you both type into one prompt.
claude-duet
Best for: two people prompting the same Claude Code, with the host in control, free.
claude-duet, an open-source tool under the MIT license and no relation to Anthropic’s Claude Duet app, says: “Share your Claude Code session with a friend — real-time collaboration for AI pair programming.” You chat with each other, and either of you sends a prompt to Claude with @claude. “Claude runs on your machine,” and by default your partner connects “directly peer-to-peer via WebRTC. No server needed,” with end-to-end encryption. “Approval mode is on by default so you review every prompt.”
Price: free; it needs Node.js 18 or later and the Claude Code command line.
Watch for: its README says “Heads up: claude-duet gives your partner the ability to run prompts on your machine through Claude Code,” and to “only share sessions with people you trust.” It’s Claude Code only, and it’s a community project, not Anthropic’s.
Tuple
Best for: pairing on anything on your screen, including the Claude and ChatGPT desktop apps.
Tuple calls itself “Screen sharing for people who build software,” with “Snappy remote control combined with clear audio and video.” A teammate with the app can take remote control of your screen, so they can type into whatever agent you have open. “The Tuple app runs on macOS and Windows, and Linux is in alpha. Anyone can also join a call from their browser.”
Price: $30 a user a month on Standard, with a 14-day free trial; Enterprise is priced on request.
Watch for: guests in a browser can watch, but “To share their own screen, take remote control, or draw on screen, they need the app.” It’s a call, so the session is only shared while you’re both on it, and it costs per person.
Cursor’s cloud agents
Best for: teams that already pay for Cursor and want a teammate to pick up an agent’s work.
Cursor’s cloud agents “are visible to members of the Cursor team they were started under.” “Viewing is read-only,” but “To let teammates send follow-up messages and continue the work, a team admin can enable team follow-ups.”
Price: “You need a plan that includes Cloud Agents: Premium and higher, Teams, Enterprise, or a legacy paid plan.” Cursor’s pricing has Premium at $30 a month and Teams from $30 a user a month.
Watch for: it’s Cursor’s own agent, not Claude Code or Codex, and it bills to Cursor: “Cloud Agents use your plan’s usage like other agent work.” “Team membership alone doesn’t grant access”: Cursor “verifies each viewer’s repository access.”
Push the branch and export the transcript
Best for: handing a task to a teammate who’ll carry on with their own agent, at no cost.
Commit and push your branch, then pass on what the agent knew. In Claude Code, /export will “Export the current conversation as plain text. With a filename, writes directly to that file.” In Codex, a shared snapshot does the same job: your teammate can “import the snapshot as an attachment and refer to it in a new thread.” They check out the branch, start a session of their own, and give it the transcript.
Price: free.
Watch for: it’s a copy, not the session. Your teammate’s agent starts fresh with the transcript as context, and nothing you do afterward reaches them.
Whose account does the work
Enjoy, Live Share, tmux, claude-duet and Tuple all run the agent under the host’s account. In Enjoy, teammates use “the AI accounts signed in” on your computer; claude-duet says “Claude runs on your machine”; Live Share, tmux and Tuple share your own terminal or screen. Their work counts against your plan’s limits.
If that plan is a personal one, read its terms first. Anthropic’s Consumer Terms, which “govern your use of Claude.ai, Claude Pro, and other products and services that we may offer for individuals,” say “You also may not make your Account available to anyone else.” OpenAI’s Terms of Use, for “ChatGPT, DALL·E, and OpenAI’s other services for individuals,” say “You may not share your account credentials or make your account available to anyone else and are responsible for all activities that occur under your account.”
The views don’t hand anything over: Codex’s docs say a snapshot “doesn’t give other people access to your project or computer.” Claude Tag bills channel work to your organization, and Cursor’s team agents run on your team’s plan.
When the agent’s own share is enough
If your teammate only needs to see what happened, to review how a bug was found or check an agent’s reasoning, Claude Code’s share link or Codex’s snapshot is free on the plan you have, and there’s nothing for them to install. If your team is on Claude Team or Enterprise and already talks in Slack, Claude Tag lets everyone hand work to the same Claude without sharing anyone’s account.
Look further when two people need to type to the same session while it runs, when you use more than one lab’s agent, or when the session lives on your computer rather than in a cloud.
How we compared
We read Anthropic’s Claude Code and Claude Tag docs, pricing and Consumer Terms, OpenAI’s Codex docs, pricing and Terms of Use, and Cursor’s, Microsoft’s, tmux’s, tmate’s, claude-duet’s and Tuple’s own pages on November 14, 2026, and every one is linked below. We quote each maker’s own words for its limits and leave out what it hasn’t documented. These apps change weekly, so we recheck this guide against its sources at least once a month, and the date at the foot of the page says when we last did.
15.Questions.
Can two people use the same Claude Code session?
- Not with Claude Code alone. Its share links are read-only views of cloud sessions, and Remote Control is for picking up your own session on another device. To prompt one session together, share the terminal it runs in with VS Code Live Share or tmux, use the open-source claude-duet, or invite your teammate into your conversations in Enjoy.
Can I share a Codex thread with a teammate?
- Yes, as a read-only snapshot. On all Codex plans, the ChatGPT desktop app for macOS can share one, and on a workspace account only members of your workspace can open it. Your teammate can’t fork your thread from it, but can import it as an attachment in a new thread of their own.
Does a shared session update as the agent works?
- Not with share links or snapshots. Claude Code’s docs say recipients “see the latest state when they open the link, but their view doesn’t update in real time,” and a Codex snapshot isn’t updated by later messages. Enjoy, Live Share, claude-duet, Tuple and a Claude Tag thread show the work as it happens.
Whose usage does a shared session use?
- Usually the host’s. Enjoy runs teammates’ conversations on the agents and AI accounts signed in on your computer, and Live Share, tmux, claude-duet and Tuple share your own terminal or screen. Claude Tag bills channel work to your organization’s usage balance instead.
Is there a free way?
- Yes. Claude Code’s share links and Codex’s snapshots come with your plan, and VS Code Live Share, tmux, claude-duet, Git and Claude Code’s /export cost nothing. Enjoy is a monthly subscription for you and for each teammate, free for seven days, and Tuple is $30 a user a month.