Overview
How might we design shared session link so people can trust and act on AI output?
When this pattern fits
- Essential for support escalation, design critique, and team debugging where one person’s AI session must be replayed or continued by another.
When to skip or lighten it
- Sessions containing secrets that cannot be safely shared.
- Personal journaling chats with no collab need.
- Exports that already cover the handoff better than a live link.
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Public-by-default links with no auth.
Links that keep working after the owner intended revoke.
Sharing UI that omits what data the recipient will see.
Recipients who can trigger spend without knowing a budget applies.
How products use it
| Product | Implementation |
|---|---|
| ChatGPT | Share chat links with view access controls. |
| Claude | Shareable conversation links for collaboration. |
| Cursor | Shared threads and project context for teams. |
| Replit | Shareable AI-assisted project sessions. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Shared Session Link" AI interface design pattern.
Pattern Definition:Frequently asked questions
What should a shared session link include?
Visible messages, attached files the sharer allows, and permission level (view vs continue). State expiry and revoke clearly.
View-only vs continue?
View-only is for review. Continue lets recipients prompt in the same context—gate spend and tools carefully.
How does this differ from export?
Export is a snapshot file. A shared link is a living (or frozen) session inside the product.
How do you revoke safely?
Kill the link immediately, list active viewers if possible, and rotate any embedded credentials.