Files
791989cdb8 fix(vscode): keep sibling model settings when writing provider config (#15829)
* fix(vscode): keep sibling model settings when writing provider config

Configuring a Coding Plan or a model provider from the panel replaced the
whole settings.model object with { name }, silently dropping keys the CLI
owns: baseUrl, reasoningEffort, maxSessionTurns and the run budgets.

Write name and its paired baseUrl key by key instead, matching the other
sections in the same writer and the CLI's own writers. The baseUrl is
written rather than merely preserved because the resolver's merge invariant
needs a present value (or an empty-string tombstone) to override a stale
one in a lower-priority scope.

Fixes #15822

* test(vscode-companion): pin region and custom-endpoint baseUrl writes

The api-key fixtures reused the fallback literal, so a regression that
dropped the modelProviders lookup kept the suite green; likewise only the
china branch of the Coding Plan model.baseUrl write was pinned. Seed a
custom gateway URL plus an active-model-absent fallback case, and assert
the global region writes its own endpoint.

* test(vscode-companion): pin the api-key install path's model baseUrl

* test(vscode): pin the empty baseUrl tombstone for id-only installs

Subscription install plans select a model by id alone, so the only thing
clearing a stale model.baseUrl is the empty-string tombstone. The existing
install-path cases always pass a baseUrl, leaving the serialization half of
that branch unasserted on disk.

* fix(vscode): take the OpenAI default base URL from the core helper

The active-model write re-spelled https://api.openai.com/v1 while the paired
provider entry and the login flow both go through
getDefaultBaseUrlForProtocol. Moving that default in core would then leave
this path behind, so call the helper instead.

---------

Co-authored-by: 肖洪进 <[email protected]>
Co-authored-by: 2SinceJuly <[email protected]>
Co-authored-by: Shaojin Wen <[email protected]>
2026-11-07 02:34:22 +00:00
..
2025-07-22 23:26:01 +08:00
2026-11-06 18:03:10 +00:00

Qwen Code Companion

Version VS Code Installs Open VSX Downloads Rating

Seamlessly integrate Qwen Code into Visual Studio Code with native IDE features and an intuitive chat interface. This extension bundles everything you need — no additional installation required.

Demo

Features

  • Native IDE experience: Dedicated Qwen Code Chat panel accessed via the Qwen icon in the editor title bar
  • Native diffing: Review, edit, and accept changes in VS Code's diff view
  • Auto-accept edits mode: Automatically apply Qwen's changes as they're made
  • File management: @-mention files or attach files and images using the system file picker
  • Conversation history & multiple sessions: Access past conversations and run multiple sessions simultaneously
  • Open file & selection context: Share active files, cursor position, and selections for more precise help

Requirements

  • Visual Studio Code 1.96.0 or newer (also works with Cursor, Windsurf, and other VS Code-based editors)

Quick Start

  1. Install from the VS Code Marketplace or Open VSX Registry

  2. Open the Chat panel using one of these methods:

    • Click the Qwen icon in the top-right corner of the editor
    • Run Qwen Code: Open from the Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
  3. Start chatting — Ask Qwen to help with coding tasks, explain code, fix bugs, or write new features

Commands

Command Description
Qwen Code: Open Open the Qwen Code Chat panel
Qwen Code: Run Launch a classic terminal session with the bundled CLI
Qwen Code: Accept Current Diff Accept the currently displayed diff
Qwen Code: Close Diff Editor Close/reject the current diff

Feedback & Issues

Contributing

We welcome contributions! See our Contributing Guide for details on:

  • Setting up the development environment
  • Building and debugging the extension locally
  • Submitting pull requests

Terms of Service and Privacy Notice

By installing this extension, you agree to the Terms of Service.

License

Apache-2.0