npm - @qwen-code/qwen-code - Versions diffs - 0.19.0 → 0.19.1-nightly.20260624.a234860a4 - Mend

@qwen-code/qwen-code 0.19.0 → 0.19.1-nightly.20260624.a234860a4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (141) hide show

package/bundled/qc-helper/docs/configuration/settings.md CHANGED Viewed

@@ -88,12 +88,16 @@ Settings are organized into categories. Most settings should be placed within th
 | `general.gitCoAuthor.pr`                   | boolean | Append a Qwen Code attribution line to pull request descriptions when running `gh pr create`.                                                                                                                                                                                                                   | `true`      |
 | `general.defaultFileEncoding`              | string  | Default encoding for new files. Use `"utf-8"` (default) for UTF-8 without BOM, or `"utf-8-bom"` for UTF-8 with BOM. Only change this if your project specifically requires BOM.                                                                                                                                 | `"utf-8"`   |
 | `general.cleanupPeriodDays`                | number  | Days to retain `~/.qwen/file-history/` session backups used by `/rewind`. Backups older than this are removed by a background pass that runs at most once per day. `0` = minimum retention (~1 hour): keeps sessions touched in the last hour plus the currently active one. Changes take effect after restart. | `30`        |
+| `general.language`                         | enum    | Language for the user interface. Use `"auto"` to detect from system settings, or a language code (e.g. `"zh-CN"`, `"fr"`). Custom codes can be added by placing JS locale files in `~/.qwen/locales/`. See [i18n](../features/language). Requires restart.                                                       | `"auto"`    |
+| `general.outputLanguage`                   | string  | Language for model output. Use `"auto"` to detect from system settings, or set a specific language. Requires restart.                                                                                                                                                                                          | `"auto"`    |
+| `general.dynamicCommandTranslation`        | boolean | Enable AI translation of dynamic slash-command descriptions. When disabled, dynamic commands keep their original descriptions and skip translation model calls.                                                                                                                                                | `false`     |
 #### output
 | Setting         | Type   | Description                   | Default  | Possible Values    |
 | --------------- | ------ | ----------------------------- | -------- | ------------------ |
-| `output.format` | string | The format of the CLI output. | `"text"` | `"text"`, `"json"` |
+| `output.format`         | string  | The format of the CLI output.                            | `"text"` | `"text"`, `"json"` |
+| `output.showTimestamps` | boolean | Show an `[HH:MM:SS]` timestamp before each assistant response. | `false`  |                    |
 #### ui
@@ -122,7 +126,6 @@ Settings are organized into categories. Most settings should be placed within th
 | `ui.enableFollowupSuggestions`          | boolean          | Enable [followup suggestions](../features/followup-suggestions) that predict what you want to type next after the model responds. Suggestions appear as placeholder text and are accepted with Tab, Enter, or Right Arrow (which fill the input — they do not auto-submit). On by default; set to `false` to opt out.                                                                                                                                                                                                                              | `true`        |
 | `ui.enableCacheSharing`                 | boolean          | Use cache-aware forked queries for suggestion generation. Reduces cost on providers that support prefix caching (experimental).                                                                                                                                                                                                                                                                                                                                                                                                                    | `true`        |
 | `ui.enableSpeculation`                  | boolean          | Speculatively execute accepted suggestions before submission. Results appear instantly when you accept (experimental).                                                                                                                                                                                                                                                                                                                                                                                                                             | `false`       |
-| `experimental.emitToolUseSummaries`     | boolean          | Generate short LLM-based labels summarizing each tool-call batch. See [Tool-Use Summaries](../features/tool-use-summaries). Requires `fastModel` to be configured; silently skipped otherwise. Can be overridden per-session with `QWEN_CODE_EMIT_TOOL_USE_SUMMARIES=0` or `=1`.                                                                                                                                                                                                                                                                   | `true`        |
 #### ide
@@ -247,7 +250,7 @@ The `extra_body` field allows you to add custom parameters to the request body s
 | `context.fileFiltering.enableRecursiveFileSearch`           | boolean                    | Whether to enable searching recursively for filenames under the current tree when completing `@` prefixes in the prompt.                                                                                                                                                                                                                                              | `true`                          |
 | `context.fileFiltering.enableFuzzySearch`                   | boolean                    | When `true`, enables fuzzy search capabilities when searching for files. Set to `false` to improve performance on projects with a large number of files.                                                                                                                                                                                                              | `true`                          |
 | `context.clearContextOnIdle.toolResultsThresholdMinutes`    | number                     | Minutes of inactivity before clearing old tool result content. Use `-1` to disable the idle trigger.                                                                                                                                                                                                                                                                  | `60`                            |
-| `context.clearContextOnIdle.toolResultsNumToKeep`           | number                     | Number of most-recent compactable tool results to preserve when clearing. Floor at 1.                                                                                                                                                                                                                                                                                 | `5`                             |
+| `context.clearContextOnIdle.toolResultsNumToKeep`           | integer                    | Integer number of most-recent compactable tool results to preserve when clearing. Values below 1 are floored to 1.                                                                                                                                                                                                                                                    | `5`                             |
 | `context.clearContextOnIdle.toolResultsTotalCharsThreshold` | number                     | Total compactable tool result output characters allowed in history before clearing oldest results. Use `-1` to disable the size trigger. This is a soft threshold: protected recent tool results may keep the total above it.                                                                                                                                         | `500000`                        |
 #### Troubleshooting File Search Performance
