[UI] container ‘qwen-code-secondary’ does not exist

[0xFE-LIT]

What happened?

When moving the extension panel to the secondary sidebar, the following message appeared:

extension's Runtime Status

View container ‘qwen-code-secondary’ does not exist and all views registered to it will be added to ‘Explorer’.

However, this did not affect functionality.

What did you expect to happen?

Error-free operation

Client information

Qwen Code: 0.12.3 (f1ee463)
Среда выполнения: Node.js v22.15.1 / npm unknown
ОС: linux x64 (6.12.47-generic-5rosa2021.1-x86_64)
Аутентификация: Qwen OAuth
Модель: coder-model
ID сессии: 0d538d25-569b-4b9e-b9f7-ec2a6606c1f9
Песочница: no sandbox
Прокси: no proxy
Использование памяти: 169.1 MB

Login information

No response

Anything else we need to know?

No response

[yiliang114]

Thanks for the feedback! 🙏

To help investigate this issue, could you please provide your VSCode version information?

How to get it:

• Press Cmd + Shift + P (macOS) or Ctrl + Shift + P (Windows/Linux)
• Type About, then a version info window will appear

[0xFE-LIT]

could you please provide your VSCode version information?

Version: 1.102.3
Commit: 488a1f239235055e34e673291fb8d8c810886f81
Date: 2025-07-29T03:00:23.339Z
Electron: 35.6.0
ElectronBuildId: 11847422
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Linux x64 6.12.47-generic-5rosa2021.1-x86_64

[yiliang114]

@0xFE-LIT Thanks for the report!

Based on the version info you shared, this looks like a compatibility case with older VS Code versions rather than a functional error.

1.102.3 is below the secondary sidebar support threshold we currently use, so in that case the extension should fall back to the primary sidebar. That means this message is expected to be a warning / fallback signal, not a runtime failure.

Could you help confirm one thing: in your actual usage, is everything working normally and the only confusing part is this warning message?

Either way, I'll likely improve the messaging here so the fallback behavior is clearer on older VS Code versions.

[0xFE-LIT]

thanks! there's only this issue on that version of VS Code. Everything works fine