What would you like to be added?
The VS Code extension currently only supports Qwen OAuth for authentication, while the CLI offers a richer set of options. We'd like the VS Code extension to provide the same authentication choices and a similarly guided experience — all within the editor.
Current CLI Authentication
The CLI presents a guided auth dialog with three options:
┌─────────────────────────────────────────────┐
│ Select Authentication Method │
│ │
│ ○ Qwen OAuth │
│ Free · Up to 1,000 requests/day │
│ │
│ ○ Alibaba Cloud Coding Plan │
│ Paid · Up to 6,000 requests/5 hrs │
│ │
│ ○ API Key │
│ Bring your own API key │
└─────────────────────────────────────────────┘
Each option leads to a dedicated step-by-step flow (QR code for OAuth, region selection + key input for Coding Plan, settings link for API Key) — all within the terminal.
Current VS Code Authentication
The VS Code extension only supports Qwen OAuth. Users see a "Log In" button, which triggers a browser-based redirect. There is no option for Coding Plan or API Key.
Requested
The VS Code extension should present the same three authentication options in its chat panel, with equivalent guided flows for each method — adapted to VS Code's UI patterns but offering the same choices.
Why is this needed?
-
Consistency: Users who switch between the terminal and VS Code should feel at home in both. Right now, the CLI offers three clear authentication paths, while VS Code only supports one — this creates a fragmented experience.
-
Missing capabilities: Users on the Alibaba Cloud Coding Plan or using their own API keys currently cannot authenticate through the VS Code extension at all. They are forced to use the CLI to set up authentication, which defeats the purpose of having a VS Code integration.
-
Better onboarding: A guided, in-editor authentication flow (with options, region selection, and API key input) removes friction. Users shouldn't have to leave VS Code or read external docs just to get started.
-
Feature parity: The VS Code extension should be a first-class citizen, not a limited wrapper around one auth method. Supporting the full set of authentication options makes it viable for all users, not just those using Qwen OAuth.
Additional context
The CLI currently presents a polished, step-by-step authentication experience with clear descriptions for each option, back-navigation between steps, and helpful links. The VS Code extension should aim to replicate this level of guided UX within its chat panel — adapted to fit VS Code's design patterns (e.g., using webview UI elements rather than terminal-style menus), but offering the same choices and flow.
What would you like to be added?
The VS Code extension currently only supports Qwen OAuth for authentication, while the CLI offers a richer set of options. We'd like the VS Code extension to provide the same authentication choices and a similarly guided experience — all within the editor.
Current CLI Authentication
The CLI presents a guided auth dialog with three options:
Each option leads to a dedicated step-by-step flow (QR code for OAuth, region selection + key input for Coding Plan, settings link for API Key) — all within the terminal.
Current VS Code Authentication
The VS Code extension only supports Qwen OAuth. Users see a "Log In" button, which triggers a browser-based redirect. There is no option for Coding Plan or API Key.
Requested
The VS Code extension should present the same three authentication options in its chat panel, with equivalent guided flows for each method — adapted to VS Code's UI patterns but offering the same choices.
Why is this needed?
Consistency: Users who switch between the terminal and VS Code should feel at home in both. Right now, the CLI offers three clear authentication paths, while VS Code only supports one — this creates a fragmented experience.
Missing capabilities: Users on the Alibaba Cloud Coding Plan or using their own API keys currently cannot authenticate through the VS Code extension at all. They are forced to use the CLI to set up authentication, which defeats the purpose of having a VS Code integration.
Better onboarding: A guided, in-editor authentication flow (with options, region selection, and API key input) removes friction. Users shouldn't have to leave VS Code or read external docs just to get started.
Feature parity: The VS Code extension should be a first-class citizen, not a limited wrapper around one auth method. Supporting the full set of authentication options makes it viable for all users, not just those using Qwen OAuth.
Additional context
The CLI currently presents a polished, step-by-step authentication experience with clear descriptions for each option, back-navigation between steps, and helpful links. The VS Code extension should aim to replicate this level of guided UX within its chat panel — adapted to fit VS Code's design patterns (e.g., using webview UI elements rather than terminal-style menus), but offering the same choices and flow.