@@ -460,6 +463,19 @@ LSP server configuration is done through `.lsp.json` files in your project root
 | `advanced.bugCommand`          | object           | Configuration for the bug report command. Overrides the default URL for the `/bug` command. Properties: `urlTemplate` (string): A URL that can contain `{title}` and `{info}` placeholders. Example: `"bugCommand": { "urlTemplate": "https://bug.example.com/new?title={title}&info={info}" }`                                          | `undefined`              |
 | `plansDirectory`               | string           | Custom directory for approved Plan Mode files. Relative paths are resolved from the project root, and the resolved path must stay within the project root. If unset, plan files are stored in `~/.qwen/plans`. **Requires restart.** If the directory is inside the project root, add it to `.gitignore` to avoid committing plan files. | `undefined`              |
+#### experimental
+> [!warning]
+>
+> **Experimental features.** These toggles gate in-development capabilities and may change or be removed in future releases.
+| Setting                             | Type    | Description                                                                                                                                                                                                                                                                | Default |
+| ----------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| `experimental.cron`                 | boolean | Enable in-session cron/loop tools (`cron_create`, `cron_list`, `cron_delete`) so the model can create recurring prompts. Can be disabled via the `QWEN_CODE_DISABLE_CRON=1` environment variable. Requires restart.                                                         | `true`  |
+| `experimental.agentTeam`            | boolean | Enable agent-team collaboration tools (`team_create`, `task_create`, `task_update`, `send_message`, etc.) for multi-agent coordination. Can also be enabled via `QWEN_CODE_ENABLE_AGENT_TEAM=1`. Requires restart.                                                          | `false` |
+| `experimental.artifact`             | boolean | Enable the Artifact tool, letting the model publish a self-contained HTML page and open it in the browser. Interactive, non-SDK sessions only. Toggle via `QWEN_CODE_ENABLE_ARTIFACT=1` / `QWEN_CODE_DISABLE_ARTIFACT=1`. Requires restart.                                 | `false` |
+| `experimental.emitToolUseSummaries` | boolean | Generate a short LLM-based label after each tool-call batch completes. See [Tool-Use Summaries](../features/tool-use-summaries). Requires a fast model to be configured (`fastModel`); silently skipped otherwise. Can be overridden per-session with `QWEN_CODE_EMIT_TOOL_USE_SUMMARIES=0` or `=1`. | `true`  |
 #### mcpServers
 Configures connections to one or more Model-Context Protocol (MCP) servers for discovering and using custom tools. Qwen Code attempts to connect to each configured MCP server to discover available tools. If multiple MCP servers expose a tool with the same name, the tool names will be prefixed with the server alias you defined in the configuration (e.g., `serverAlias__actualToolName`) to avoid conflicts. Note that the system might strip certain schema properties from MCP tool definitions for compatibility. At least one of `command`, `url`, or `httpUrl` must be provided. If multiple are specified, the order of precedence is `httpUrl`, then `url`, then `command`.
@@ -481,7 +497,7 @@ Configures connections to one or more Model-Context Protocol (MCP) servers for d
 #### telemetry
-Configures logging and metrics collection for Qwen Code. For more information, see [telemetry](/developers/development/telemetry).
+Configures logging and metrics collection for Qwen Code. For more information, see [telemetry](../../developers/development/telemetry.md).
 | Setting                                    | Type    | Description                                                                                                                                                                                                                                                                              | Default |
 | ------------------------------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
@@ -641,11 +657,11 @@ For sandbox image selection, precedence is:
 | `--approval-mode`            |       | Sets the approval mode for tool calls.                                                                                                                                                                                                       | `plan`, `default`, `auto-edit`, `auto`, `yolo` | Supported modes: `plan`: Analyze only—do not modify files or execute commands. `default`: Require approval for file edits or shell commands (default behavior). `auto-edit`: Automatically approve edit tools (`edit`, `write_file`, `notebook_edit`) while prompting for others. `auto`: LLM classifier auto-approves safe actions and blocks risky ones. `yolo`: Automatically approve all tool calls (equivalent to `--yolo`). Cannot be used together with `--yolo`. Use `--approval-mode=yolo` instead of `--yolo` for the new unified approach. Example: `qwen --approval-mode auto-edit`<br>See more about [Approval Mode](../features/approval-mode). |
 | `--allowed-tools`            |       | A comma-separated list of tool names that will bypass the confirmation dialog.                                                                                                                                                               | Tool names                                     | Example: `qwen --allowed-tools "Shell(git status)"`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 | `--disabled-slash-commands`  |       | Slash command names to hide/disable (comma-separated or repeated). Unioned with the `slashCommands.disabled` setting and the `QWEN_DISABLED_SLASH_COMMANDS` environment variable. Matched case-insensitively against the final command name. | Command names                                  | Example: `qwen --disabled-slash-commands "auth,mcp,extensions"`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `--telemetry`                |       | Enables [telemetry](/developers/development/telemetry).                                                                                                                                                                                      |                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `--telemetry-target`         |       | Sets the telemetry target.                                                                                                                                                                                                                   |                                                | See [telemetry](/developers/development/telemetry) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| `--telemetry-otlp-endpoint`  |       | Sets the OTLP endpoint for telemetry.                                                                                                                                                                                                        |                                                | See [telemetry](../../developers/development/telemetry) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `--telemetry-otlp-protocol`  |       | Sets the OTLP protocol for telemetry (`grpc` or `http`).                                                                                                                                                                                     |                                                | Defaults to `grpc`. See [telemetry](../../developers/development/telemetry) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `--telemetry-log-prompts`    |       | Enables logging of prompts for telemetry.                                                                                                                                                                                                    |                                                | See [telemetry](../../developers/development/telemetry) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `--telemetry`                |       | Enables [telemetry](../../developers/development/telemetry.md).                                                                                                                                                                              |                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `--telemetry-target`         |       | Sets the telemetry target.                                                                                                                                                                                                                   |                                                | See [telemetry](../../developers/development/telemetry.md) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `--telemetry-otlp-endpoint`  |       | Sets the OTLP endpoint for telemetry.                                                                                                                                                                                                        |                                                | See [telemetry](../../developers/development/telemetry.md) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `--telemetry-otlp-protocol`  |       | Sets the OTLP protocol for telemetry (`grpc` or `http`).                                                                                                                                                                                     |                                                | Defaults to `grpc`. See [telemetry](../../developers/development/telemetry.md) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `--telemetry-log-prompts`    |       | Enables logging of prompts for telemetry.                                                                                                                                                                                                    |                                                | See [telemetry](../../developers/development/telemetry.md) for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | `--acp`                      |       | Enables ACP mode (Agent Client Protocol). Useful for IDE/editor integrations like [Zed](../integration-zed).                                                                                                                                 |                                                | Stable. Replaces the deprecated `--experimental-acp` flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | `--experimental-lsp`         |       | Enables experimental [LSP (Language Server Protocol)](../features/lsp) feature for code intelligence (go-to-definition, find references, diagnostics, etc.).                                                                                 |                                                | Experimental. Requires language servers to be installed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | `--extensions`               | `-e`  | Specifies a list of extensions to use for the session.                                                                                                                                                                                       | Extension names                                | If not provided, all available extensions are used. Use the special term `qwen -e none` to disable all extensions. Example: `qwen -e my-extension -e my-other-extension`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
