Compare

How to share Codex sessions with your team

Five ways to let a teammate read, join or continue a Codex session, and what each one gives up.

By Eimen, founder of Leverage Computer · Last reviewed · 10 min read

The short answer

  • To show a teammate a finished thread: share a read-only snapshot from the ChatGPT desktop app on macOS. On a workspace account, only members of your workspace can open it1.
  • For a session in the Codex CLI: /export saves it as Markdown, or /app moves it to the desktop app3.
  • For a searchable record of sessions: Lore turns a Codex session into a link with transcript, summary and files touched6.
  • To let a teammate's Codex read and message your task: Shuttle, a Mac app with a self-hostable relay7.
  • If your team works in each other's Codex sessions every day: Leverage Computer. Sessions are shared live in team threads, and anyone can pick one up later on the same machine and files8, 9.

Four ways to share a Codex session

A snapshot linkFrom the desktop app on macOS. Read-only, and later turns do not update it1.
An export/export writes the whole conversation as Markdown3.
A shared queueShuttle lets collaborators send to the owner's Codex task while the owner is online7.
A shared computerLeverage Computer: the team watches live and continues on the same machine and files8, 9.
Codex's own sharing covers reading. Working in the same session needs a tool around it.

What "sharing a session" can mean

  1. Read it. A teammate sees the prompts, replies and changes after the fact.
  2. Join it live. A teammate watches it happen and can type into it.
  3. Continue it. A teammate picks up the work later, with the same files and context.
  4. Keep it safe. Sessions can contain code and secrets, so check who can open the link.

Side by side

ReadJoin liveContinueWhere it runsCost
Codex shared snapshotMessages, reasoning summaries and diffs1No: later changes "don't update the existing snapshot"1No fork; import it as an attachment in a new thread1Your Mac; the snapshot is uploaded1All Codex plans1
/exportAs Markdown3NoPaste it into a new chatYour machineBuilt into the CLI3
LoreTranscript, summary, decisions, files touched6NoFork into a new Codex, Claude Code or Amp session6Your machineFree and Team ($20 per seat a month) plans13
ShuttleThe task's saved history7Send messages to the owner's task7In your own Codex task7Each person's Mac; the owner's must be online7Free, MIT7
Leverage ComputerYes8Yes: watch, steer, queue or stop8Yes, on the same VM and files9Its own VM per session9$0.50 per agent hour12

The options

Codex shared thread snapshots: the built-in option

Strengths

  • Open a local Codex thread in the ChatGPT desktop app for macOS, select Share, then Copy link1.
  • Added on 2026-08-20 for all Codex plans2.
  • On a workspace account, "only authenticated members of the workspace" can open the link. You can allow the whole workspace or only invited people and groups1.
  • A snapshot can include messages, reasoning summaries, images and file changes with paths and diffs1.
  • View or revoke links in ChatGPT data controls, under Shared links1.

Weaknesses

  • A snapshot is fixed: later messages and changes don't update it1.
  • It leaves out the thread's tool calls, shell commands, and tool input and output1.
  • "You can't fork the original thread from a shared snapshot"1.
  • On a personal account, "anyone with the link can open the snapshot"1. A workspace admin can turn off workspace share links1.

Price. Included on all Codex plans1.

/export in the Codex CLI: the quick way for a terminal session

Strengths

  • /export exports "the complete conversation as Markdown", to a file or the clipboard3.
  • /copy copies a response, code block or quote3.
  • /app opens the current session in the ChatGPT desktop app on macOS or Windows3.

Weaknesses

  • Text only. The teammate gets no files, tools or running state.
  • The CLI's slash command list has no /share command3.
  • /resume and /fork work on your own saved chats3. Remote connections need a host signed in to "the same account and workspace"5.

Price. Built into the Codex CLI3.

Lore: for readable links to past sessions

Strengths

  • Turns "Claude Code, Cowork, and Codex sessions into a shareable link". In Codex, run $lore:share6.
  • A teammate opens the "transcript, summary, decisions, files touched"6.
  • Threads can be private, workspace or public, and a thread can be forked into a fresh Codex session6.

Weaknesses

  • A link shows a finished record. Nobody can join the session live.
  • Its pricing page describes plans in terms of skills and does not say whether sharing is limited on Free13.

Price. Free $0; Team $20 per seat a month; Enterprise custom13.

Shuttle: for hand-offs between teammates who each use Codex

Strengths

  • Lets "authorized collaborators read a shared task's persisted history or submit feedback to its Codex queue"7.
  • Share one link, or limit it to email addresses. Access lasts 1, 7 or 30 days, or with no end7.
  • Can relay a chosen localhost service, so teammates can open a preview in a browser7.
  • MIT-licensed, with a hosted or self-hosted Relay that does not store task content7.

