UI bug导致token翻倍

[zeonseoi]

环境信息

• 操作系统：Windows 11
• 终端：Git Bash（Laragon 环境）
• Qwen Code 版本：v0.16.0
• Node.js 版本：v24.9.0

问题描述

从 v0.15.11 升级到 v0.16.0 后，CLI 的 UI 完全显示异常。
状态栏/界面渲染出现乱码，无法正常使用（见截图）。

截图

复现步骤

1. npm install -g @qwen-code/qwen-code@0.16.0
2. 在 Git Bash 终端中运行 qwen
3. CLI UI 立即显示异常

临时解决方案

回退到 v0.15.11 后恢复正常：
npm install -g @qwen-code/qwen-code@0.15.11

补充说明

v0.15.11 在该环境下运行正常，升级到 v0.16.0 后出现此问题。
猜测可能与 v0.16.0 新增的状态行预设（statusLine preset）相关。

[qwen-code-ci-bot]

This appears related to other status line rendering issues:

• ui.statusLine crashes CLI with spawn EBADF on macOS, then hits ansiRegex3 is not a function #3264 - ui.statusLine crashes CLI with spawn EBADF on macOS (closed) - similar statusLine rendering crash with ansiRegex error
• 无法在win11的git bash中正常进入qwen #2774 - Git Bash TTY detection issues on Windows (closed) - general Git Bash compatibility problem

The version-specific regression (v0.15.11 → v0.16.0) and Git Bash environment suggest this may be related to the new statusLine preset feature interacting with Windows terminal handling.

[LaZzyMan]

Confirmed v0.16.0 regression — UI rendering is broken on Windows + Git Bash. Your hypothesis about the new statusLine preset is the right direction; cc @wenshao who owns the statusLine feature.

For users hitting this: temporary workaround is to downgrade — npm install -g @qwen-code/qwen-code@0.15.11. We'll prioritize a v0.16.x fix.

[zeonseoi]

@wenshao

[yiliang114]

Root Cause Analysis

The v0.15.11 → v0.16.0 regression on Windows Git Bash (MinTTY) is likely caused by a combination of changes:

1. Ink 6 → 7.0.3 upgrade (primary suspect) — #4119

Ink 7 rewrote the render pipeline (output diffing, cursor positioning, line-erase sequence generation). MinTTY handles certain ANSI cursor-movement + erase combinations differently from xterm/VT100. The new sequences Ink 7 generates may hit MinTTY rendering edge cases that Ink 6 did not trigger.

Context: Ink was first upgraded to 7.0.2 in #3860, reverted in #4083 due to a <Static> remount bug, then re-upgraded to 7.0.3 in #4119 after upstream fixed that specific issue. The MinTTY compat problem is a separate, previously untested scenario.

2. OSC 8 hyperlink wrapping (aggravating factor) — #4037

v0.16.0 added OSC 8 hyperlink support. The detection logic (supportsHyperlinks() in osc8.ts:239) returns true for TERM_PROGRAM=mintty unconditionally, assuming mintty ≥ 3.3. If the Git Bash bundled with Laragon ships an older mintty, the raw OSC 8 escape bytes (\x1b]8;;url\x07) would render as visible garbage.

3. terminalRedrawOptimizer interaction

The optimizer monkey-patches stdout.write to collapse repeated eraseLine + cursorUp pairs. With Ink 7's changed output patterns, the optimizer's regex may no longer match correctly, causing either missed optimizations (redundant erase sequences) or incorrect sequence merging.

Suggested fixes

• Gate OSC 8 on mintty version (≥ 3.3) rather than blanket true
• Test Ink 7.0.3 rendering specifically on MinTTY — may need platform-specific adaptation
• Document QWEN_CODE_LEGACY_ERASE_LINES=1 as immediate user workaround

[zeonseoi]

@wenshao @yiliang114

后续测试情况：

1. v0.16.1、v0.16.2、v0.17.0 全部测试过，UI 乱码问题依然存在。
2. 问题不限于 Git Bash/MinTTY。PowerShell、cmd、Windows Terminal 下全部乱码。这说明不是终端模拟器兼容性问题