@@ -694,7 +710,7 @@ Here's a conceptual example of what a context file at the root of a TypeScript p
 This example demonstrates how you can provide general project context, specific coding conventions, and even notes about particular files or components. The more relevant and precise your context files are, the better the AI can assist you. Project-specific context files are highly encouraged to establish conventions and context.
-- **Hierarchical Loading and Precedence:** The CLI implements a hierarchical memory system by loading context files (e.g., `QWEN.md`) from several locations. Content from files lower in this list (more specific) typically overrides or supplements content from files higher up (more general). The exact concatenation order and final context can be inspected using the `/memory show` command. The typical loading order is:
+- **Hierarchical Loading and Precedence:** The CLI implements a hierarchical memory system by loading context files (e.g., `QWEN.md`) from several locations. Content from files lower in this list (more specific) typically overrides or supplements content from files higher up (more general). The exact concatenation order and final context can be inspected from the `/memory` dialog. The typical loading order is:
   1. **Global Context File:**
      - Location: `~/.qwen/<configured-context-filename>` (e.g., `~/.qwen/QWEN.md` in your user home directory).
      - Scope: Provides default instructions for all your projects.
@@ -702,11 +718,11 @@ This example demonstrates how you can provide general project context, specific
      - Location: The CLI searches for the configured context file in the current working directory and then in each parent directory up to either the project root (identified by a `.git` folder) or your home directory.
      - Scope: Provides context relevant to the entire project or a significant portion of it.
 - **Concatenation & UI Indication:** The contents of all found context files are concatenated (with separators indicating their origin and path) and provided as part of the system prompt. The CLI footer displays the count of loaded context files, giving you a quick visual cue about the active instructional context.
-- **Importing Content:** You can modularize your context files by importing other Markdown files using the `@path/to/file.md` syntax. For more details, see the [Memory Import Processor documentation](../configuration/memory).
+- **Importing Content:** You can modularize your context files by importing other Markdown files using the `@path/to/file.md` syntax. For more details, see the [Memory documentation](../features/memory.md).
 - **Commands for Memory Management:**
-  - Use `/memory refresh` to force a re-scan and reload of all context files from all configured locations. This updates the AI's instructional context.
-  - Use `/memory show` to display the combined instructional context currently loaded, allowing you to verify the hierarchy and content being used by the AI.
-  - See the [Commands documentation](../features/commands) for full details on the `/memory` command and its sub-commands (`show` and `refresh`).
+  - Use `/memory` to open the memory management dialog.
+  - Refresh memory from the dialog to re-scan and reload context files from all configured locations.
+  - See the [Commands documentation](../features/commands.md) for full details on the `/memory` command.
 By understanding and utilizing these configuration layers and the hierarchical nature of context files, you can effectively manage the AI's memory and tailor Qwen Code's responses to your specific needs and projects.

package/bundled/qc-helper/docs/configuration/themes.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # Themes
-Qwen Code supports a variety of themes to customize its color scheme and appearance. You can change the theme to suit your preferences via the `/theme` command or `"theme":` configuration setting.
+Qwen Code supports a variety of themes to customize its color scheme and appearance. You can change the theme to suit your preferences via the `/theme` command or the `"ui.theme"` configuration setting.
 ## Available Themes
@@ -13,12 +13,15 @@ Qwen Code comes with a selection of pre-defined themes, which you can list using
   - `Default`
   - `Dracula`
   - `GitHub`
+  - `Qwen Dark`
+  - `Shades Of Purple`
 - **Light Themes:**
   - `ANSI Light`
   - `Ayu Light`
   - `Default Light`
   - `GitHub Light`
   - `Google Code`
+  - `Qwen Light`
   - `Xcode`
 ### Changing Themes
@@ -28,7 +31,7 @@ Qwen Code comes with a selection of pre-defined themes, which you can list using
 3.  Using the arrow keys, select a theme. Some interfaces might offer a live preview or highlight as you select.
 4.  Confirm your selection to apply the theme.
-**Note:** If a theme is defined in your `settings.json` file (either by name or by a file path), you must remove the `"theme"` setting from the file before you can change the theme using the `/theme` command.
+**Note:** If a theme is defined in your `settings.json` file (either by name or by a file path), you must remove the `"ui.theme"` setting from the file before you can change the theme using the `/theme` command.
 ### Theme Persistence
