Skip to content

Sharing Conversations

Overview

OpenCode’s sharing feature allows you to create public links to your conversations, making it easy to collaborate with team members, share knowledge, and get help from colleagues. The /share command generates a shareable URL that anyone can use to view your conversation.

Using the /share Command

Basic Usage

To share your current conversation, simply type:

/share

Keyboard Shortcut

You can also use the keyboard shortcut:

Ctrl+X S

What Happens When You Share

When you run the /share command:

  1. OpenCode generates a unique public URL for your conversation
  2. The URL is copied to your clipboard for easy sharing
  3. You’ll see a confirmation message with the shareable link
  4. The conversation becomes publicly accessible via the link

Example Output

✓ Conversation shared successfully
✓ Link copied to clipboard: https://opencode.share/abc123def456

Anyone with this link can view your conversation. Be careful not to share sensitive information.

Unsharing Conversations

To stop sharing a conversation and revoke public access:

/unshare

This will remove the public link and make the conversation private again.

Team Collaboration Benefits

Real-Time Knowledge Sharing

  • Instant access: Team members can view your conversation immediately
  • No context loss: Full conversation history is preserved
  • Cross-platform: Share links via email, chat, or any communication tool

Collaborative Problem Solving

  • Get input from experts: Share complex issues with specialized team members
  • Collect feedback: Team members can review your approach and suggest improvements
  • Learn together: Share successful problem-solving strategies with the entire team

Documentation and Knowledge Base

  • Create reference materials: Share valuable AI interactions as documentation
  • Onboard new team members: Use shared conversations as training resources
  • Build institutional knowledge: Create a library of solved problems and solutions

Use Cases

Code Review and Collaboration

Scenario: You’re working on a complex refactoring task and want input from a senior developer.

How to use:

  1. Work through the problem with OpenCode
  2. When you have a solution or need input, run /share
  3. Send the link to your colleague
  4. They can review the entire conversation and provide feedback

Troubleshooting and Support

Scenario: You’re encountering a difficult bug and need help from the team.

How to use:

  1. Document your debugging process with OpenCode
  2. Share the conversation with your team
  3. Team members can see exactly what you’ve tried and where you’re stuck
  4. They can provide targeted advice based on the full context

Knowledge Transfer

Scenario: You’ve discovered a useful workflow or solution that others should know about.

How to use:

  1. Create a conversation demonstrating the solution
  2. Share it with your team
  3. New team members can reference it as a learning resource
  4. The entire team benefits from your discovery

Best Practices

Security Considerations

Effective Sharing

  1. Be selective: Only share conversations that are genuinely useful to others
  2. Add context: Include a brief explanation when sharing links
  3. Follow up: After sharing, check in with team members for feedback
  4. Clean up: Use /unshare when the conversation is no longer needed

Organizing Shared Conversations

  • Create a shared document: Maintain a list of useful shared conversations
  • Use descriptive session names: Make it easy to identify what each conversation is about
  • Tag relevant team members: When sharing links, mention who might benefit most

Advanced Usage

Sharing Specific Parts of Conversations

While the /share command shares the entire conversation, you can:

  1. Use /new to start a focused conversation on a specific topic
  2. Work through the issue with OpenCode
  3. Share only that specific conversation
  4. Keep sensitive information in private conversations

Combining with Other Commands

  • /compact + /share: First summarize long conversations to make them more readable
  • /export + /share: Export as Markdown for offline reference, then share the link for online access
  • /sessions + /share: Switch between sessions and share specific ones as needed

FAQ

Q: Who can access my shared conversations?

A: Anyone with the link can view your shared conversation. There’s no authentication required.

Q: How long do shared conversations remain accessible?

A: Shared conversations remain accessible until you run the /unshare command or until the conversation is deleted.

A: No, the link is automatically generated and cannot be customized.

Q: Is there a limit to how many conversations I can share?

A: No, there’s no limit to the number of conversations you can share.

Q: What happens to shared conversations if I delete my OpenCode installation?

A: Shared conversations are hosted on OpenCode’s servers, but we recommend unsharing conversations before uninstalling to ensure privacy.

Conclusion

The sharing feature in OpenCode is a powerful tool for team collaboration, knowledge sharing, and getting help from colleagues. By following best practices and using it responsibly, you can enhance your team’s productivity and build a valuable knowledge base of AI-assisted problem-solving.

Remember to always be mindful of the content you share and use the /unshare command when conversations are no longer needed.