Claude's output teardown

Updated June 15, 2026

Claude keeps lightweight Q&A in the message stream so small course corrections do not require a new chat. Try again, quote-to-reply, and feedback handle iteration at message scale. When the deliverable grows beyond prose, it graduates to an artifact in a separate teardown.

Short answers stay in the thread

Factual Q&A with copy, read-aloud, feedback, and Try again. No side pane needed.

What works

Not every answer becomes an artifact. Simple replies stay in the stream so reading flow stays uninterrupted.
Per-message actions (copy, read aloud, thumbs, Try again) sit directly under the answer. Refinement targets one turn, not the whole chat.
Edit on the user bubble supports thread branching when someone revisits an earlier prompt.

What we would push on

Try again and edit sit beside each other with equal weight. First-time users may not know edit forks while Try again keeps the same branch.

Business strategy

Claude keeps quick answers in-thread so chat feels fast and artifacts feel like a promotion, not the default. That lowers intimidation for new users while reserving the split pane for work worth shipping.

Tradeoff

Decision	Benefit	Cost
In-thread answers as default; artifacts on promotion	Uninterrupted reading flow for simple Q&A	Users may not know when output should graduate to an artifact

Takeaway

Default to in-thread output. Artifacts should feel like a promotion, not the norm.

Pattern: Response Refinement

Pattern: Thread Branching

Try again without losing the first draft

After Try again, 2/2 navigation lets users compare versions of the same answer.

What works

Try again generates an alternate answer instead of overwriting the first one.
1/N navigation with Previous version tooltip makes comparison explicit. Users can pick the better draft or keep exploring.
Versioning applies to in-thread text answers before any artifact opens.

What we would push on

Version controls are small and easy to miss under long answers. High-stakes edits may need a clearer “you are viewing version 2” banner.

Business strategy

Non-destructive Try again encourages more retries per session without fragmenting context across new chats. Users explore alternatives in place, which drives inference without losing the thread.

Tradeoff

Decision	Benefit	Cost
Try again with 1/N version navigation	Low-cost retries; compare drafts in place	Version controls easy to miss under long answers

Takeaway

Non-destructive Try again lowers the cost of asking for a redo. Pair it with visible version navigation.

Pattern: Response Refinement

Thumbs up opens structured feedback

Optional details field asks what was satisfying; submit sends the conversation for model improvement.

What works

Thumbs up sits in the per-message action row beside copy, read aloud, and Try again. Feedback targets one reply.
The modal is lightweight: one optional text field (“What was satisfying about this response?”) plus Cancel and Submit.
Disclaimer states the full conversation may be sent to Anthropic, explicit consent before submit.

What we would push on

Modal interrupts flow for a simple thumbs up. One-click satisfaction with details optional on expand might feel faster.

Business strategy

Anthropic pairs low-friction thumbs with optional qualitative capture so praise still yields training signal when users want to explain what worked, not just that it worked.

Tradeoff

Decision	Benefit	Cost
Thumbs up opens optional detail modal	Qualitative praise signal when users opt in	Modal interrupts flow for simple satisfaction

Takeaway

Pair low-friction thumbs with an optional qualitative capture when users want to explain what worked.

Pattern: Feedback

Thumbs down adds issue taxonomy

Negative feedback adds an issue-type dropdown plus optional details before submit.

What works

Thumbs down opens a richer form than thumbs up, issue type dropdown helps route reports without free-text guessing.
Optional details field still available for specifics (“What was unsatisfying about this response?”).
Same conversation-disclosure copy as positive feedback keeps trust symmetric.

What we would push on

Asymmetric depth (dropdown on down, not up) makes sense for triage but may feel punitive. Keep the down path fast if users skip the form.

Business strategy

Structured issue types on negative feedback route safety, quality, and capability failures to the right teams. Anthropic needs categorized signal more than aggregate downvotes.

Tradeoff

