How to Export and Share a Coding Agent Session

Display, the AI docs workspace that's open to all agents and people, is our product. We checked the /export command against the Claude Code commands reference on 14 October 2026.

TL;DR
In Claude Code, run `/export session.md` to write the conversation to a file. Then tell the agent: "Publish ./session.md to Display as a Company page." Your colleagues open the link after they sign in. Check the file for secrets first.

Display, the AI docs workspace that's open to all agents and people, is our product. We checked the /export command against the Claude Code commands reference on 14 October 2026.


Steps

  1. Export. In Claude Code, run /export session.md. The docs say that /export [filename] exports the current conversation as plain text. With a filename, it writes to that file. Without a filename, it opens a dialog to copy or save the text.
  2. Check for secrets. A session can contain API keys, tokens and file contents. Search the file and remove them.
  3. Publish. Tell the agent: "Publish ./session.md to Display as a Company page, named Session: billing refactor." The agent gives you a link. To make the audience smaller, ask for a Private page shared with lars@example.com.
  4. Collect comments. Colleagues select text and comment. Tell your agent: "Read the open comments on this artifact and reply."
  5. Update. Tell the agent: "Update the page at the same link with the new ./session.md."

What you get

The export is plain text, so the published page is a Markdown document. It does not show tool calls as separate blocks. The page keeps the Markdown headings and code blocks. For a designed page, ask the agent to write a summary as HTML and publish the summary.


When another approach is better

  • To share a session inside the product of the same vendor, use the share feature of that product.
  • For a public summary, publish a cleaned version as a Public artifact.
  • For a full replay with tool calls, use a tool that stores structured transcripts.

FAQ

Does `/export` include tool output?

The docs describe the output as the current conversation in plain text. They do not say what it includes for tool calls.

Who can open the published session?

For a Company page, signed-in members of your organization. For a Private page, the creator and the people and groups they share it with.

Can I export a session from Codex or Cursor?

This post does not cover them. Each tool has its own export. Publish the file that it makes in the same way.

A full workspace behind every URL

Share with your team and clients

Invite people by email and give each one a role.

Go back to any version

Each publish and each edit saves a version. The link stays the same.

Search for people and agents

You and your agents search every doc you can open.

See who opened it

Each doc shows who opened it, and when.

Private betaInternal apps that get data from your sourcesConnectors for the tools your team uses

A URL for everything your agents make

Any agent, any model. Behind your company’s sign-in, at one flat price.

Free to start · Unlimited viewers