@@ -139,7 +142,7 @@ You can define multiple custom themes by adding more entries to the `customTheme
 In addition to defining custom themes in `settings.json`, you can also load a theme directly from a JSON file by specifying the file path in your `settings.json`. This is useful for sharing themes or keeping them separate from your main configuration.
-To load a theme from a file, set the `theme` property in your `settings.json` to the path of your theme file:
+To load a theme from a file, set the `ui.theme` property in your `settings.json` to the path of your theme file:
 ```json
 {
@@ -175,7 +178,7 @@ The theme file must be a valid JSON file that follows the same structure as a cu
 }
 ```
-**Security Note:** For your safety, Gemini CLI will only load theme files that are located within your home directory. If you attempt to load a theme from outside your home directory, a warning will be displayed and the theme will not be loaded. This is to prevent loading potentially malicious theme files from untrusted sources.
+**Security Note:** For your safety, Qwen Code will only load theme files that are located within your home directory. If you attempt to load a theme from outside your home directory, a warning will be displayed and the theme will not be loaded. This is to prevent loading potentially malicious theme files from untrusted sources.
 ### Example Custom Theme

package/bundled/qc-helper/docs/extension/extension-releasing.md CHANGED Viewed

@@ -75,7 +75,7 @@ To ensure Qwen Code can automatically find the correct release asset for each pl
 Archives must be fully contained extensions and have all the standard requirements - specifically the `qwen-extension.json` file must be at the root of the archive.
-The rest of the layout should look exactly the same as a typical extension, see [extensions.md](extension.md).
+The rest of the layout should look exactly the same as a typical extension, see [introduction.md](./introduction.md).
 #### Example GitHub Actions workflow

package/bundled/qc-helper/docs/extension/introduction.md CHANGED Viewed

@@ -263,7 +263,7 @@ The `qwen-extension.json` file contains the configuration for the extension. The
 - `name`: The name of the extension. This is used to uniquely identify the extension and for conflict resolution when extension commands have the same name as user or project commands. The name should be lowercase or numbers and use dashes instead of underscores or spaces. This is how users will refer to your extension in the CLI. Note that we expect this name to match the extension directory name.
 - `version`: The version of the extension.
-- `mcpServers`: A map of MCP servers to configure. The key is the name of the server, and the value is the server configuration. These servers will be loaded on startup just like MCP servers configured in a [`settings.json` file](./cli/configuration.md). If both an extension and a `settings.json` file configure an MCP server with the same name, the server defined in the `settings.json` file takes precedence.
+- `mcpServers`: A map of MCP servers to configure. The key is the name of the server, and the value is the server configuration. These servers will be loaded on startup just like MCP servers configured in a [`settings.json` file](../configuration/settings.md). If both an extension and a `settings.json` file configure an MCP server with the same name, the server defined in the `settings.json` file takes precedence.
   - Note that all MCP server configuration options are supported except for `trust`.
 - `channels`: A map of custom channel adapters. The key is the channel type name, and the value has an `entry` (path to compiled JS entry point) and optional `displayName`. The entry point must export a `plugin` object conforming to the `ChannelPlugin` interface. See [Channel Plugins](../features/channels/plugins) for a full guide.
 - `contextFileName`: The name of the file that contains the context for the extension. This will be used to load the context from the extension directory. If this property is not used but a `QWEN.md` file is present in your extension directory, then that file will be loaded.
@@ -287,24 +287,12 @@ Extensions can require configuration through settings (such as API keys or crede
 qwen extensions settings set <extension-name> <setting-name> [--scope user|workspace]
 ```
-**List all settings for an extension:**
+**List all settings and current values for an extension:**
 ```bash
 qwen extensions settings list <extension-name>
 ```
-**View current values (user and workspace):**
-```bash
-qwen extensions settings show <extension-name> <setting-name>
-```
-**Remove a setting value:**
-```bash
-qwen extensions settings unset <extension-name> <setting-name> [--scope user|workspace]
-```
 Settings can be configured at two levels:
 - **User level** (default): Settings apply across all projects (`~/.qwen/.env`)
@@ -316,7 +304,7 @@ When Qwen Code starts, it loads all the extensions and merges their configuratio
 ### Custom commands
