Share Codex sessions as URLs your team can read

Run /share-codex inside any Codex CLI session and Lore turns the thread (prompts, tool calls, diffs) into a shareable URL. Free workspace plan.

What this integration does

Lore turns any Codex CLI session into a URL your team can open in a browser. Run /share-codex from inside the session and you get a link to the full conversation (prompts, tool calls, diffs), rendered the way it played out.

The integration is a Codex skill. No application to install, no API key to configure. If you can run a Codex skill, you can share a session.

How it works

Install the Tanagram CLI: npm install -g @tanagram/lore
Run lore once to authorize. Your sessions upload automatically from then on.
Inside any Codex session, run /share-codex. The skill exports the thread to Lore and returns a lore.tanagram.ai/session/... URL.
Paste the URL anywhere your team already collaborates: a PR description, a Slack thread, a Linear ticket. The recipient opens it in a browser and sees the conversation in full.

The CLI's background sync covers Codex too. Sessions are uploaded automatically and browseable at lore.tanagram.ai/threads.

What gets exported

The same envelope as any Lore thread:

Every prompt and assistant turn, in order.
Every tool call the model made and its result.
Every diff applied during the session.
Skill invocations, with their input and output preserved.

What doesn't get exported:

Local files outside the session.
Messages you trim before publishing.
Anything in the session if you don't run /share-codex. The export is opt-in.

Visibility

The same three modes as Claude Code threads:

Private, only you.
Workspace, teammates with the same email domain.
Public, anyone with the URL.

Visibility is changeable after publishing. Deleting the URL removes the thread.

Why share a Codex session

Codex sessions are often the artifact of a different team: data science notebooks, ML pipelines, one-off scripts. Three patterns where the thread carries more value than the resulting code:

Data exploration. A Codex thread that walks through a dataset, tries five queries, and arrives at the one that answers the question is far more useful to share than the SQL string at the end. The dead ends are the part that's hardest to recover.
One-off scripts. Scripts that get run once and discarded never get a code review. The Codex thread is the only place the reasoning that produced them exists.
Cross-language work. When an engineer who normally writes Go uses Codex to write a TypeScript build script, the thread shows the assumptions they made about the new language. That's invaluable for the engineer who maintains it next.

For a longer treatment of how teams have made Codex sharing stick, see Codex thread sharing for engineering teams.

Pricing

The Codex integration is free. The Free tier covers thread uploads, public links (3-day TTL), and workspace membership. Permanent shared links come with Creator ($29/month). Workspace-wide sharing and the Review feature (beta) come with Team ($19 per seat / month, minimum 2 seats).

Existing Lore URLs keep working at your current tier until the period ends, even after a cancellation.