vrr/qwen-code
2
0
Fork 0
mirror of https://github.com/QwenLM/qwen-code.git synced 2026-04-28 11:41:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 13
qwen-code/docs/developers/tools/introduction.md
顾盼 aeeb2976d6
feat(web-search): remove built-in web_search tool, replace with MCP-based approach (#3502) 
* feat(web-search): add GLM (ZhipuAI) web search provider

- Add GlmProvider class implementing BaseWebSearchProvider using the
  ZhipuAI Web Search API (https://open.bigmodel.cn/api/paas/v4/web_search)
- Support multiple search engines: search_std, search_pro, search_pro_sogou,
  search_pro_quark
- Support optional config: maxResults, searchIntent, searchRecencyFilter,
  contentSize, searchDomainFilter
- Truncate query to 70 characters per API limit
- Register 'glm' in the provider discriminated union (types.ts) and
  createProvider() switch (index.ts)
- Add GlmProviderConfig to settingsSchema, ConfigParams, and Config class
- Add --glm-api-key CLI flag and GLM_API_KEY env var support in webSearch.ts
- Forward GLM_API_KEY in sandbox environment
- Update provider priority list: Tavily > Google > GLM > DashScope
- Add 17 unit tests for GlmProvider and 4 integration tests in index.test.ts
- Update docs/developers/tools/web-search.md with GLM configuration,
  env vars, CLI args, pricing, and corrected DashScope billing info
- Fix stale OAuth/free-tier references in web-search.md

Closes #3496

* docs(web-search): fix DashScope note and add GLM server-side limitations

* fix(web-search): make DashScope provider work with standard API key, remove qwen-oauth dependency

- DashScopeProvider.isAvailable() now checks config.apiKey instead of authType
- Remove OAuth credential file reading and resource_url requirement
- Use standard DashScope endpoint: dashscope.aliyuncs.com/api/v1/indices/plugin/web_search
- Read DASHSCOPE_API_KEY env var and --dashscope-api-key CLI flag
- Forward DASHSCOPE_API_KEY into sandbox environment
- Update integration test to detect DASHSCOPE_API_KEY
- Update docs to reflect new API key based configuration

* feat(web-search): remove built-in web search tool

The web_search tool and all related provider implementations are removed.
Web search functionality will be provided via MCP integrations instead,
which is the direction the broader agent ecosystem is moving.

Removed:
- packages/core/src/tools/web-search/ (entire directory)
- packages/cli/src/config/webSearch.ts
- integration-tests/cli/web_search.test.ts
- ToolNames.WEB_SEARCH, ToolErrorCode.WEB_SEARCH_FAILED
- webSearch config in ConfigParams, Config class, settingsSchema
- CLI options: --tavily-api-key, --google-api-key, --google-search-engine-id,
  --glm-api-key, --dashscope-api-key, --web-search-default
- Sandbox env forwarding for TAVILY/GLM/DASHSCOPE/GOOGLE search keys
- web_search from rule-parser, permission-manager, speculation gate,
  microcompact tool set, and builtin-agents tool list

* fix: remove websearch reference

* docs: remove websearch tool

* docs: add break change guide

* fix review
2026-04-24 11:29:02 +08:00

5.1 KiB
Raw Blame History

Qwen Code tools

Qwen Code includes built-in tools that the model uses to interact with your local environment, access information, and perform actions. These tools enhance the CLI's capabilities, enabling it to go beyond text generation and assist with a wide range of tasks.

Overview of Qwen Code tools

In the context of Qwen Code, tools are specific functions or modules that the model can request to be executed. For example, if you ask the model to "Summarize the contents of my_document.txt," it will likely identify the need to read that file and will request the execution of the read_file tool.

The core component (packages/core) manages these tools, presents their definitions (schemas) to the model, executes them when requested, and returns the results to the model for further processing into a user-facing response.

These tools provide the following capabilities:

  • Access local information: Tools allow the model to access your local file system, read file contents, list directories, etc.
  • Execute commands: With tools like run_shell_command, the model can run shell commands (with appropriate safety measures and user confirmation).
  • Interact with the web: Tools can fetch content from URLs.
  • Take actions: Tools can modify files, write new files, or perform other actions on your system (again, typically with safeguards).
  • Ground responses: By using tools to fetch real-time or specific local data, responses can be more accurate, relevant, and grounded in your actual context.

How to use Qwen Code tools

To use Qwen Code tools, provide a prompt to the CLI. The process works as follows:

  1. You provide a prompt to the CLI.
  2. The CLI sends the prompt to the core.
  3. The core, along with your prompt and conversation history, sends a list of available tools and their descriptions/schemas to the configured model API.
  4. The model analyzes your request. If it determines that a tool is needed, its response will include a request to execute a specific tool with certain parameters.
  5. The core receives this tool request, validates it, and (often after user confirmation for sensitive operations) executes the tool.
  6. The output from the tool is sent back to the model.
  7. The model uses the tool's output to formulate its final answer, which is then sent back through the core to the CLI and displayed to you.

You will typically see messages in the CLI indicating when a tool is being called and whether it succeeded or failed.

Security and confirmation

Many tools, especially those that can modify your file system or execute commands (write_file, edit, run_shell_command), are designed with safety in mind. Qwen Code will typically:

  • Require confirmation: Prompt you before executing potentially sensitive operations, showing you what action is about to be taken.
  • Utilize sandboxing: All tools are subject to restrictions enforced by sandboxing (see Sandboxing in Qwen Code). This means that when operating in a sandbox, any tools (including MCP servers) you wish to use must be available inside the sandbox environment. For example, to run an MCP server through npx, the npx executable must be installed within the sandbox's Docker image or be available in the sandbox-exec environment.

It's important to always review confirmation prompts carefully before allowing a tool to proceed.

Learn more about Qwen Code's tools

Qwen Code's built-in tools can be broadly categorized as follows:

  • File System Tools: For interacting with files and directories (reading, writing, listing, searching, etc.).
  • Shell Tool (run_shell_command): For executing shell commands.
  • Web Fetch Tool (web_fetch): For retrieving content from URLs.
  • Multi-File Read Tool (read_many_files): A specialized tool for reading content from multiple files or directories, often used by the @ command.
  • Memory Tool (save_memory): For saving and recalling information across sessions.
  • Todo Write Tool (todo_write): For creating and managing structured task lists during coding sessions.
  • Task Tool (task): For delegating complex tasks to specialized subagents.
  • Exit Plan Mode Tool (exit_plan_mode): For exiting plan mode and proceeding with implementation.

Additionally, these tools incorporate: