AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Collab

Shared Session Link

A URL to the same AI context (prompts, files, outcomes) with permission controls. Share the session. Stop screenshotting the chat.

Interactive demo

Share chat

Session link

Recipients see this thread and attachments you allow.

aiux.dev/s/7k2n

Anyone with the link can comment

Overview

How might we design shared session link so people can trust and act on AI output?

When to use

  • 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

  • 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.

Rules

  • 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.

Evidence

ProductImplementation
ChatGPTShare chat links with view access controls.
ClaudeShareable conversation links for collaboration.
CursorShared threads and project context for teams.
ReplitShareable AI-assisted project sessions.

FAQ

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.