vrr/qwen-code
2
0
Fork 0
mirror of https://github.com/QwenLM/qwen-code.git synced 2026-04-28 03:30:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 13
qwen-code/docs/developers/tools/introduction.md
Reid f7ebc372f1
feat(core): add dynamic swarm worker tool (#3433) 
* feat(core): add dynamic swarm worker tool

  Add a swarm tool for ad-hoc parallel worker execution with bounded concurrency, wait-all and first-success modes, per-worker failure
  isolation, and aggregated results.

  Register the tool in core, prevent nested worker recursion, and document the new workflow.

* fix(core): harden swarm worker execution

  Prevent swarm calls from bypassing the outer scheduler concurrency budget.

  Disallow interactive question prompts in swarm workers by default, and avoid incomplete Markdown table escaping by using an HTML entity for
  pipe characters. Add focused tests for the scheduler behavior, worker tool restrictions, and result formatting.
2026-04-19 14:46:59 +08:00

5.2 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.
  • Web Search Tool (web_search): For searching the web.
  • 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.
  • Swarm Tool (swarm): For running many independent lightweight workers in parallel and aggregating their results.
  • Exit Plan Mode Tool (exit_plan_mode): For exiting plan mode and proceeding with implementation.

Additionally, these tools incorporate: