← Back to patterns
Trust & Verification
Emerging

Conversation Permalink

A stable link to one answer, not the whole thread

A chat thread is one moving stream. Most products can only share it whole, so the turn you meant is buried in the rest of it; the few that link a single answer pass on its words, at most with its prompt, not the model or the context behind them. A Conversation Permalink gives every turn a stable address that captures that answer and the context it came from, so it can be shared, cited, and reopened exactly as it was — even after the live thread has moved on.

Metaphor

Anchor

Interaction

Per-Turn Link, Snapshot Capture, Reopen Read-only

Use case

Sharing AI Answers, Citing Output, Bookmarking, Support Handoffs

Failure mode

Buried Turn

Control mechanisms

Link Affordance per Turn · Context Snapshot · Permalink Chip · Frozen View

Reference examples

Microsoft Copilot Share response · ChatGPT Shared links · Perplexity Shareable sessions · Claude Share · Slack Message permalinks

Interactive Example

The chat default and the pattern, against each other on the same task. The demo is the comparison.

Loading Demo

Preparing the interactive example for this pattern.

A chat link carries the words. Rarely what produced them.

A conversation is one moving stream. Most chats still share the whole thread, so the turn you pointed at is buried among the rest. The best now link a single answer as a snapshot, but what travels is the text, at most with its prompt — not the model that wrote it or the rest of the context it was given, so whoever opens it cannot check what they are citing.

A permalink gives each turn an address that freezes it: the answer, the model, and a snapshot of the context it was given. Share it, cite it, bookmark it — and it reopens exactly as it was, no matter how far the live thread has moved on.

An answer you can't trace is an answer you can't cite — and the web ran on permalinks for a reason.

DOPE Lens

How this pattern improves AI interaction quality.

DOPETRUSTWORTHYAIAUTONOMY

Directability

Copy, share, or bookmark any turn; open a permalink read-only, or fork a fresh thread from it

Observability

Every turn carries a visible link affordance, and the permalink names what it captured — which turn, which model, how much context

PredictabilityPrimary

The link always reopens the same answer and the same context snapshot, even as the live thread keeps growing

Explainability

The permalink shows the captured context — the messages it was given, the model, and when it was frozen

Fit

Where it earns its place.

Use it
when

Answers worth sharing or citing need a stable address — without one you forward the whole thread and the point you meant gets buried in it.

Avoid
when

Throwaway chats no one will ever reference again — addressable turns add machinery with nothing to cite.

In the wild

Where this pattern already ships.

The pattern is shipping but still maturing across products. Entries below show how different teams have approached it; expect variation as the space settles.

Microsoft Copilot · Share response — conversation-permalink pattern in use

Microsoft Copilot · Share response

Microsoft

Share response, in the More options menu on an answer, links that one response plus the prompt that generated it: a snapshot, and a follow-up starts a separate copy in the viewer's own history. Viewers must sign in, and work or school links stay inside the organization. Referenced files keep their permissions, deleting the conversation stops its sharing links, and the help page says nothing of the link carrying the model or earlier turns.

Visit Microsoft ↗

ChatGPT · Shared links — conversation-permalink pattern in use

ChatGPT · Shared links

OpenAI

Share the whole conversation or a single assistant response — a link to one answer, the per-turn address this pattern asks for. Personal links are snapshots that leave out later messages until you choose Update link; workspace links can pick them up. The help page says nothing of the link naming the model or context behind the answer.

Visit OpenAI ↗

Perplexity · Shareable sessions — conversation-permalink pattern in use (from the vendor's site)

Perplexity · Shareable sessions

Perplexity

Threads are now sessions, shared by one link set to Private, Anyone with the link, or org-only; a visitor's follow-up starts their own session instead of changing yours. Each answer can show the model and search mode behind it, but the address is per session, not per answer — and whether a shared link freezes or keeps growing is not documented.

Visit Perplexity ↗

Claude · Share — conversation-permalink pattern in use

Claude · Share

Anthropic

Share opens on Only people invited — add people by email, or copy a link — and says it plainly: only messages up until now will be shared. It is a snapshot, artifacts included; later messages stay private until you update the shared chat. The address points at the whole chat, not one answer — ChatGPT's response-level link is the step past it.

Visit Anthropic ↗

Slack · Message permalinks — conversation-permalink pattern in use (from the vendor's site)

Slack · Message permalinks

Slack

Copy link on any message yields a stable per-message address that survives as the channel moves on — the mature, non-AI precedent for per-turn addresses, which AI chat has only begun to ship: ChatGPT and Microsoft Copilot now each link a single response.

Visit Slack ↗

Research Frame

Why this pattern exists, and where it breaks.

Most chats can only share the whole thread, so the turn you meant is buried in everything around it — and the few that link one answer pass on its words, at most with its prompt, not the model or context behind them.

Give every turn a stable permalink that captures that answer plus the context it came from, so it can be shared, cited, and reopened exactly as it was.

Chat treats the conversation as one moving stream: most products have no address for a single turn, a whole-thread link buries the turn you meant, and even a per-answer link carries the text, at most with its prompt, without the model and context that produced it.

A permalink that re-renders against the live thread instead of a frozen snapshot breaks the moment the conversation moves on; capturing context also widens what a shared link can expose.

Common questions

What people ask about this pattern.

When should I use the Conversation Permalink pattern?

+

Answers worth sharing or citing need a stable address — without one you forward the whole thread and the point you meant gets buried in it.

When should I avoid the Conversation Permalink pattern?

+

Throwaway chats no one will ever reference again — addressable turns add machinery with nothing to cite.

What problem does Conversation Permalink solve?

+

Most chats can only share the whole thread, so the turn you meant is buried in everything around it — and the few that link one answer pass on its words, at most with its prompt, not the model or context behind them.

Why is chat the wrong fit for this?

+

Chat treats the conversation as one moving stream: most products have no address for a single turn, a whole-thread link buries the turn you meant, and even a per-answer link carries the text, at most with its prompt, without the model and context that produced it.