From c884dc080b6af2127b96e2dd749133a13af29b22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=AE=B6=E5=A8=83?= Date: Wed, 29 Oct 2025 10:55:57 +0800 Subject: [PATCH] [to #12345678] docs: update excludeTools documentation in extensions guide - Added clarification that tools specified in excludeTools will be disabled for the entire conversation context - Added note that excludeTools configuration affects all subsequent queries in the current session This change improves documentation clarity for extension developers by better explaining the scope and impact of the excludeTools configuration. Co-authored-by: Qwen-Coder --- docs/extensions/extension.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extensions/extension.md b/docs/extensions/extension.md index 1986ffb9..0d2e93eb 100644 --- a/docs/extensions/extension.md +++ b/docs/extensions/extension.md @@ -107,7 +107,7 @@ The `qwen-extension.json` file contains the configuration for the extension. The - `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. - Note that all MCP server configuration options are supported except for `trust`. - `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. -- `excludeTools`: An array of tool names to exclude from the model. You can also specify command-specific restrictions for tools that support it, like the `run_shell_command` tool. For example, `"excludeTools": ["run_shell_command(rm -rf)"]` will block the `rm -rf` command. Note that this differs from the MCP server `excludeTools` functionality, which can be listed in the MCP server config. +- `excludeTools`: An array of tool names to exclude from the model. You can also specify command-specific restrictions for tools that support it, like the `run_shell_command` tool. For example, `"excludeTools": ["run_shell_command(rm -rf)"]` will block the `rm -rf` command. Note that this differs from the MCP server `excludeTools` functionality, which can be listed in the MCP server config. **Important:** Tools specified in `excludeTools` will be disabled for the entire conversation context and will affect all subsequent queries in the current session. When Qwen Code starts, it loads all the extensions and merges their configurations. If there are any conflicts, the workspace configuration takes precedence.