Decision	Benefit	Cost
Issue-type dropdown on thumbs down	Routable failure categories for triage	Heavier down path than up; may feel punitive

Takeaway

Use structured issue types on negative feedback where you need to categorize failures; keep positive path lighter.

Pattern: Feedback

Reply on a selection

Highlight part of the answer; Reply tooltip targets refinement to that passage.

What works

Users can select prose inside an assistant message, not just react to the whole bubble.
Reply tooltip appears on the selection so the follow-up is scoped (“fix this bullet”) instead of vague (“make it better”).
Works on list items and paragraphs alike; selection stays highlighted until the user acts.

What we would push on

Reply on selection is discoverable only after highlighting. No persistent affordance for users who do not try select-first.

Business strategy

Selection-based reply scopes follow-ups to one passage, reducing full Try again regenerations and keeping users in a mostly-good answer instead of starting over.

Tradeoff

Decision	Benefit	Cost
Reply tooltip on text selection	Surgical refinement without full rewrite	Discoverable only after highlighting

Takeaway

Let users anchor refinement to a span of text when the issue is local, not global.

Pattern: Response Refinement

Quote lands in the composer

Selected passage appears as a quote chip above the prompt; user adds the fix on top.

What works

Quoted text carries into the composer as a removable chip, Claude sees exactly which lines the user is talking about.
Send stays available once the user types a follow-up; quote + new instruction ship as one message.
Alternative to Try again when the user wants a surgical edit, not a full rewrite.

What we would push on

Quote chip truncates long selections. Verify the model still receives full context on multi-paragraph quotes.

Business strategy

Quote-to-reply makes surgical edits explicit in the composer, so the model and user share the same anchor. That reduces vague follow-ups and failed regenerations.

Tradeoff

Decision	Benefit	Cost
Quote chip in composer for selection follow-ups	Explicit scope; model sees exact lines	Long selections may truncate in the chip UI

Takeaway

Quote-to-reply is refinement without regenerating the whole answer, pair it with Try again for full rewrites.

Pattern: Response Refinement

How output fits with artifacts

The pattern

Quick answers in-thread with per-message actions: copy, read aloud, Try again, thumbs up/down.
Non-destructive Try again with 1/N version navigation; edit on user messages for thread branching.
Quote-to-reply on selections for surgical follow-ups; artifacts when work graduates beyond a reply.

Where it varies

Refinement path: full Try again vs quote-to-reply vs edit-to-branch depending on whether the issue is local or directional.
Feedback depth: optional modal on thumbs up, issue-type dropdown on thumbs down.
Artifact promotion happens in a separate teardown; in-thread refinement continues while the pane is open.

Business strategy

Claude splits output into a fast in-thread layer and a promoted artifact layer. Chat stays the reasoning trail; the artifact is the deliverable users copy, run, or ship. That keeps simple Q&A lightweight while competing on substantial work.

Tradeoffs

Decision	Benefit	Cost
In-thread answers as default; artifacts on promotion	Uninterrupted reading flow for simple Q&A	Users may not know when output should graduate to an artifact
Try again with 1/N version navigation	Low-cost retries; compare drafts in place	Version controls easy to miss under long answers
Thumbs up opens optional detail modal	Qualitative praise signal when users opt in	Modal interrupts flow for simple satisfaction
Issue-type dropdown on thumbs down	Routable failure categories for triage	Heavier down path than up; may feel punitive
Reply tooltip on text selection	Surgical refinement without full rewrite	Discoverable only after highlighting
Quote chip in composer for selection follow-ups	Explicit scope; model sees exact lines	Long selections may truncate in the chip UI

Takeaway

Claude spreads refinement across Try again, version navigation, quote-to-reply, and edit-to-branch while keeping most answers in-stream. Steal non-destructive retries and quote chips; graduate to artifacts when the deliverable is worth a workspace.

Pattern: Response Refinement

Pattern: Thread Branching

Pattern: Feedback