Qwen logo

Qwen output: keep the chain in the thread

Updated August 25, 2026

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

Upload a portrait, arm Create Image mode, and send without typing a prompt.
Upload a portrait, arm Create Image mode, and send without typing a 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

DecisionBenefitCost
Visible text prompt step before image generateEdit scope before render; teaches prompt qualityExtra scroll; slower time-to-image

Takeaway

For reference-image gen, show the rewritten prompt in-thread and let users edit it before render.

Image in thread

After generate, view the image in the thread with action overlays.
After generate, view the image in the thread with action overlays.

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

DecisionBenefitCost
Inline image with chain overlays plus message actionsChains image to video without re-uploadAspect 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

With the image in thread, type "animate it" in the composer.
With the image in thread, type "animate it" in the composer.

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

DecisionBenefitCost
Reference thumbnail in bar with auto Create Video chipNatural language handoff; no re-uploadLimited motion controls at prompt time

Takeaway

When a reply references prior media, pin the thumbnail and swap mode chips to match the next job.

Video generation progress

Send the animate request and wait for the progress card.
Send the animate request and wait for the progress card.

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.

Preview, download, publish

Open the finished video preview modal.
Open the finished video preview modal.

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

DecisionBenefitCost
Modal preview with Download and Publish plus persistent mode barClear export path; easy retryPublish 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

Send Best budget laptops with Web search mode armed.
Send Best budget laptops with Web search mode armed.

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

DecisionBenefitCost
Chat-formatted search answer with inline domain chipsFamiliar reading flow; looks researchedHallucination 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.

Thinking and Search panel

Open the Thinking and Search sidebar on a web search answer.
Open the Thinking and Search sidebar on a web search answer.

What works

  • A dedicated audit drawer separates reading from verification.
  • Titles, snippets, and overflow count show breadth at a glance.

What we would push on

  • An optional panel does not fix a bad main answer. Most people never open it.
  • If snippets repeat the same fiction, transparency is not a cure.

Tradeoff

DecisionBenefitCost
Optional sidebar with source list and overflow countPower users can audit retrievalAudit surface still bad if sources are wrong; easy to ignore

Takeaway

A source drawer helps only if snippets are real. Pair it with date checks and a low-confidence state in the main answer.

Selection actions

Highlight text in the search answer (e.g. Price: $599).
Highlight text in the search answer (e.g. Price: $599).

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

DecisionBenefitCost
Generic selection menu with translate submenu on search outputReuse chat refinement patterns on research answersMissing 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

Scroll to the bottom of the search answer for chips and source globes.
Scroll to the bottom of the search answer for chips and source globes.

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

DecisionBenefitCost
Follow-up pills plus source count badges on search answersKeeps research session going; signals many sourcesSuggestions 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.

Full comparison

Useful for a critique or spec? Share it.

Original gallery pages: Output & Refinement