What would you like to be added?
When resuming a previous conversation, Qwen Code currently prints all historical messages to the terminal,
causing rapid scrolling that can last several seconds for long sessions.
I'd like a --quiet-restore flag (or a settings.json option like "quietRestore": true) that skips printing
historical messages when resuming a conversation. The context would still be loaded into memory for the LLM, but
the terminal would remain clean — showing only a brief summary like "Resumed conversation with 47 messages" and
then waiting for user input.
Why is this needed?
- Long conversations (50+ messages) cause noticeable terminal scrolling on resume, which is disruptive and
provides no useful information to the user since they already saw those messages in the original session.
- On Windows Terminal especially, the scrolling is slow and visually unpleasant.
- Users can work around this with Ctrl+C, but that's unintuitive and feels like interrupting something important.
- The history output is purely cosmetic — it doesn't affect the LLM's context — so making it optional has no
functional downside.
Additional context
Suggested behavior:
CLI flag
qwen --resume --quiet-restore
Or settings.json
{
"quietRestore": true
}
Expected output on resume:
✓ Resumed conversation (47 messages, started 2026-05-10)
This is similar to how most modern CLIs (e.g., gh, docker) handle session restoration — they confirm the
action without replaying history.
What would you like to be added?
When resuming a previous conversation, Qwen Code currently prints all historical messages to the terminal,
causing rapid scrolling that can last several seconds for long sessions.
I'd like a
--quiet-restoreflag (or asettings.jsonoption like"quietRestore": true) that skips printinghistorical messages when resuming a conversation. The context would still be loaded into memory for the LLM, but
the terminal would remain clean — showing only a brief summary like "Resumed conversation with 47 messages" and
then waiting for user input.
Why is this needed?
provides no useful information to the user since they already saw those messages in the original session.
functional downside.
Additional context
Suggested behavior:
CLI flag
qwen --resume --quiet-restore
Or settings.json
{
"quietRestore": true
}
Expected output on resume:
✓ Resumed conversation (47 messages, started 2026-05-10)
This is similar to how most modern CLIs (e.g.,
gh,docker) handle session restoration — they confirm theaction without replaying history.