@qwen-code/qwen-code 0.19.3-nightly.20260701.a974594d7 → 0.19.4

package/bundled/loop/loop-tick-resolver.test.ts

@@ -649,6 +649,48 @@ describe('LoopTickResolver', () => {
     }
   });
 
+  it('homeLoopLabel uses forward slashes for Windows tilde labels under the real home', async () => {
+    const prevQwenHome = process.env['QWEN_HOME'];
+    delete process.env['QWEN_HOME'];
+    vi.resetModules();
+    vi.doMock('node:path', async (importActual) => {
+      const actual = await importActual<typeof import('node:path')>();
+      return {
+        ...actual.win32,
+        default: actual.win32,
+        posix: actual.posix,
+        win32: actual.win32,
+      };
+    });
+    vi.doMock('node:os', async (importActual) => {
+      const actual = await importActual<typeof import('node:os')>();
+      return {
+        ...actual,
+        default: { ...actual, homedir: () => 'C:\\Users\\runneradmin' },
+        homedir: () => 'C:\\Users\\runneradmin',
+      };
+    });
+    try {
+      const { LoopTickResolver: WindowsPathResolver } = await import(
+        './loop-tick-resolver.js'
+      );
+      const windowsPathResolver = new WindowsPathResolver({
+        projectRoot: 'C:\\project',
+        homeDir: 'C:\\Users\\runneradmin',
+        homeQwenDir: 'C:\\Users\\runneradmin\\.qwen-loop',
+        allowProjectFile: () => true,
+      });
+
+      expect(windowsPathResolver.homeLoopLabel()).toBe('~/.qwen-loop/loop.md');
+    } finally {
+      vi.doUnmock('node:path');
+      vi.doUnmock('node:os');
+      vi.resetModules();
+      if (prevQwenHome === undefined) delete process.env['QWEN_HOME'];
+      else process.env['QWEN_HOME'] = prevQwenHome;
+    }
+  });
+
   it('re-expands after delete→recreate even when the recreated content is identical', async () => {
     await writeProject('- same tasks');
     expect((await resolver.resolve('dynamic')).full).toBe(true);

package/bundled/loop/loop-tick-resolver.ts

@@ -276,7 +276,7 @@ export class LoopTickResolver {
 
     const tildeified = tildeifyPath(homeLoopPath);
     if (tildeified !== homeLoopPath) {
-      return tildeified;
+      return tildeified.replace(/\\/g, '/');
     }
     // Outside $HOME: tildeifyPath was a no-op. When $QWEN_HOME relocated the
     // global dir (homeQwenDir is its resolved value), report the literal env-var

package/bundled/qc-helper/docs/configuration/auth.md

@@ -165,7 +165,7 @@ The key concept is **Model Providers** (`modelProviders`): Qwen Code supports mu
 
 | Protocol          | `modelProviders` key | Environment variables                                                                                | Providers                                                                                             |
 | ----------------- | -------------------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| OpenAI-compatible | `openai`             | `OPENAI_API_KEY`, `OPENAI_BASE_URL`, `OPENAI_MODEL`                                                  | OpenAI, Azure OpenAI, OpenRouter, Requesty, ModelScope, Alibaba Cloud, any OpenAI-compatible endpoint |
+| OpenAI-compatible | `openai`             | `OPENAI_API_KEY`, `OPENAI_BASE_URL`, `OPENAI_MODEL` (alias: `QWEN_MODEL`)                            | OpenAI, Azure OpenAI, OpenRouter, Requesty, ModelScope, Alibaba Cloud, any OpenAI-compatible endpoint |
 | Anthropic         | `anthropic`          | `ANTHROPIC_API_KEY`, `ANTHROPIC_BASE_URL`, `ANTHROPIC_MODEL`                                         | Anthropic Claude                                                                                      |
 | Google GenAI      | `gemini`             | `GEMINI_API_KEY`, `GEMINI_MODEL`                                                                     | Google Gemini                                                                                         |
 | Vertex AI         | `vertex-ai`          | `GOOGLE_API_KEY`, `GOOGLE_MODEL` (sets `GOOGLE_GENAI_USE_VERTEXAI=true`; uses the `gemini` protocol) | Google Vertex AI                                                                                      |

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

@@ -91,6 +91,9 @@ Settings are organized into categories. Most settings should be placed within th
 | `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`     |
+| `general.terminalBell`                     | boolean | Play a terminal bell sound when a response completes or needs approval.                                                                                                                                                                                                                                         | `true`      |
+| `general.preventSystemSleep`               | boolean | Prevent the system from sleeping while Qwen Code is streaming a model response or executing tools. Idle prompt time and permission prompts do not inhibit sleep. Read once at startup, so changes take effect after restart.                                                                                    | `true`      |
+| `general.chatRecording`                    | boolean | Save chat history to disk. Disabling this also prevents `--continue` and `--resume` from working. Requires restart.                                                                                                                                                                                             | `true`      |
 
 #### output
 
@@ -127,6 +130,12 @@ 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`       |
+| `ui.showStatusInTitle`                  | boolean          | Show the Qwen Code session name and status in the terminal window title.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | `true`        |
+| `ui.disableWorkflowKeywordTrigger`      | boolean          | When `true`, mentioning the word `workflow` in a prompt no longer softly steers the turn toward the Workflow tool (and the Footer `workflow active` indicator is suppressed). Only applies when workflows are enabled.                                                                                                                                                                                                                                                                                                                             | `false`       |
+| `ui.enableUserFeedback`                 | boolean          | Show an optional feedback dialog after conversations to help improve Qwen performance.                                                                                                                                                                                                                                                                                                                                                                                                                                                             | `true`        |
+| `ui.compactInline`                      | boolean          | Compact tool display within each group instead of merging across groups. Requires `ui.compactMode` to be enabled. Requires restart.                                                                                                                                                                                                                                                                                                                                                                                                                | `false`       |
+| `ui.useTerminalBuffer`                  | boolean          | Render conversation history in an in-app scrollable viewport instead of the terminal scrollback buffer. Recommended if you see flicker, scroll-storm, or interface freeze on long sessions. Scroll with `Shift+↑/↓` (line), `PgUp`/`PgDn` (page), `Ctrl+Home/End` (top/bottom), or the mouse wheel. Does not use the host terminal scrollback while enabled; hold `Shift` (or `Option` on macOS) while dragging for native text selection.                                                                                                         | `false`       |
+| `ui.hideBuiltinWorktreeIndicator`       | boolean          | Hide the built-in `⎇ worktree-<branch> (<slug>)` line in the Footer. The worktree state is still passed to custom statusline scripts via the stdin payload. Keep at the default unless your custom statusline renders the worktree itself.                                                                                                                                                                                                                                                                                                         | `false`       |
 
 #### ide
 
@@ -278,6 +287,7 @@ If you are experiencing performance issues with file searching (e.g., with `@` c
 | `tools.truncateToolOutputLines`       | number            | Maximum lines or entries kept when truncating tool output. Applies to Shell, Grep, Glob, ReadFile and ReadManyFiles tools.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | `1000`      | Requires restart: Yes                                                                                                                                                                                                                                                                                                       |
 | `tools.computerUse.enabled`           | boolean           | Enable the built-in Computer Use tools (cua-driver native desktop automation). When `true` (default), the `computer_use__*` tools are registered as deferred built-ins; the first invocation downloads the pinned, signed cua-driver binary into `~/.qwen/computer-use/` and walks through macOS Accessibility / Screen Recording permissions.                                                                                                                                                                                                                                                                                                                                                                                                       | `true`      | Requires restart: Yes                                                                                                                                                                                                                                                                                                       |
 | `tools.computerUse.maxImageDimension` | number            | Longest-edge pixel cap applied to cua-driver screenshots (via `set_config`'s `max_image_dimension`). `-1` (default) keeps cua-driver's built-in default (1568); `0` disables resizing (full resolution); a positive value caps the longest edge. Lower caps cut vision-token cost at the expense of fine detail.                                                                                                                                                                                                                                                                                                                                                                                                                                     | `-1`        | Requires restart: Yes. Env override: `QWEN_COMPUTER_USE_MAX_IMAGE_DIMENSION` (a non-negative integer; takes precedence over this setting)                                                                                                                                                                                   |
+| `tools.toolSearch.enabled`            | boolean           | Load MCP tools on demand via ToolSearch to reduce prompt size. Disable this for models that rely on prefix-based KV caching (e.g. DeepSeek) to keep the prompt prefix stable and maximize cache hit rates.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | `true`      | Requires restart: Yes                                                                                                                                                                                                                                                                                                       |
 
 > [!note]
 >
@@ -285,12 +295,14 @@ If you are experiencing performance issues with file searching (e.g., with `@` c
 
 #### memory
 
-| Setting                          | Type    | Description                                                                                                                    | Default |
-| -------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------ | ------- |
-| `memory.enableManagedAutoMemory` | boolean | Enable background extraction of memories from conversations.                                                                   | `true`  |
-| `memory.enableManagedAutoDream`  | boolean | Enable automatic consolidation (deduplication and cleanup) of collected memories.                                              | `true`  |
-| `memory.enableAutoSkill`         | boolean | Enable background review for reusable project skills after tool-heavy sessions.                                                | `true`  |
-| `memory.autoSkillConfirm`        | boolean | Ask for confirmation before auto-generated skills are added to the skill library. When off, auto-skills are saved immediately. | `true`  |
+| Setting                          | Type    | Description                                                                                                                                                                                           | Default |
+| -------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| `memory.enableManagedAutoMemory` | boolean | Enable background extraction of memories from conversations.                                                                                                                                          | `true`  |
+| `memory.enableManagedAutoDream`  | boolean | Enable automatic consolidation (deduplication and cleanup) of collected memories.                                                                                                                     | `true`  |
+| `memory.enableAutoSkill`         | boolean | Enable background review for reusable project skills after tool-heavy sessions.                                                                                                                       | `true`  |
+| `memory.autoSkillConfirm`        | boolean | Ask for confirmation before auto-generated skills are added to the skill library. When off, auto-skills are saved immediately.                                                                        | `true`  |
+| `memory.enableTeamMemory`        | boolean | Enable a project memory tier shared with collaborators via the git-tracked `.qwen/team-memory/` directory. Writes to it are secret-scanned and reviewable in the git diff.                            | `false` |
+| `memory.enableTeamMemorySync`    | boolean | When team memory is enabled, automatically commit, fast-forward-pull, and push the `.qwen/team-memory/` directory at session start so collaborators stay in sync. Requires a configured git upstream. | `false` |
 
 See [Memory](../features/memory) for details on how auto-memory works and how to use the `/memory`, `/remember`, and `/dream` commands.
 
@@ -424,11 +436,11 @@ execute when typed.
 
 #### mcp
 
-| Setting             | Type             | Description                                                                                                                                                                                                                                                                  | Default     |
-| ------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
-| `mcp.serverCommand` | string           | Command to start an MCP server.                                                                                                                                                                                                                                              | `undefined` |
-| `mcp.allowed`       | array of strings | An allowlist of MCP servers to allow. Allows you to specify a list of MCP server names that should be made available to the model. This can be used to restrict the set of MCP servers to connect to. Note that this will be ignored if `--allowed-mcp-server-names` is set. | `undefined` |
-| `mcp.excluded`      | array of strings | A denylist of MCP servers to exclude. A server listed in both `mcp.excluded` and `mcp.allowed` is excluded. Note that this will be ignored if `--allowed-mcp-server-names` is set.                                                                                           | `undefined` |
+| Setting             | Type             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                 | Default     |
+| ------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| `mcp.serverCommand` | string           | Command to start an MCP server.                                                                                                                                                                                                                                                                                                                                                                                                             | `undefined` |
+| `mcp.allowed`       | array of strings | An allowlist of MCP servers to allow. Allows you to specify a list of MCP server names that should be made available to the model. This can be used to restrict the set of MCP servers to connect to. Supports glob patterns (`*` matches any sequence, `?` matches a single character — e.g. `"*puppeteer*"`); entries without glob characters are matched exactly. Note that this will be ignored if `--allowed-mcp-server-names` is set. | `undefined` |
+| `mcp.excluded`      | array of strings | A denylist of MCP servers to exclude. A server listed in both `mcp.excluded` and `mcp.allowed` is excluded. Supports glob patterns (`*`, `?`) the same way as `mcp.allowed`. Note that this will be ignored if `--allowed-mcp-server-names` is set.                                                                                                                                                                                         | `undefined` |
 
 > [!note]
 >

package/bundled/qc-helper/docs/features/approval-mode.md

@@ -300,6 +300,9 @@ reason inline and decide whether to switch to Ask Permissions Mode for that step
         "deny": ["Any network call to intranet.example.com"],
       },
       "environment": ["Open-source monorepo; commits are signed"],
+      // Optional: route ALL shell commands (including read-only ones like
+      // ls, cat) through the classifier for defense-in-depth.
+      // "classifyAllShell": true,
     },
   },
 }

package/bundled/qc-helper/docs/features/auto-mode.md

@@ -43,6 +43,14 @@ The classifier uses your configured fast model
 (`/model --fast`). If no fast model is configured, the main session
 model is used instead.
 
+> [!tip]
+>
+> Shell commands that the permission system detects as read-only (e.g.
+> `ls`, `cat`, `git log`) are auto-approved before reaching the
+> classifier. Set `permissions.autoMode.classifyAllShell: true` to
+> override this and route all shell commands through the classifier —
+> see [Classify all shell commands](#classify-all-shell-commands) below.
+
 ## Hard rules still win
 
 Auto Mode does **not** replace hard permission rules. Before the classifier
@@ -145,6 +153,38 @@ To keep the classifier system prompt small:
 way other permission settings are: arrays are concatenated and
 de-duplicated.
 
+### Classify all shell commands
+
+By default, read-only shell commands (`ls`, `cat`, `git status`, …) are
+auto-approved without invoking the classifier — the permission system
+detects them as safe at layer 3 and skips the classifier entirely. Set
+`classifyAllShell` to `true` to force **every** shell command through
+the classifier, including read-only ones:
+
+```json
+{
+  "permissions": {
+    "autoMode": {
+      "classifyAllShell": true
+    }
+  }
+}
+```
+
+This is useful for production or high-security environments where you
+want defense-in-depth: even seemingly harmless commands are reviewed by
+the classifier before execution. The trade-off is added latency (~300ms
+per read-only shell call) and reliance on classifier availability — if
+the classifier API is unreachable, read-only shell commands will also be
+blocked (fail-closed).
+
+> [!note]
+>
+> `classifyAllShell` only affects shell commands (`run_shell_command` and
+> `monitor`). Built-in read-only tools (`read_file`, `grep_search`,
+> `glob`, `list_directory`, etc.) are unaffected and still use the
+> fast-path allowlist.
+
 ## Reading the decision
 
 When the classifier blocks an action, the tool call fails with one of

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

@@ -47,24 +47,25 @@ Channels are configured under the `channels` key in `settings.json`. Each channe
 
 ### Options
 
-| Option                   | Required | Description                                                                                                                                    |
-| ------------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `type`                   | Yes      | Channel type: `telegram`, `weixin`, `qq`, `dingtalk`, `feishu`, or a custom type from an extension (see [Plugins](./plugins))                  |
-| `token`                  | Telegram | Bot token. Supports `$ENV_VAR` syntax to read from environment variables. Not needed for WeChat or DingTalk                                    |
-| `clientId`               | DingTalk | DingTalk AppKey. Supports `$ENV_VAR` syntax                                                                                                    |
-| `clientSecret`           | DingTalk | DingTalk AppSecret. Supports `$ENV_VAR` syntax                                                                                                 |
-| `model`                  | No       | Model to use for this channel (e.g., `qwen3.5-plus`). Overrides the default model. Useful for multimodal models that support image input       |
-| `senderPolicy`           | No       | Who can talk to the bot: `allowlist` (default), `open`, or `pairing`                                                                           |
-| `allowedUsers`           | No       | List of user IDs allowed to use the bot (used by `allowlist` and `pairing` policies)                                                           |
-| `sessionScope`           | No       | How sessions are scoped: `user` (default), `thread`, or `single`                                                                               |
-| `cwd`                    | No       | Working directory for the agent. Defaults to the current directory                                                                             |
-| `instructions`           | No       | Custom instructions prepended to the first message of each session                                                                             |
-| `groupPolicy`            | No       | Group chat access: `disabled` (default), `allowlist`, or `open`. See [Group Chats](#group-chats)                                               |
-| `groups`                 | No       | Per-group settings. Keys are group chat IDs or `"*"` for defaults. See [Group Chats](#group-chats)                                             |
-| `dispatchMode`           | No       | What happens when you send a message while the bot is busy: `steer` (default), `collect`, or `followup`. See [Dispatch Modes](#dispatch-modes) |
-| `blockStreaming`         | No       | Progressive response delivery: `on` or `off` (default). See [Block Streaming](#block-streaming)                                                |
-| `blockStreamingChunk`    | No       | Chunk size bounds: `{ "minChars": 400, "maxChars": 1000 }`. See [Block Streaming](#block-streaming)                                            |
-| `blockStreamingCoalesce` | No       | Idle flush: `{ "idleMs": 1500 }`. See [Block Streaming](#block-streaming)                                                                      |
+| Option                   | Required | Description                                                                                                                                                            |
+| ------------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type`                   | Yes      | Channel type: `telegram`, `weixin`, `qq`, `dingtalk`, `feishu`, or a custom type from an extension (see [Plugins](./plugins))                                          |
+| `token`                  | Telegram | Bot token. Supports `$ENV_VAR` syntax to read from environment variables. Not needed for WeChat or DingTalk                                                            |
+| `clientId`               | DingTalk | DingTalk AppKey. Supports `$ENV_VAR` syntax                                                                                                                            |
+| `clientSecret`           | DingTalk | DingTalk AppSecret. Supports `$ENV_VAR` syntax                                                                                                                         |
+| `model`                  | No       | Model to use for this channel (e.g., `qwen3.5-plus`). Overrides the default model. Useful for multimodal models that support image input                               |
+| `senderPolicy`           | No       | Who can talk to the bot: `allowlist` (default), `open`, or `pairing`                                                                                                   |
+| `allowedUsers`           | No       | List of user IDs allowed to use the bot (used by `allowlist` and `pairing` policies)                                                                                   |
+| `sessionScope`           | No       | How sessions are scoped: `user` (default), `thread`, or `single`                                                                                                       |
+| `cwd`                    | No       | Working directory for the agent. Defaults to the current directory                                                                                                     |
+| `instructions`           | No       | Custom instructions prepended to the first message of each session                                                                                                     |
+| `groupPolicy`            | No       | Group chat access: `disabled` (default), `allowlist`, or `open`. See [Group Chats](#group-chats)                                                                       |
+| `groupHistoryLimit`      | No       | Opt-in group history backfill. `0` or omitted disables it. A positive number persists that many authorized, unmentioned group messages for the next bot mention/reply. |
+| `groups`                 | No       | Per-group settings. Keys are group chat IDs or `"*"` for defaults. See [Group Chats](#group-chats)                                                                     |
+| `dispatchMode`           | No       | What happens when you send a message while the bot is busy: `steer` (default), `collect`, or `followup`. See [Dispatch Modes](#dispatch-modes)                         |
+| `blockStreaming`         | No       | Progressive response delivery: `on` or `off` (default). See [Block Streaming](#block-streaming)                                                                        |
+| `blockStreamingChunk`    | No       | Chunk size bounds: `{ "minChars": 400, "maxChars": 1000 }`. See [Block Streaming](#block-streaming)                                                                    |
+| `blockStreamingCoalesce` | No       | Idle flush: `{ "idleMs": 1500 }`. See [Block Streaming](#block-streaming)                                                                                              |
 
 ### Sender Policy
 
@@ -82,6 +83,18 @@ Controls how conversation sessions are managed:
 - **`thread`** — One session per thread/topic. Useful for group chats with threads.
 - **`single`** — One shared session for all users. Everyone shares the same conversation.
 
+### Channel Memory
+
+Channel memory lets an authorized channel member save stable context for one chat or thread. Qwen Code injects that memory when a fresh channel session starts, including after `/clear`.
+
+Commands:
+
+- `/remember-channel <text>` saves a memory line for the current chat or thread.
+- `/channel-memory` shows saved memory for the current chat or thread.
+- `/forget-channel confirm` clears saved memory for the current chat or thread.
+
+Only users listed in `allowedUsers` can read, write, or clear channel memory. If `allowedUsers` is empty, channel memory commands are disabled for everyone.
+
 ### Token Security
 
 Bot tokens should not be stored directly in `settings.json`. Instead, use environment variable references:
@@ -158,6 +171,38 @@ Configure per-group with the `groups` setting:
 - **Group chat ID** — Override settings for a specific group. Overrides `"*"` defaults.
 - **`requireMention`** (default: `true`) — When `true`, the bot only responds to messages that @mention it or reply to one of its messages. When `false`, the bot responds to all messages (useful for dedicated task groups).
 
+### Group History Backfill
+
+By default, Qwen ignores unmentioned group messages and does not store them as session turns. To let the next `@mention` include recent group context, set `groupHistoryLimit` to a positive number.
+
+```json
+{
+  "channels": {
+    "my-dingtalk": {
+      "type": "dingtalk",
+      "clientId": "$DINGTALK_CLIENT_ID",
+      "clientSecret": "$DINGTALK_CLIENT_SECRET",
+      "groupPolicy": "open",
+      "groupHistoryLimit": 50,
+      "groups": {
+        "*": { "requireMention": true },
+        "sensitive-group-id": {
+          "requireMention": true,
+          "groupHistoryLimit": 0
+        }
+      }
+    }
+  }
+}
+```
+
+- Omitted or `0` disables backfill.
+- Group-level `groupHistoryLimit` overrides the channel-level value.
+- Only messages from authorized senders are persisted.
+- Messages rejected by `groupPolicy` or group allowlist are not persisted.
+- Pending group history is stored as local JSONL under `~/.qwen/channels/<channel-name>-group-history.jsonl` or `$QWEN_HOME/channels/<channel-name>-group-history.jsonl`.
+- Cached messages are injected as untrusted context on the next real trigger and are not written as standalone session turns.
+
 ### How group messages are evaluated
 
 ```
@@ -312,6 +357,24 @@ qwen channel stop
 
 The bot runs in the foreground. Press `Ctrl+C` to stop, or use `qwen channel stop` from another terminal.
 
+### Experimental Daemon-Managed Mode
+
+You can also run configured channels under `qwen serve`:
+
+```bash
+# Start one channel under the daemon lifecycle
+qwen serve --channel my-channel
+
+# Start all configured channels
+qwen serve --channel all
+```
+
+This mode starts one channel worker process owned by `qwen serve`. The worker connects back to the daemon through the SDK and uses the same channel adapters. It is separate from the daemon process, so a channel adapter crash does not crash the daemon.
+
+`qwen serve --channel` is not the same service as `qwen channel start`. Standalone `qwen channel start` still uses the ACP-backed channel service and can run channel configs with different `cwd` values. Daemon-managed channels require every selected channel's `cwd` to resolve to the daemon workspace.
+
+When channels are serve-managed, `qwen channel status` shows the owner as `qwen serve`, and `qwen channel stop` tells you to stop the daemon instead of signaling the worker directly. If a ready worker exits unexpectedly, the daemon continues running and reports a channel-worker warning in `/daemon/status`.
+
 ### Multi-Channel Mode
 
 When you run `qwen channel start` without a name, all channels defined in `settings.json` start together sharing a single agent process. Each channel maintains its own sessions — a Telegram user and a WeChat user get separate conversations, even though they share the same agent.

package/bundled/qc-helper/docs/features/code-review.md

@@ -28,8 +28,7 @@ The `/review` command runs a multi-stage pipeline:
 ```
 Step 1:  Determine scope (local diff / PR worktree / file)
 Step 2:  Load project review rules
-Step 3:  Run deterministic analysis (linter, typecheck)    [zero LLM cost]
-Step 4:  9 parallel review agents                          [9 LLM calls]
+Step 3:  9 parallel review agents                          [9 LLM calls]
            |-- Agent 1: Correctness
            |-- Agent 2: Security
            |-- Agent 3: Code Quality
@@ -37,13 +36,12 @@ Step 4:  9 parallel review agents                          [9 LLM calls]
            |-- Agent 5: Test Coverage
            |-- Agent 6: Undirected Audit (3 personas: 6a/6b/6c)
            '-- Agent 7: Build & Test (runs shell commands)
-Step 5:  Deduplicate --> Batch verify --> Aggregate         [1 LLM call]
-Step 6:  Iterative reverse audit (1-3 rounds, gap finding) [1-3 LLM calls]
-Step 7:  Present findings + verdict
-Step 8:  Autofix (user-confirmed, optional)
-Step 9:  Post PR inline comments (if requested)
-Step 10: Save report + incremental cache
-Step 11: Clean up (remove worktree + temp files)
+Step 4:  Deduplicate --> Batch verify --> Aggregate         [1 LLM call]
+Step 5:  Iterative reverse audit (1-3 rounds, gap finding) [1-3 LLM calls]
+Step 6:  Present findings + verdict
+Step 7:  Submit PR review (inline comments, if requested)
+Step 8:  Save report + incremental cache
+Step 9:  Clean up (remove worktree + temp files)
 ```
 
 ### Review Agents
@@ -60,29 +58,6 @@ Step 11: Clean up (remove worktree + temp files)
 
 All agents run in parallel (Agent 6 launches 3 persona variants concurrently, totaling 9 parallel tasks for same-repo reviews). Findings from Agents 1-6 are verified in a **single batch verification pass** (one agent reviews all findings at once, keeping verification cost fixed regardless of finding count). After verification, **iterative reverse audit** runs 1-3 rounds of gap-finding — each round receives the cumulative finding list from prior rounds, so successive rounds focus on whatever's left undiscovered. The loop stops as soon as a round returns "No issues found", or after 3 rounds (hard cap). Reverse audit findings skip verification (the agent already has full context) and are included as high-confidence results.
 
-## Deterministic Analysis
-
-Before the LLM agents run, `/review` automatically runs your project's existing linters and type checkers:
-
-| Language              | Tools detected                                                   |
-| --------------------- | ---------------------------------------------------------------- |
-| TypeScript/JavaScript | `tsc --noEmit`, `npm run lint`, `eslint`                         |
-| Python                | `ruff`, `mypy`, `flake8`                                         |
-| Rust                  | `cargo clippy`                                                   |
-| Go                    | `go vet`, `golangci-lint`                                        |
-| Java                  | `mvn compile`, `checkstyle`, `spotbugs`, `pmd`                   |
-| C/C++                 | `clang-tidy` (if `compile_commands.json` available)              |
-| Other                 | Auto-discovered from CI config (`.github/workflows/*.yml`, etc.) |
-
-For projects that don't match standard patterns (e.g., OpenJDK), `/review` reads CI configuration files to discover what lint/check commands the project uses. No user configuration needed.
-
-Deterministic findings are tagged with `[linter]` or `[typecheck]` and skip LLM verification — they are ground truth.
-
-- **Errors** → Critical severity
-- **Warnings** → Nice to have (terminal only, not posted as PR comments)
-
-If a tool is not installed or times out, it is skipped with an informational note.
-
 ## Severity Levels
 
 | Severity         | Meaning                                                             | Posted as PR comment?      |
@@ -93,26 +68,12 @@ If a tool is not installed or times out, it is skipped with an informational not
 
 Low-confidence findings appear in a separate "Needs Human Review" section in the terminal and are never posted as PR comments.
 
-## Autofix
-
-After presenting findings, `/review` offers to auto-apply fixes for Critical and Suggestion findings that have clear solutions:
-
-```
-Found 3 issues with auto-fixable suggestions. Apply auto-fixes? (y/n)
-```
-
-- Fixes are applied using the `edit` tool (targeted replacements, not full-file rewrites)
-- Per-file linter checks run after fixes to verify they don't introduce new issues
-- For PR reviews, fixes are committed and pushed from the worktree automatically — your working tree stays clean
-- Nice to have and low-confidence findings are never auto-fixed
-- PR review submission always uses the **pre-fix verdict** (e.g., "Request changes") since the remote PR hasn't been updated until the autofix push completes
-
 ## Worktree Isolation
 
 When reviewing a PR, `/review` creates a temporary git worktree (`.qwen/tmp/review-pr-<number>`) instead of switching your current branch. This means:
 
 - Your working tree, staged changes, and current branch are **never touched**
-- Dependencies are installed in the worktree (`npm ci`, etc.) so linting and build/test work
+- Dependencies are installed in the worktree (`npm ci`, etc.) so build/test work
 - Build and test commands run in isolation without polluting your local build cache
 - If anything goes wrong, your environment is unaffected — just delete the worktree
 - The worktree is automatically cleaned up after the review completes
@@ -127,15 +88,13 @@ You can review PRs from other repositories by passing the full URL:
 /review https://github.com/other-org/other-repo/pull/456
 ```
 
-This runs in **lightweight mode** — no worktree, no linter, no build/test, no autofix. The review is based on the diff text only (fetched via GitHub API). PR comments can still be posted if you have write access.
+This runs in **lightweight mode** — no worktree, no build/test. The review is based on the diff text only (fetched via GitHub API). PR comments can still be posted if you have write access.
 
 | Capability                                                 | Same-repo | Cross-repo                    |
 | ---------------------------------------------------------- | --------- | ----------------------------- |
 | LLM review (Agents 1-6 + verify + iterative reverse audit) | ✅        | ✅                            |
 | Agent 7: Build & test                                      | ✅        | ❌ (no local codebase)        |
-| Deterministic analysis (linter/typecheck)                  | ✅        | ❌                            |
 | Cross-file impact analysis                                 | ✅        | ❌                            |
-| Autofix                                                    | ✅        | ❌                            |
 | PR inline comments                                         | ✅        | ✅ (if you have write access) |
 | Incremental review cache                                   | ✅        | ❌                            |
 
@@ -158,7 +117,7 @@ Or, after running `/review 123`, type `post comments` to publish findings withou
 
 **What stays terminal-only:**
 
-- Nice to have findings (including linter warnings)
+- Nice to have findings
 - Low-confidence findings
 
 **Self-authored PRs:** GitHub does not allow you to submit `APPROVE` or `REQUEST_CHANGES` reviews on your own pull request — both fail with HTTP 422. When `/review` detects that the PR author matches the current authenticated user, it automatically downgrades the API event to `COMMENT` regardless of verdict, so the submission still succeeds. The terminal still shows the honest verdict ("Approve" / "Request changes" / "Comment") — only the GitHub-side review event is neutralized. The actual findings still appear as inline comments on specific lines, so substantive feedback is unchanged.
@@ -178,7 +137,7 @@ After the review, context-aware tips appear as ghost text. Press Tab to accept:
 | PR review, zero findings           | `post comments`    | Approves the PR on GitHub (LGTM)        |
 | Local review, all clear            | `commit`           | Commits your changes                    |
 
-Note: `fix these issues` is only available for local reviews. For PR reviews, use Autofix (Step 8) — the worktree is cleaned up after the review, so post-review interactive fixing is not possible.
+Note: `fix these issues` is only available for local reviews. For PR reviews the worktree is cleaned up after the review, so post-review interactive fixing is not possible — use `--comment` or `post comments` to publish findings instead.
 
 ## Project Review Rules
 
@@ -241,7 +200,7 @@ For same-repo reviews, results are saved as a Markdown file in your project's `.
 .qwen/reviews/2026-04-06-150510-local.md
 ```
 
-Reports include: timestamp, diff stats, deterministic analysis results, all findings with verification status, and the verdict.
+Reports include: timestamp, diff stats, build/test results, all findings with verification status, and the verdict.
 
 ## Cross-file Impact Analysis
 
@@ -260,10 +219,9 @@ The review pipeline uses a bounded number of LLM calls regardless of how many fi
 
 | Stage                            | LLM calls         | Notes                                               |
 | -------------------------------- | ----------------- | --------------------------------------------------- |
-| Deterministic analysis (Step 3)  | 0                 | Shell commands only                                 |
-| Review agents (Step 4)           | 9 (or 8)          | Run in parallel; Agent 7 skipped in cross-repo mode |
-| Batch verification (Step 5)      | 1                 | Single agent verifies all findings at once          |
-| Iterative reverse audit (Step 6) | 1-3               | Loops until "No issues found" or 3-round cap        |
+| Review agents (Step 3)           | 9 (or 8)          | Run in parallel; Agent 7 skipped in cross-repo mode |
+| Batch verification (Step 4)      | 1                 | Single agent verifies all findings at once          |
+| Iterative reverse audit (Step 5) | 1-3               | Loops until "No issues found" or 3-round cap        |
 | **Total**                        | **11-13 (10-12)** | Same-repo: 11-13; cross-repo: 10-12 (no Agent 7)    |
 
 Most PRs converge to the lower end of the range (1 reverse audit round); the cap prevents runaway cost on pathological cases.
@@ -273,8 +231,7 @@ Most PRs converge to the lower end of the range (1 reverse audit round); the cap
 The review intentionally excludes:
 
 - Pre-existing issues in unchanged code (focus on the diff only)
-- Style/formatting/naming that matches your codebase conventions
-- Issues a linter or type checker would catch (handled by deterministic analysis)
+- Style or formatting a formatter would auto-normalize, or naming matching your codebase conventions — but NOT substantive issues a linter or type checker would flag (unused variables, unreachable code, type errors), which are in scope
 - Subjective "consider doing X" suggestions without a real problem
 - Minor refactoring that doesn't fix a bug or risk
 - Missing documentation unless the logic is genuinely confusing
@@ -285,7 +242,6 @@ The review intentionally excludes:
 > **Silence is better than noise.** Every comment should be worth the reader's time.
 
 - If unsure whether something is a problem → don't report it
-- Linter/typecheck issues are handled by tools, not LLM guesses
 - Same pattern across N files → aggregated into one finding
 - PR comments are high-confidence only
-- Style/formatting issues matching codebase conventions are excluded
+- Cosmetic style/formatting matching codebase conventions is excluded

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

@@ -127,12 +127,12 @@ Commands for managing AI tools and models.
 
 These commands invoke bundled skills that provide specialized workflows.
 
-| Command      | Description                                                         | Usage Examples                                    |
-| ------------ | ------------------------------------------------------------------- | ------------------------------------------------- |
-| `/review`    | Review code changes with 5 parallel agents + deterministic analysis | `/review`, `/review 123`, `/review 123 --comment` |
-| `/loop`      | Run a prompt on a recurring schedule                                | `/loop 5m check the build`                        |
-| `/simplify`  | Review recent changes and apply safe cleanup edits directly         | `/simplify`, `/simplify focus on duplication`     |
-| `/qc-helper` | Answer questions about Qwen Code usage and configuration            | `/qc-helper how do I configure MCP?`              |
+| Command      | Description                                                 | Usage Examples                                    |
+| ------------ | ----------------------------------------------------------- | ------------------------------------------------- |
+| `/review`    | Review code changes with 9 parallel review agents           | `/review`, `/review 123`, `/review 123 --comment` |
+| `/loop`      | Run a prompt on a recurring schedule                        | `/loop 5m check the build`                        |
+| `/simplify`  | Review recent changes and apply safe cleanup edits directly | `/simplify`, `/simplify focus on duplication`     |
+| `/qc-helper` | Answer questions about Qwen Code usage and configuration    | `/qc-helper how do I configure MCP?`              |
 
 See [Code Review](./code-review.md) for full `/review` documentation.
 

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

@@ -381,12 +381,14 @@ The `mcp` object in your `settings.json` defines global rules for all MCP server
 - `mcp.allowed`: allow-list of MCP server names (keys in `mcpServers`)
 - `mcp.excluded`: deny-list of MCP server names
 
+Both lists support glob patterns: `*` matches any sequence of characters and `?` matches a single character (for example, `"*puppeteer*"` matches every server whose name contains `puppeteer`). Entries without glob characters are matched exactly. When a server matches both lists, `mcp.excluded` takes precedence.
+
 Example:
 
 ```json
 {
   "mcp": {
-    "allowed": ["my-trusted-server"],
+    "allowed": ["my-trusted-server", "*-internal"],
     "excluded": ["experimental-server"]
   }
 }

package/bundled/qc-helper/docs/features/scheduled-tasks.md

@@ -40,6 +40,16 @@ The scheduled prompt can itself be a command or skill invocation. This is useful
 
 Each time the job fires, Qwen Code runs `/review-pr 1234` as if you had typed it.
 
+### Autonomous mode
+
+Running `/loop` with **no prompt** starts an autonomous loop instead of repeating a fixed prompt. Qwen Code acts as a steward of the work already established in the conversation — it keeps your work moving while you're away:
+
+```text
+/loop
+```
+
+A bare `/loop` (no prompt, no interval) runs a self-paced autonomous loop; `/loop <interval>` with no prompt runs the same autonomous loop on a fixed cadence (e.g. `/loop 10m`). On each fire it advances what the conversation already set up — finishing things you started, maintaining an in-progress PR (addressing review threads, fixing failing CI, resolving conflicts), and honoring follow-up commitments. It only acts on work the transcript already established: it never invents new work or makes irreversible changes (push, delete, send) without clear authorization, and it stops once everything is quiet.
+
 ### Manage loops
 
 `/loop` also supports two subcommands for managing existing jobs: