Qwen output: keep the chain in the thread
Qwen bets on continuation. Media jobs stay in one thread so a reference photo can become an image, then a video, without leaving chat. Search answers bring retrieval signals and an optional audit path beside the reply. The patterns that matter are in-thread handoffs and whether claim-level sourcing keeps up with confident lists.
Photo to image prompt

What works
- The model shows an art-direction brief before pixels. Users can edit scope before spend.
- Mode controls stay armed through the reply. The job does not reset mid-thread.
What we would push on
- A long single block is hard to scan. Call out what changed from the upload.
- Send readiness should be obvious when the expanded prompt is the thing to approve.
Product bet
Showing prompt expansion builds trust for image spend. Users feel the model understood the reference before GPU time runs.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Visible text prompt step before image generate | Edit scope before render; teaches prompt quality | Extra scroll; slower time-to-image |
Takeaway
For reference-image gen, show the rewritten prompt in-thread and let users edit it before render.
Pattern: Progressive Disclosure
Image in thread

What works
- Chain actions live on the image. Next jobs stay on the artifact, not buried in +.
- Message-level actions cover feedback and export without leaving the thread.
What we would push on
- Aspect label and rendered result must agree. Lying chips break format trust.
- Accuracy disclaimers that sit under the bar lose to confident output above.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Inline image with chain overlays plus message actions | Chains image to video without re-upload | Aspect chip can lie; disclaimer fades into footer |
Takeaway
Put chain actions on the image itself. Match aspect label to what actually rendered.
Animate with reference

What works
- Source stays pinned in the bar. Context is visible before the next spend.
- Mode follows intent. Short language can swap Create Image to Create Video without re-upload.
What we would push on
- Silent chip swaps teach less than a one-line mode change notice.
- Motion controls belong at prompt time if video is a first-class job.
Product bet
Image-to-video is the upsell path. Reference plus auto mode swap keeps users in one thread instead of a separate video app.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Reference thumbnail in bar with auto Create Video chip | Natural language handoff; no re-upload | Limited motion controls at prompt time |
Takeaway
When a reply references prior media, pin the thumbnail and swap mode chips to match the next job.
Pattern: Tool Switching in Composer
Video generation progress

What works
- A progress card makes render feel like a job, not a stuck chat.
- Mode settings survive the wait so people can prepare another pass.
What we would push on
- Percent alone is thin for long renders. Stage copy or ETA reduces anxiety.
- Blocking the next send until render finishes kills queueing.
Takeaway
Show percent for video gen, but add stage copy or ETA when renders run longer than a few seconds.
Pattern: Progressive Disclosure
Preview, download, publish

What works
- Preview with duration treats video as a deliverable, not a chat attachment.
- Download and publish sit as equal primaries. Export is the goal.
- Mode bar stays available for another pass without losing context.
What we would push on
- Publish needs a named destination. Trust requires knowing where it goes.
- Aspect mismatch between setting and preview is the same format lie as images.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Modal preview with Download and Publish plus persistent mode bar | Clear export path; easy retry | Publish target vague; aspect mismatch visible |
Takeaway
Treat video like a deliverable: preview, duration, download, and name the publish target on the button.
Web search answer

What works
- A retrieval signal and inline domains sell "this was researched."
- Structured product lists scan better than a wall of prose for shopper queries.
What we would push on
- Citation chrome can costume a hallucination. Authoritative layout on a fictional product is worse than a plain miss.
- Domains without claim-level links make audit hard. Numbers beat orphan chips.
- Tiny disclaimers lose to confident lists above them.
Product bet
Search mode competes on Perplexity-shaped answers. Retrieval chrome sells freshness even when the model fills gaps with fiction.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Chat-formatted search answer with inline domain chips | Familiar reading flow; looks researched | Hallucination wears a citation costume; weak claim-to-source link |
Takeaway
If you show domain chips, tie each claim to a numbered source and surface when retrieval failed or dates look wrong.
Selection actions

What works
- Selection refinement works on research answers, not only plain chat.
- Translate depth matches a multilingual product bet.
What we would push on
- Overlapping ask vs explain actions force a coin flip.
- Search threads need source-check actions on selection, not only rewrite verbs.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Generic selection menu with translate submenu on search output | Reuse chat refinement patterns on research answers | Missing search-specific actions; Ask vs Explain redundant |
Takeaway
Extend selection menus for search threads with source-check actions, not only translate and explain.
Follow-ups and source badges

What works
- Follow-ups keep the research session going without a blank bar.
- Armed search mode persists so the next turn stays in the same job.
What we would push on
- Follow-ups that repeat a shaky premise amplify the error.
- Source counts that do not open a list impress more than they inform.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Follow-up pills plus source count badges on search answers | Keeps research session going; signals many sources | Suggestions can amplify errors; badge count without list |
Takeaway
Follow-ups should deepen verification, not repeat the same shaky premise. Make source badges open the drawer.
Copy this
- Prompt expansion in-thread before image generate from a reference
- Chain actions on the image itself
- Reference thumbnail plus auto mode swap for image-to-video
- Video progress as a job card while mode settings persist
- Preview modal with duration, download, and named publish
- Retrieval signal plus claim-linked sources on search answers
- Optional audit drawer for reasoning and sources
- Selection refinement that includes source-check on search threads
Skip this
- Citation chrome on answers that invent products or dates
- Aspect settings that disagree with what rendered
- Publish without a named destination
- Overlapping selection actions with no guidance
- Follow-ups that double down on wrong premises
- Source count badges that do not open a source list
How others output, artifacts & refinement
How other products handle the same job, and what each tradeoff reveals.
Compare output & artifacts UX
ChatGPT, Claude, Perplexity, and Gemini side by side: refinement, artifacts, export, and patterns to copy.
Perplexity numbers citations and centers sources. Qwen keeps chat-shaped answers with domain chips and an optional audit drawer.
Read teardownChatGPT chains image and video in-thread. Qwen also arms Web search as a composer mode with starters under the bar.
Read teardownGemini output leans Guides and Workspace exports. Qwen focuses on the generative chain and search refinement menus.
Read teardownUseful for a critique or spec? Share it.
Original gallery pages: Output & Refinement
