Qwen Code 0.26.6 adds model timing and clearer recovery to Web Shell

Qwen Code 0.26.6 adds model timing and recovery information to Web Shell.

Qwen Code released version 0.26.6 on November 2. The release adds model timing and failure information to Web Shell, introduces a sidebar option for opening eligible sessions in Split View and adds RPM installers for Fedora 44 and RHEL 10 on x64. It is a release of the coding client and its supporting tooling. [Qwen Code v0.26.6 release](https://github.com/QwenLM/qwen-code/releases/tag/v0.26.6)

Timing that helps separate different delays

The Web Shell Token Usage view now plots first-token latency, output speed and failure details per request by model. A request can take a long time before any text arrives and then stream quickly. Another can start promptly and generate slowly. Recording both measures gives a team a way to investigate those two experiences separately. It also helps when a failure could come from a model route or the surrounding service. [Release notes](https://github.com/QwenLM/qwen-code/releases/tag/v0.26.6)

The release changes how failed managed-session lists appear. Web Shell displays a retry notice and request information when loading fails. An empty session list and an unavailable session list call for different actions. By making the failure visible, the interface gives the operator a way to retry or correlate the request without assuming sessions were removed. [Release notes](https://github.com/QwenLM/qwen-code/releases/tag/v0.26.6)

Where the smaller fixes matter

The notes describe changes to how Web Shell displays approval text and paths. It escapes control characters and bidirectional formatting controls in those contexts. This reduces the chance that hidden formatting changes what a user sees when deciding whether to approve an action. The change concerns the displayed content. Approval authorization and the scope of an action are separate controls. [Release notes](https://github.com/QwenLM/qwen-code/releases/tag/v0.26.6)

The package and interface changes affect different users. An administrator installing the desktop client can check the new distribution-specific artifact. A Web Shell user can open two eligible sessions and inspect a deliberately failed request to see whether the new status information helps. Both checks should use the precise release version, especially in an installation where the desktop and managed runtime are updated separately.