# 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 15 November 2026.

Disclosure: We make Leverage Computer, one of the tools on this page. We describe every product, ours included, from its own public pages, and each fact links to its source. Prices change: check the linked page before you buy. Found something wrong or out of date? Email [founders@leverage.computer](mailto:founders@leverage.computer) and we will fix it.

## 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 it [1].
- **For a session in the Codex CLI:** `/export` saves it as Markdown, or `/app` moves it to the desktop app [3].
- **For a searchable record of sessions:** Lore turns a Codex session into a link with transcript, summary and files touched [6].
- **To let a teammate's Codex read and message your task:** Shuttle, a Mac app with a self-hostable relay [7].
- **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 files [8][9].

**Figure: Four ways to share a Codex session.** Codex's own sharing covers reading. Working in the same session needs a tool around it.

- A snapshot link: From the desktop app on macOS. Read-only, and later turns do not update it [1].
- An export: `/export` writes the whole conversation as Markdown [3].
- A shared queue: Shuttle lets collaborators send to the owner's Codex task while the owner is online [7].
- A shared computer: Leverage Computer: the team watches live and continues on the same machine and files [8][9].

## 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

|  | Read | Join live | Continue | Where it runs | Cost |
| --- | --- | --- | --- | --- | --- |
| Codex shared snapshot | Messages, reasoning summaries and diffs [1] | No: later changes "don't update the existing snapshot" [1] | No fork; import it as an attachment in a new thread [1] | Your Mac; the snapshot is uploaded [1] | All Codex plans [1] |
| `/export` | As Markdown [3] | No | Paste it into a new chat | Your machine | Built into the CLI [3] |
| Lore | Transcript, summary, decisions, files touched [6] | No | Fork into a new Codex, Claude Code or Amp session [6] | Your machine | Free and Team ($20 per seat a month) plans [13] |
| Shuttle | The task's saved history [7] | Send messages to the owner's task [7] | In your own Codex task [7] | Each person's Mac; the owner's must be online [7] | Free, MIT [7] |
| Leverage Computer | Yes [8] | Yes: watch, steer, queue or stop [8] | Yes, on the same VM and files [9] | Its own VM per session [9] | $0.50 per agent hour [12] |

## 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 link [1].
- Added on 2026-08-20 for all Codex plans [2].
- 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 groups [1].
- A snapshot can include messages, reasoning summaries, images and file changes with paths and diffs [1].
- View or revoke links in ChatGPT data controls, under Shared links [1].

**Weaknesses**

- A snapshot is fixed: later messages and changes don't update it [1].
- It leaves out the thread's tool calls, shell commands, and tool input and output [1].
- "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 links [1].

**Price.** Included on all Codex plans [1].

### /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 clipboard [3].
- `/copy` copies a response, code block or quote [3].
- `/app` opens the current session in the ChatGPT desktop app on macOS or Windows [3].

**Weaknesses**

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

**Price.** Built into the Codex CLI [3].

### Lore: for readable links to past sessions

**Strengths**

- Turns "Claude Code, Cowork, and Codex sessions into a shareable link". In Codex, run `$lore:share` [6].
- 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 session [6].

**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 Free [13].

**Price.** Free $0; Team $20 per seat a month; Enterprise custom [13].

### 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 end [7].
- Can relay a chosen localhost service, so teammates can open a preview in a browser [7].
- MIT-licensed, with a hosted or self-hosted Relay that does not store task content [7].

**Weaknesses**

- An "early release for macOS" that needs an Apple Silicon Mac on macOS 15 or later [7].
- 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 session [7].

**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 it [8][9].

**Strengths**

- **Live and multiplayer.** Watch a teammate's session live, steer it, queue a message or stop it [8].
- **Shared like a doc.** Keep a session private, share it with a space or the workspace, or invite people as viewers or collaborators [8].
- **Stay in Codex.** The Codex desktop app and CLI connect over SSH. Spaces show as projects and sessions as threads [11].
- **Continue later.** Archive a session and reopen it later with the same machine and files [9].
- **Bring local work in.** The CLI imports local Codex sessions [10].
- **One setup for everyone.** Environments hold variables and secrets, and private preview links show what an agent builds [9].
- **Share what it built.** Publish pages with versions, shared with people, spaces or the workspace [8].

**Where Leverage Computer is the wrong choice**

- **You only need an occasional read-only link.** Codex's shared snapshot is included on all Codex plans [1], and `/export` is built in [3].
- **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 Relay [7].
- **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 credits [12].

## How to choose

1. **Occasional hand-offs?** A shared snapshot from the desktop app, or `/export` for CLI work [1][3].
2. **A searchable record of sessions for the team?** Lore [6].
3. **Teammates who each work in their own Codex?** Shuttle [7].
4. **Several people in each other's sessions every day, with work that keeps running?** Leverage Computer [8][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 link [1]. The Codex CLI has `/export` for Markdown, but its command list has no `/share` [3].

**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 thread [1]. 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 Computer [8][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 remain [1]. You can revoke a link under Shared links in ChatGPT data controls [1].

## Sources

Checked on 15 November 2026.

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

[Get started](https://app.leverage.computer/login?mode=signup&utm_source=leverage.computer&utm_medium=markdown&utm_content=/compare/share-codex-sessions/)

## More

- [How to share Claude Code sessions with your team](https://leverage.computer/compare/share-claude-code-sessions/)
- [Codex for teams: your options compared](https://leverage.computer/compare/codex-for-teams/)
- [AI agent workspaces for engineering teams, compared](https://leverage.computer/compare/ai-agent-workspaces-for-engineering-teams/)
- [Work in the open: shared sessions](https://leverage.computer/teams/)
- [Leverage in your coding agent](https://leverage.computer/integrations/)
- [Pricing](https://leverage.computer/pricing/)
- [All comparisons](https://leverage.computer/compare/)