Weaknesses

  • An "early release for macOS" that needs an Apple Silicon Mac on macOS 15 or later7.
  • The owner's Companion "must be online for task reads, message submission, and local previews"7.
  • Each person stays in their own Codex task, not one shared session7.

Price. Free and open source (MIT)7.

Leverage Computer: for teams that work in each other's sessions every day

We make Leverage Computer. This section uses our own public pages, and it says where Leverage Computer does not fit.

In Leverage Computer, every agent session runs on its own VM in a shared workspace, where teammates can open it8, 9.

Strengths

  • Live and multiplayer. Watch a teammate's session live, steer it, queue a message or stop it8.
  • Shared like a doc. Keep a session private, share it with a space or the workspace, or invite people as viewers or collaborators8.
  • Stay in Codex. The Codex desktop app and CLI connect over SSH. Spaces show as projects and sessions as threads11.
  • Continue later. Archive a session and reopen it later with the same machine and files9.
  • Bring local work in. The CLI imports local Codex sessions10.
  • One setup for everyone. Environments hold variables and secrets, and private preview links show what an agent builds9.
  • Share what it built. Publish pages with versions, shared with people, spaces or the workspace8.

Where Leverage Computer is the wrong choice

  • You only need an occasional read-only link. Codex's shared snapshot is included on all Codex plans1, and /export is built in3.
  • Your code must stay on your own machines. Leverage Computer does not offer a self-hosted version. Shuttle keeps tasks on each person's Mac and can use a self-hosted Relay7.
  • You don't want another tool. Leverage Computer is a workspace your team works in, not a plugin for Codex.

Price. $0.50 per agent hour on a Standard machine; people are free; use your own ChatGPT plan, an API key or credits12.

Inside one Leverage Computer session

People

Watch it live

Steer or queue a message

Approve tool calls

Share as viewer or collaborator

Environment

Variables per space or session

Secrets added at the network

Values hidden from transcripts

The computer

Its own VM with sudo

Claude Code, Codex or Grok Build

Sleeps when idle

terminalbrowserfilesdisk

Git

Every turn committed

Team memory and skills

What it makes

Pull requests with Auto-fix

Private preview links

Published pages

Scheduled and event runs

One session, one computer. The marked parts matter most for this comparison.
The sessions page. Two sessions need a person first: one approval and one question. Other sessions are listed by space, above a box to start new work.
Every session in the workspace, and which ones need a person.

How to choose

  1. Occasional hand-offs? A shared snapshot from the desktop app, or /export for CLI work1, 3.
  2. A searchable record of sessions for the team? Lore6.
  3. Teammates who each work in their own Codex? Shuttle7.
  4. Several people in each other's sessions every day, with work that keeps running? Leverage Computer8, 9.

Questions

Does Codex have a share button?
Yes, in the ChatGPT desktop app for macOS. Select Share on a local Codex thread to make a read-only snapshot link1. The Codex CLI has /export for Markdown, but its command list has no /share3.
Can a teammate continue my Codex session?
Not from a snapshot. You can't fork it, but you can import it as an attachment in a new thread1. For a Codex Cloud task started in Slack, the channel reply "doesn't give every channel member access to the underlying task"4. To keep working on the same files and machine together, you need a shared environment such as Leverage Computer8, 9.
Is it safe to share a Codex thread?
Treat it like sharing code. Codex redacts known secret patterns, but OpenAI says sensitive content, including file paths, may remain1. You can revoke a link under Shared links in ChatGPT data controls1.

Sources

Checked on 15 November 2026.

  1. ChatGPT Learn, share a read-only snapshot of a Codex thread: learn.chatgpt.com/codex/use-chatgpt#share-a-read-only-snapshot-of-a-codex-thread
  2. Codex docs, changelog: learn.chatgpt.com/docs/changelog
  3. Codex docs, CLI slash commands: learn.chatgpt.com/docs/cli/slash-commands
  4. Codex docs, Slack: learn.chatgpt.com/docs/third-party/slack
  5. Codex docs, remote connections: learn.chatgpt.com/docs/remote-connections
  6. Lore, share: lore.link/share
  7. Shuttle, README: github.com/yeliex/shuttle
  8. Leverage Computer, work in the open: leverage.computer/teams/
  9. Leverage Computer, the computer underneath: leverage.computer/compute/
  10. Leverage Computer, harnesses: leverage.computer/harnesses/
  11. Leverage Computer, integrations: leverage.computer/integrations/
  12. Leverage Computer, pricing: leverage.computer/pricing/
  13. Lore, pricing: lore.link/pricing
Get started →