> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synti.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Sharing Conversations

> Publish a conversation as a read-only web page, or fork it into another workspace.

Sometimes a conversation is worth sharing — a debugging session, a plan the agent worked out, a report it generated. Synti can publish any conversation as a clean, read-only web page and copy the link to your clipboard, so anyone with the link can read it in their browser. You stay in control: update the share as the conversation grows, or stop sharing to take it down entirely.

## Sharing a conversation online

Click the share icon in the conversation header (or open the title menu) and choose **Share Online**. Synti uploads the conversation and copies the link to your clipboard automatically.

<Steps>
  <Step title="Open the share menu">
    Click the share icon in the conversation header, or use the title menu.
  </Step>

  <Step title="Choose Share Online">
    Synti uploads the conversation and copies the link for you.
  </Step>

  <Step title="Send the link">
    Paste it anywhere — the recipient opens a read-only page, no account needed.
  </Step>
</Steps>

### What's included

A shared page carries the full conversation:

* Every user and assistant message
* Tool calls and their results
* Code blocks, diffs, and terminal output
* Session metadata such as the title and the model used

### What's left out

Some things never leave your machine:

* File attachments
* Local file paths
* Plan files
* Workspace-specific configuration

## Access and privacy

Each share gets a cryptographically random 21-character ID, which makes the link effectively impossible to guess. There's no login — **anyone with the link can view the page, and can forward it to others.** Treat a share link like a secret.

<Warning>
  Read your conversation before you share it. API keys, passwords, or other secrets in the transcript are visible to anyone who has the link.
</Warning>

## Managing a share

Once a conversation is shared, its share icon turns your accent color and offers four actions:

| Action              | Effect                                                    |
| ------------------- | --------------------------------------------------------- |
| **Open in Browser** | Launches the published page                               |
| **Copy Link**       | Copies the URL again                                      |
| **Update Share**    | Re-uploads the conversation to include new messages       |
| **Stop Sharing**    | Deletes the page permanently; the link then returns a 404 |

A share has no expiration date — it stays up until you revoke it.

## Viewer experience

Recipients see a clean, read-only rendering with full formatting: syntax-highlighted code, diff previews, terminal output, and a light/dark theme toggle. They cannot send messages, run code, or otherwise interact with the conversation.

## Sending to another workspace

Sharing online isn't the only way to move a conversation. **Send to Workspace** creates an independent copy — a fork — of the session on a target workspace, visible only to people on that workspace. This needs a connected remote workspace; see [Workspaces](/go-further/workspaces).

## Limits

* A shared conversation can be at most 5 MB. Sharing fails if it exceeds that.
* There's no automatic expiry — shares persist until you stop them.

## Related

<CardGroup cols={2}>
  <Card title="Workspaces" icon="layer-group" href="/go-further/workspaces">
    Fork sessions between workspaces.
  </Card>

  <Card title="Rich output" icon="table-cells" href="/go-further/rich-output">
    Formatting is preserved on the shared page.
  </Card>
</CardGroup>