Расширение Qwen Code Companion для VS Code опять не работает ,

[AndyInjiner]

What happened?

Preparing Qwen Code...

What did you expect to happen?

версия 0.12.2 работала , версия 0.12.3 не работает. установил версию vs code с 1.111.0 на 1.110.1 все равно не работает

Client information

Client Information

Run qwen to enter the interactive CLI, then run the /about command.

$ qwen /about
# paste output here

Login information

No response

Anything else we need to know?

Версия: 1.110.1 (user setup)
Фиксация: 61b3d0ab13be7dda2389f1d3e60a119c7f660cc3
Дата: 2026-03-06T23:03:27.520Z
Electron: 39.6.0
ElectronBuildId: 13330601
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
ОС: Windows_NT x64 10.0.19045

[yiliang114]

Thanks for reporting this, and sorry you are hitting this after the update.

Since 0.12.2 worked and 0.12.3 does not, this looks like a regression on our side. We want to narrow down whether this is in the VS Code extension startup flow, or whether the underlying CLI/auth flow is also affected.

Could you help us check these points?

1. Outside VS Code, does the standalone Qwen Code CLI still work normally on the same machine?
   For example: can it log in successfully and start a normal session?

2. Do you have any MCP servers configured?
   This includes mcpServers in settings, extension-provided MCP integrations, or previous MCP OAuth setup.

3. If you do have MCP configured, could you temporarily disable all MCP servers and try the VS Code extension again?

4. When the extension gets stuck on Preparing Qwen Code..., is this happening before login, or does it still happen even if you are already logged in?

This will help us determine whether the regression is more likely related to:

• VS Code extension startup / ACP session initialization
• authentication refresh
• or MCP-related initialization blocking

If it is easier, you can reply in a short form like this:

• Standalone CLI: works / does not work
• MCP configured: yes / no
• Disable MCP and retry: fixed / still stuck
• Stuck before login or after login: ___

Thanks again — that should help us narrow this down much faster.

[AndyInjiner]

На версии VSCode 1.111.0 и в версии компаньона 0.12.3
Автономный интерфейс qwen code работает
MCP сервер для Unity - на работу компонента не влияет
Я могу синхронизировать данные м Github но компанент все время Preparing Qwen Code...

[AndyInjiner]

я уже полностью удалил и снова установил vs code и qwen companion но проблема осталась ,Preparing Qwen Code... и не появляется окно авторизации

[yiliang114]

@AndyInjiner Thanks, this is helpful.

Since the standalone Qwen Code CLI still works on the same machine, MCP does not seem to change the behavior, and reinstalling VS Code + Qwen Companion did not help, this looks more like the VS Code Companion is getting stuck somewhere in its startup / pre-login flow rather than the CLI itself failing.

Since the Output panel does not currently show anything useful, could you please check the VS Code Developer Tools console for webview / extension errors?

Steps:

1. In VS Code, press Ctrl + Shift + P
2. Type Toggle Developer Tools
3. Press Enter to open Developer Tools
4. Switch to the Console tab
5. Open Qwen Companion again and reproduce the issue until it gets stuck on Preparing Qwen Code...

If you see any red errors, warnings, or messages related to Qwen Code, webview, or the extension, please either:

• copy and paste them here, or
• send a screenshot

If possible, please include the earliest errors that appear in the console, since those are usually the closest to the root cause.

That should help us determine whether the problem is happening during webview initialization, extension startup, or just before the login window is supposed to open.