-Extensions can provide [custom commands](./cli/commands.md#custom-commands) by placing Markdown files in a `commands/` subdirectory within the extension directory. These commands follow the same format as user and project custom commands and use standard naming conventions.
+Extensions can provide [custom commands](../features/commands.md#4-custom-commands) by placing Markdown files in a `commands/` subdirectory within the extension directory. These commands follow the same format as user and project custom commands and use standard naming conventions.
 > **Note:** The command format has been updated from TOML to Markdown. TOML files are deprecated but still supported. You can migrate existing TOML commands using the automatic migration prompt that appears when TOML files are detected.

package/bundled/qc-helper/docs/features/arena.md CHANGED Viewed

@@ -7,7 +7,7 @@
 Agent Arena lets you pit multiple AI models against each other on the same task. Each model runs as a fully independent agent in its own isolated Git worktree, so file operations never interfere. When all agents finish, you compare results and select a winner to merge back into your main workspace.
-Unlike [subagents](/users/features/sub-agents), which delegate focused subtasks within a single session, Arena agents are complete, top-level agent instances — each with its own model, context window, and full tool access.
+Unlike [subagents](./sub-agents.md), which delegate focused subtasks within a single session, Arena agents are complete, top-level agent instances — each with its own model, context window, and full tool access.
 This page covers:
@@ -104,7 +104,7 @@ If you want to inspect the complete reasoning path before deciding, each agent's
 ## Configuration
-Arena behavior can be customized in [settings.json](/users/configuration/settings):
+Arena behavior can be customized in [settings.json](../configuration/settings.md):
 ```json
 {
@@ -215,5 +215,5 @@ Agent Arena is one of several planned multi-agent modes in Qwen Code. **Agent Te
 Explore related approaches for parallel and delegated work:
-- **Lightweight delegation**: [Subagents](/users/features/sub-agents) handle focused subtasks within your session — better when you don't need model comparison
+- **Lightweight delegation**: [Subagents](./sub-agents.md) handle focused subtasks within your session — better when you don't need model comparison
 - **Manual parallel sessions**: Run multiple Qwen Code sessions yourself in separate terminals with [Git worktrees](https://git-scm.com/docs/git-worktree) for full manual control

package/bundled/qc-helper/docs/features/channels/overview.md CHANGED Viewed

@@ -7,7 +7,7 @@ Channels let you interact with a Qwen Code agent from messaging platforms like T
 When you run `qwen channel start`, Qwen Code:
 1. Reads channel configurations from your `settings.json`
-2. Spawns a single agent process using the [Agent Client Protocol (ACP)](../../developers/architecture)
+2. Spawns a single agent process using the [Agent Client Protocol (ACP)](../../../developers/architecture.md)
 3. Connects to each messaging platform and starts listening for messages
 4. Routes incoming messages to the agent and sends responses back to the correct chat

package/bundled/qc-helper/docs/features/channels/plugins.md CHANGED Viewed

@@ -84,4 +84,4 @@ Custom channels automatically support everything built-in channels do:
 ## Building Your Own Channel Plugin
-Want to build a channel plugin for a new platform? See the [Channel Plugin Developer Guide](/developers/channel-plugins) for the `ChannelPlugin` interface, the `Envelope` format, and extension points.
+Want to build a channel plugin for a new platform? See the [Channel Plugin Developer Guide](../../../developers/channel-plugins.md) for the `ChannelPlugin` interface, the `Envelope` format, and extension points.

package/bundled/qc-helper/docs/features/commands.md CHANGED Viewed

@@ -43,10 +43,13 @@ Commands for adjusting interface appearance and work environment.
 | `/clear`             | Clear terminal screen content                                                                                                                                                     | `/clear` (shortcut: `Ctrl+L`)           |
 | `/context`           | Show context window usage breakdown                                                                                                                                               | `/context`                              |
 | → `detail`           | Show per-item context usage breakdown                                                                                                                                             | `/context detail`                       |
+| `/history`           | Control history display preferences and visibility                                                                                                                               | `/history collapse-on-resume`, `/history expand-on-resume`, `/history expand-now` |
 | `/diff`              | Open an interactive diff viewer showing uncommitted changes and per-turn diffs. Use ←/→ to switch between current git diff and individual conversation turns, ↑/↓ to browse files | `/diff`                                 |
 | `/theme`             | Change Qwen Code visual theme                                                                                                                                                     | `/theme`                                |
 | `/vim`               | Turn input area Vim editing mode on/off                                                                                                                                           | `/vim`                                  |
+| `/voice`             | Toggle voice dictation input                                                                                                                                                      | `/voice`, `/voice status`               |
 | `/directory`         | Manage multi-directory support workspace                                                                                                                                          | `/dir add ./src,./tests`                |
+| `/cd`                | Move this session to a new working directory                                                                                                                                      | `/cd ../other-project`                  |
 | `/editor`            | Open dialog to select supported editor                                                                                                                                            | `/editor`                               |
 | `/statusline`        | Open interactive [status line](./status-line.md) preset dialog                                                                                                                    | `/statusline`                           |
 | `/statusline <text>` | Generate a command-mode [status line](./status-line.md) via agent                                                                                                                 | `/statusline show model and git branch` |
@@ -72,6 +75,7 @@ Commands for managing AI tools and models.
 | Command          | Description                                   | Usage Examples                                |
 | ---------------- | --------------------------------------------- | --------------------------------------------- |
 | `/mcp`           | List configured MCP servers and tools         | `/mcp`, `/mcp desc`                           |
+| `/import-config` | Import MCP servers from Claude configs         | `/import-config claude-code`, `/import-config claude-desktop --scope project` |
 | `/tools`         | Display currently available tool list         | `/tools`, `/tools desc`                       |
 | `/skills`        | List and run available skills                 | `/skills`, `/skills <name>`                   |
 | `/plan`          | Switch to plan mode or exit plan mode         | `/plan`, `/plan <task>`, `/plan exit`         |
@@ -81,8 +85,9 @@ Commands for managing AI tools and models.
 | →`auto-edit`     | Automatically approve edits                   | Trusted environment                           |
 | →`auto`          | Classifier-evaluated approval                 | Autonomous sessions with safety guardrails    |
 | →`yolo`          | Automatically approve all                     | Quick prototyping                             |
-| `/model`         | Switch model used in current session          | `/model`                                      |
+| `/model`         | Switch model used in current session          | `/model`, `/model <model-id>` (switch immediately) |
 | `/model --fast`  | Set a lighter model for prompt suggestions    | `/model --fast qwen3-coder-flash`             |
+| `/model --voice` | Set the model used for voice transcription    | `/model --voice <model-id>`                   |
 | `/extensions`    | List all active extensions in current session | `/extensions`                                 |
 | `/memory`        | Open the Memory Manager dialog                | `/memory`                                     |
 | `/remember`      | Save a durable memory                         | `/remember Prefer terse responses`            |

package/bundled/qc-helper/docs/features/headless.md CHANGED Viewed

@@ -406,6 +406,6 @@ These messages keep CI runners alive and let you monitor progress. They do not a
 ## Resources
 - [CLI Configuration](../configuration/settings#command-line-arguments) - Complete configuration guide
-- [Authentication](../configuration/settings#environment-variables-for-api-access) - Setup authentication
+- [Authentication](../configuration/auth.md) - Setup authentication
 - [Commands](../features/commands) - Interactive commands reference
 - [Tutorials](../quickstart) - Step-by-step automation guides

package/bundled/qc-helper/docs/features/mcp.md CHANGED Viewed

@@ -20,7 +20,7 @@ With MCP servers connected, you can ask Qwen Code to:
 Qwen Code loads MCP servers from `mcpServers` in your `settings.json`. You can configure servers either:
 - By editing `settings.json` directly
-- By using `qwen mcp` commands (see [CLI reference](#qwen-mcp-cli))
+- By using `qwen mcp` commands (see [CLI reference](#manage-mcp-servers-with-qwen-mcp))
 ### Add your first server
@@ -30,13 +30,21 @@ Qwen Code loads MCP servers from `mcpServers` in your `settings.json`. You can c
 qwen mcp add --transport http my-server http://localhost:3000/mcp
 ```
-2. Open MCP management dialog to view and manage servers:
+2. Start Qwen Code and open the MCP management dialog to view and manage
+   servers:
 ```bash
-qwen mcp
+qwen
 ```
-3. Restart Qwen Code in the same project (or start it if it wasn’t running yet), then ask the model to use tools from that server.
+Then enter:
+```text
+/mcp
+```
+3. If Qwen Code was already running before you added the server, restart it in
+   the same project. Then ask the model to use tools from that server.
 ## Where configuration is stored (scopes)
@@ -190,8 +198,12 @@ syntax — type `@`, then the server name, a colon, and the resource URI:
 summarize @myserver:file:///docs/spec.md and list the open questions
 ```
-Typing `@myserver:` shows an autocomplete list of that server's resource
-URIs. On submit, the referenced resource is read and its contents are
+Typing `@myserver:` shows an autocomplete list of that server's resources;
+keep typing to filter, matching (case-insensitively) either the resource URI
+or its friendly name/title. You don't have to know a URI by heart — before
+you reach the colon, typing part of a server name also suggests matching
+servers that expose resources, so you can pick one and drill straight into
+its resource list. On submit, the referenced resource is read and its contents are
 appended to your message (text inline, binary blobs as attachments); the
 `@server:uri` reference is preserved in the prompt so the model knows what
 it is looking at. The `server` prefix must match a configured MCP server —
@@ -333,11 +345,15 @@ OAuth configuration properties:
 OAuth tokens are automatically:
-- **Stored securely** in `~/.qwen/mcp-oauth-tokens-v2.json` (AES-256-GCM encrypted), with keychain storage preferred when available
+- **Stored** in `~/.qwen/mcp-oauth-tokens.json` (plaintext, mode 0600) by default. If `QWEN_CODE_FORCE_ENCRYPTED_FILE_STORAGE=true` is set, Qwen Code uses keychain-backed storage where available, or `~/.qwen/mcp-oauth-tokens-v2.json` with AES-256-GCM encryption.
 - **Refreshed** when expired (if refresh tokens are available)
 - **Validated** before each connection attempt
-Use the `/mcp auth` command within Qwen Code to manage OAuth authentication interactively.
+> [!WARNING]
+> By default, OAuth tokens are stored unencrypted on disk. On shared or multi-user machines, set `QWEN_CODE_FORCE_ENCRYPTED_FILE_STORAGE=true` to protect credentials.
+Use the `/mcp` dialog within Qwen Code to inspect MCP servers and manage
+authentication interactively.
 ### Tool filtering (allow/deny tools per server)

package/bundled/qc-helper/docs/features/sandbox.md CHANGED Viewed

@@ -163,7 +163,7 @@ If you want to restrict outbound network access to an allowlist, you can run a l
 This is especially useful with `*-proxied` Seatbelt profiles.
-For a working allowlist-style proxy example, see: [Example Proxy Script](/developers/examples/proxy-script).
+For a working allowlist-style proxy example, see: [Example Proxy Script](../../developers/examples/proxy-script.md).
 ## Linux UID/GID handling
@@ -210,7 +210,7 @@ Then rebuild the sandbox image:
 QWEN_SANDBOX=docker BUILD_SANDBOX=1 qwen -s
 ```
-For more details on customizing the sandbox, see [Customizing the sandbox environment](/developers/tools/sandbox).
+For more details on customizing the sandbox, see [Customizing the sandbox environment](../../developers/tools/sandbox.md).
 **Network issues**

package/bundled/qc-helper/docs/features/tool-use-summaries.md CHANGED Viewed

@@ -174,5 +174,5 @@ If you do not want the extra cost, turn the feature off via `experimental.emitTo
 ## Related
-- [Compact Mode](../configuration/settings#ui.compactMode) — toggle with `Ctrl+O`; the summary replaces the generic tool-group header when compact mode is on.
+- [Compact Mode](../configuration/settings#ui) — toggle with `Ctrl+O`; the summary replaces the generic tool-group header when compact mode is on.
 - [Followup Suggestions](./followup-suggestions) — another fast-model-driven UX enhancement that shares the same `fastModel` setting.

package/bundled/qc-helper/docs/integration-github-action.md CHANGED Viewed

@@ -96,7 +96,7 @@ This workflow acts as a central dispatcher for Qwen Code CLI, routing requests t
 ### Issue Triage
-This action can be used to triage GitHub Issues automatically or on a schedule. For a detailed guide on how to set up the issue triage system, go to the [GitHub Issue Triage workflow documentation](./examples/workflows/issue-triage).
+This action can be used to triage GitHub Issues automatically or on a schedule. For a working issue triage setup, see the [automated issue triage workflow](https://github.com/QwenLM/qwen-code/blob/main/.github/workflows/qwen-automated-issue-triage.yml).
 ### Pull Request Review
@@ -208,7 +208,7 @@ The Qwen Code CLI can be extended with additional functionality through extensio
 These extensions are installed from source from their GitHub repositories.
 For detailed instructions on how to set up and configure extensions, go to the
-[Extensions documentation](../developers/extensions/extension).
+[Extensions documentation](./extension/introduction.md).
 ## Best Practices

package/bundled/qc-helper/docs/overview.md CHANGED Viewed

@@ -40,7 +40,7 @@ cd your-project
 qwen
 ```
-Choose your authentication method — **API Key** or **[Alibaba Cloud Coding Plan](https://bailian.console.aliyun.com/cn-beijing/?tab=coding-plan#/efm/coding-plan-index)** ([intl](https://modelstudio.console.alibabacloud.com/?tab=coding-plan#/efm/coding-plan-index)) — and follow the prompts to configure. See the API setup guide ([Beijing](https://bailian.console.aliyun.com/cn-beijing/?tab=doc#/doc/?type=model&url=3023091) / [intl](https://modelstudio.console.alibabacloud.com/ap-southeast-1?tab=doc#/doc/?type=model&url=2974721)) for step-by-step instructions. Then let's start with understanding your codebase. Try one of these commands:
+On first launch you'll be prompted to connect a model provider. The menu offers **Alibaba ModelStudio** (Coding Plan, Token Plan, or Standard API Key), **Third-party Providers** (built-in providers such as DeepSeek, MiniMax, Z.AI, and OpenRouter, connected with an API key), and **Custom Provider** (a local server, proxy, or unsupported provider). For the [Alibaba Cloud Coding Plan](https://bailian.console.aliyun.com/cn-beijing/?tab=coding-plan#/efm/coding-plan-index) ([intl](https://modelstudio.console.alibabacloud.com/?tab=coding-plan#/efm/coding-plan-index)), choose **Alibaba ModelStudio → Coding Plan**; to use a ModelStudio API key, choose **Alibaba ModelStudio → Standard API Key** and follow the API setup guide ([Beijing](https://bailian.console.aliyun.com/cn-beijing/?tab=doc#/doc/?type=model&url=3023091) / [intl](https://modelstudio.console.alibabacloud.com/ap-southeast-1?tab=doc#/doc/?type=model&url=2974721)). Then let's start with understanding your codebase. Try one of these commands:
 ```
 what does this project do?

package/bundled/qc-helper/docs/quickstart.md CHANGED Viewed

@@ -10,7 +10,7 @@ Make sure you have:
 - A **terminal** or command prompt open
 - A code project to work with
-- An API key from Alibaba Cloud Model Studio ([Beijing](https://bailian.console.aliyun.com/) / [intl](https://modelstudio.console.alibabacloud.com/)), or an Alibaba Cloud Coding Plan ([Beijing](https://bailian.console.aliyun.com/cn-beijing/?tab=coding-plan#/efm/coding-plan-index) / [intl](https://modelstudio.console.alibabacloud.com/?tab=coding-plan#/efm/coding-plan-index)) subscription
+- An API key from Alibaba Cloud ModelStudio ([Beijing](https://bailian.console.aliyun.com/) / [intl](https://modelstudio.console.alibabacloud.com/)), or an Alibaba Cloud Coding Plan ([Beijing](https://bailian.console.aliyun.com/cn-beijing/?tab=coding-plan#/efm/coding-plan-index) / [intl](https://modelstudio.console.alibabacloud.com/?tab=coding-plan#/efm/coding-plan-index)) subscription
 ## Step 1: Install Qwen Code
@@ -66,10 +66,14 @@ qwen
 /auth
 ```
-Choose your preferred authentication method:
+The first-run menu lets you connect a model provider. Choose one of:
-- **Alibaba Cloud Coding Plan**: Select `Alibaba Cloud Coding Plan` for a fixed monthly fee with diverse model options. See the [Coding Plan guide](https://bailian.console.aliyun.com/cn-beijing/?tab=coding-plan#/efm/coding-plan-index) ([intl](https://modelstudio.console.alibabacloud.com/?tab=coding-plan#/efm/coding-plan-index)) for setup instructions.
-- **API Key**: Select `API Key`, then enter your API key from Alibaba Cloud Model Studio ([Beijing](https://bailian.console.aliyun.com/) / [intl](https://modelstudio.console.alibabacloud.com/)). See the API setup guide ([Beijing](https://bailian.console.aliyun.com/cn-beijing/?tab=doc#/doc/?type=model&url=3023091) / [intl](https://modelstudio.console.alibabacloud.com/ap-southeast-1?tab=doc#/doc/?type=model&url=2974721)) for details.
+- **Alibaba ModelStudio** — the recommended setup. Opens a sub-menu:
+  - **Coding Plan**: for individual developers, with an included weekly quota and diverse model options. See the [Coding Plan guide](https://bailian.console.aliyun.com/cn-beijing/?tab=coding-plan#/efm/coding-plan-index) ([intl](https://modelstudio.console.alibabacloud.com/?tab=coding-plan#/efm/coding-plan-index)) for setup instructions.
+  - **Token Plan**: usage-based billing with a dedicated endpoint, aimed at teams and companies.
+  - **Standard API Key**: connect with an existing API key from Alibaba Cloud ModelStudio ([Beijing](https://bailian.console.aliyun.com/) / [intl](https://modelstudio.console.alibabacloud.com/)). See the API setup guide ([Beijing](https://bailian.console.aliyun.com/cn-beijing/?tab=doc#/doc/?type=model&url=3023091) / [intl](https://modelstudio.console.alibabacloud.com/ap-southeast-1?tab=doc#/doc/?type=model&url=2974721)) for details.
+- **Third-party Providers** — choose a built-in provider (DeepSeek, MiniMax, Z.AI, ModelScope, OpenRouter, Requesty, and more) and connect with an API key.
+- **Custom Provider** — manually connect a local server, proxy, or unsupported provider.
 > ⚠️ **Note**: Qwen OAuth was discontinued on April 15, 2026. If you were previously using Qwen OAuth, please switch to one of the methods above.
@@ -86,7 +90,7 @@ Choose your preferred authentication method:
 Open your terminal in any project directory and start Qwen Code:
 ```bash
-# optiona
+# optional
 cd /path/to/your/project
 # start qwen
 qwen

package/bundled/qc-helper/docs/qwen-serve.md CHANGED Viewed

@@ -87,7 +87,11 @@ operators: `GET /daemon/status`, `GET /workspace/mcp`,
 `GET /workspace/skills`, `GET /workspace/providers`, `GET /workspace/env`,
 `GET /workspace/preflight`,
 `GET /session/:id/context`, `GET /session/:id/supported-commands`, and
-`GET /session/:id/tasks`.
+`GET /session/:id/tasks`, and `GET /session/:id/lsp`.
+`GET /session/:id/lsp` returns structured per-session LSP status. Start the
+daemon with `--experimental-lsp` to enable LSP in spawned agent sessions;
+otherwise the route returns `enabled: false` with no servers.
 `GET /daemon/status` is the consolidated troubleshooting snapshot. The default
 `detail=summary` reads only in-memory daemon state (sessions, permissions,
@@ -234,7 +238,7 @@ The token comparison is constant-time (SHA-256 + `crypto.timingSafeEqual`); 401
 | `--http-bridge`                         | `true`          | Stage 1 mode: one `qwen --acp` child per daemon (bound to one workspace at boot, per [#3803](https://github.com/QwenLM/qwen-code/issues/3803) §02); N sessions multiplex onto that child via ACP `newSession()`. Stage 2 native in-process becomes available later.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | `--allow-origin <pat>`                  | —               | T2.4 ([#4514](https://github.com/QwenLM/qwen-code/issues/4514)). Cross-origin allowlist for browser webui clients. Repeatable. Each value is `*` (any origin — boot refuses if no bearer token is configured; `--require-auth` on loopback is recommended so `/health` and `/demo` are also bearer-gated, since both are pre-auth on loopback by default) or a canonical URL origin (`<scheme>://<host>[:<port>]`, no trailing slash / path / userinfo / query). **Subdomain wildcards (`https://*.example.com`) are intentionally unsupported** — list each subdomain explicitly, or use `*` with a configured token (and `--require-auth` for full hardening). Matched origins receive CORS response headers (`Access-Control-Allow-Origin`, `Vary: Origin`, methods, headers, max-age, and exposed `Retry-After`); unmatched origins still get a 403 with the same envelope as today's wall. `Origin: null` (sandboxed iframes, file:// docs) is always rejected, even under `*`. Pre-flight via `caps.features.allow_origin`. Loopback self-origin hits are unaffected. |
 | `--web` / `--no-web`                    | `true`          | Serve the built Web Shell SPA at the daemon root (`GET /`, `/assets/*`, and SPA deep-link fallback). The static shell is registered **before** the bearer-auth gate — a browser can't attach a token to a `<script>` subresource or an address-bar navigation, the shell carries no secrets, and every API route stays token-gated regardless. On non-loopback binds a one-line stderr warning notes the UI is reachable without auth. Use `--no-web` for an API-only daemon. No effect when the build omits the Web Shell assets (the daemon logs a breadcrumb and runs API-only).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `--open`                                | `false`         | After the listener is up, open the Web Shell in your default browser at the daemon URL (with `#token=` appended as a URL fragment when a token is configured — a fragment is never sent to the server, keeping the token out of access logs and Referer headers). No-op with `--no-web`, or in headless / CI / SSH environments where no browser is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `--open`                                | `false`         | After the listener is up, open the Web Shell in your default browser at the daemon URL (with `#token=` appended as a URL fragment when a token is configured — a fragment is never sent to the server, keeping the token out of access logs and Referer headers). No-op with `--no-web`, or in headless / CI / SSH environments where no browser is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 > **Sizing the load knobs.** `--max-sessions` is the **new-child** cap.
 > Three other layers also limit load — when sizing for a high-concurrency
@@ -461,7 +465,15 @@ The bridge keeps **one channel per daemon** (one daemon per workspace, per §02)
 ## Logging in to a remote daemon (issue #4175 PR 21)
-When the daemon runs on a remote pod (no shared display with you), you can still log in to a Qwen account by triggering an OAuth device flow over HTTP. The daemon polls the IdP itself; your job is just to open a URL on whatever device has a browser.
+When the daemon runs on a remote pod (no shared display with you), a client can
+trigger an OAuth device flow over HTTP. The daemon polls the IdP itself; your job
+is just to open a URL on whatever device has a browser.
+> [!note]
+>
+> Qwen OAuth free tier was discontinued on 2026-04-15. The `qwen-oauth`
+> examples below document the device-flow protocol shape and legacy provider
+> identifier; new setups should use a currently supported auth provider.
 ```bash
 # 1. Start a flow. The daemon contacts the IdP, returns a code + URL.

package/bundled/qc-helper/docs/support/tos-privacy.md CHANGED Viewed

@@ -109,4 +109,4 @@ You can switch between Qwen OAuth, Alibaba Cloud Coding Plan, and your own API k
 2. **Within the CLI**: Use the `/auth` command to reconfigure your authentication method
 3. **Environment variables**: Set up `.env` files for automatic API key authentication
-For detailed instructions, see the [Authentication Setup](../configuration/settings#environment-variables-for-api-access) documentation.
+For detailed instructions, see the [Authentication Setup](../configuration/auth.md) documentation.