Buckets:
| title: Share | |
| description: Share your OpenCode conversations. | |
| OpenCode's share feature allows you to create public links to your OpenCode conversations, so you can collaborate with teammates or get help from others. | |
| :::note | |
| Shared conversations are publicly accessible to anyone with the link. | |
| ::: | |
| ## How it works | |
| When you share a conversation, OpenCode: | |
| 1. Creates a unique public URL for your session | |
| 2. Syncs your conversation history to our servers | |
| 3. Makes the conversation accessible via the shareable link — `opncd.ai/s/<share-id>` | |
| ## Sharing | |
| OpenCode supports three sharing modes that control how conversations are shared: | |
| ### Manual (default) | |
| By default, OpenCode uses manual sharing mode. Sessions are not shared automatically, but you can manually share them using the `/share` command: | |
| ``` | |
| /share | |
| ``` | |
| This will generate a unique URL that'll be copied to your clipboard. | |
| To explicitly set manual mode in your [config file](/docs/config): | |
| ```json title="opencode.json" | |
| { | |
| "$schema": "https://opencode.ai/config.json", | |
| "share": "manual" | |
| } | |
| ``` | |
| ### Auto-share | |
| You can enable automatic sharing for all new conversations by setting the `share` option to `"auto"` in your [config file](/docs/config): | |
| ```json title="opencode.json" | |
| { | |
| "$schema": "https://opencode.ai/config.json", | |
| "share": "auto" | |
| } | |
| ``` | |
| With auto-share enabled, every new conversation will automatically be shared and a link will be generated. | |
| ### Disabled | |
| You can disable sharing entirely by setting the `share` option to `"disabled"` in your [config file](/docs/config): | |
| ```json title="opencode.json" | |
| { | |
| "$schema": "https://opencode.ai/config.json", | |
| "share": "disabled" | |
| } | |
| ``` | |
| To enforce this across your team for a given project, add it to the `opencode.json` in your project and check into Git. | |
| ## Un-sharing | |
| To stop sharing a conversation and remove it from public access: | |
| ``` | |
| /unshare | |
| ``` | |
| This will remove the share link and delete the data related to the conversation. | |
| ## Privacy | |
| There are a few things to keep in mind when sharing a conversation. | |
| ### Data retention | |
| Shared conversations remain accessible until you explicitly unshare them. This | |
| includes: | |
| - Full conversation history | |
| - All messages and responses | |
| - Session metadata | |
| ### Recommendations | |
| - Only share conversations that don't contain sensitive information. | |
| - Review conversation content before sharing. | |
| - Unshare conversations when collaboration is complete. | |
| - Avoid sharing conversations with proprietary code or confidential data. | |
| - For sensitive projects, disable sharing entirely. | |
| ## For enterprises | |
| For enterprise deployments, the share feature can be: | |
| - **Disabled** entirely for security compliance | |
| - **Restricted** to users authenticated through SSO only | |
| - **Self-hosted** on your own infrastructure | |
| [Learn more](/docs/enterprise) about using opencode in your organization. | |
Xet Storage Details
- Size:
- 2.93 kB
- Xet hash:
- 824fa96aecbaabcbdaa01ec2a8f5a17a7147b79f2001cec36144e10499ae2c2c
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.