Conversation Permalink
A stable link to one answer, not the whole thread
A chat thread is one ephemeral stream — there is no address for a single answer, so sharing means forwarding the whole conversation, and the turn you meant drifts or disappears as the thread keeps going. 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.
Framing
The problem
You cannot point anyone to a single AI answer — sharing forwards the whole thread, and the turn you meant drifts or disappears as the conversation continues.
The pattern
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.
Why chat breaks here
Chat treats the conversation as one ephemeral stream — there is no address for a single turn, and continuing or editing the thread silently changes what a shared link points at.
Risks
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.
Avoid when
Throwaway chats no one will ever reference again — addressable turns add machinery with nothing to cite.
Use when
Answers worth sharing or citing need a stable address — without one you forward the whole thread and the point you meant gets lost or overwritten.
DOPE evaluation
- 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
- Predictability
- 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
Closest neighbours
- ChatGPT · Shared links (OpenAI) — A share link freezes the conversation at creation — later messages in the live thread are not reflected unless a new link is generated. The frozen-snapshot mechanic, but at thread granularity, not per turn.
- Perplexity · Shareable threads (Perplexity) — Threads share via a stable link, frozen at share time. Per-thread only — there is no per-answer address, which is exactly the granularity this pattern is about.
- Claude · Share (Anthropic) — Sharing creates a per-conversation snapshot frozen at share time; messages sent afterwards stay private. Same mechanic, same caveat: the address points at the thread, not the turn.
- 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. The only per-turn example in the set; no AI chat product ships it yet.
FAQ
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 lost or overwritten.
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?
You cannot point anyone to a single AI answer — sharing forwards the whole thread, and the turn you meant drifts or disappears as the conversation continues.
Why is chat the wrong fit for this?
Chat treats the conversation as one ephemeral stream — there is no address for a single turn, and continuing or editing the thread silently changes what a shared link points at.