Qoder CN provides built-in tools across five categories: search, file editing, command execution, problem retrieval, and memory management. In Agent mode, Qoder CN autonomously selects and invokes these tools. MCP server integration lets you extend capabilities with additional tools.
This article introduces the tool capabilities provided by Qoder CN CLI, including search and exploration, reading project context, editing files, running commands, managing context, dispatch and automation, MCP tools, and how tool usage is controlled.
Qoder CN CLI works with the local workspace and external information sources through tools. Tools can search and read project content, modify files, run commands, fetch web content, maintain context, and connect to external services via MCP. Tools can be used in interactive TUI sessions and in non-interactive Print mode. The actual set of available tools depends on the current session, enabled features, MCP configuration, and permission settings. In the TUI, use
Qoder CN CLI uses search and exploration tools to first understand the current task before deciding what to do next.
Qoder CN CLI can read files and other project assets to gather context for the current request.
When a task requires changes, Qoder CN CLI can create or modify files in the workspace.
File edits go through the permission system. Depending on the permission mode and rules, Qoder CN CLI may apply changes directly, request confirmation, or block the operation.
When a task requires local execution, Qoder CN CLI can run shell commands.
Shell commands are generally riskier than read-only operations. We recommend using permission rules to allow routine commands and setting ask or deny for sensitive commands.
Some tools help Qoder CN CLI maintain the state of the current task and session.
Memory and Skills provide context to the model, but they are not security boundaries. When you need to enforce policy, use permission rules and Hooks.
When the relevant capabilities are enabled in the current environment, Qoder CN CLI can use dispatch and automation capabilities.
What is actually available depends on the product configuration, feature flags, and the current session.
Qoder CN CLI can connect to Model Context Protocol (MCP) services to use external tools and data sources. Once MCP services are configured, their tools appear in the same
Whether a tool is visible and whether a tool is allowed to run are two separate things.
Examples:
For permission modes, rule syntax, and evaluation order, see Permissions. For using Hooks to intercept tool calls, see Hooks.
Qoder CN CLI works with the local workspace and external information sources through tools. Tools can search and read project content, modify files, run commands, fetch web content, maintain context, and connect to external services via MCP. Tools can be used in interactive TUI sessions and in non-interactive Print mode. The actual set of available tools depends on the current session, enabled features, MCP configuration, and permission settings. In the TUI, use
/tools to see the tools available in the current session.
Search and Exploration
Qoder CN CLI uses search and exploration tools to first understand the current task before deciding what to do next.
| Scope | Description |
|---|---|
| Files | Find files in the current workspace. |
| Code | Search code, text, and configuration files. |
| Directories | Browse the project structure and locate relevant paths. |
| Web | Search the web when the task requires current information or public materials. |
| Web content | Fetch the content of a specified web page. |
Reading Project Context
Qoder CN CLI can read files and other project assets to gather context for the current request.
| Capability | Description |
|---|---|
| View files | Read source code, documentation, configuration, and other text assets. |
| Read large files | When a file is too large, read only the relevant portions. |
| Read document assets | Read document formats such as PDF when supported. |
Editing Files
When a task requires changes, Qoder CN CLI can create or modify files in the workspace.
| Capability | Description |
|---|---|
| Modify files | Make targeted modifications to existing files. |
| Create files | Add files such as source code, tests, documentation, or configuration. |
| Edit Notebooks | Modify Notebook content in Notebook-supported scenarios. |
Running Commands
When a task requires local execution, Qoder CN CLI can run shell commands.
| Capability | Description |
|---|---|
| Run commands | Run builds, tests, packaging, Git checks, project troubleshooting, or custom shell commands. |
| Run long-running tasks | Track time-consuming commands, such as test suites or development scripts. |
Managing Context
Some tools help Qoder CN CLI maintain the state of the current task and session.
| Capability | Description |
|---|---|
| Track tasks | Maintain a lightweight plan or task list during work. |
| Clarify questions | Ask the user when a decision or key information is missing. |
| Manage memory | Save long-term information when the memory capability is available. |
| Use Skills | Load domain-specific instructions or workflows once configured. |
| Plan work | Enter or exit Plan mode when a task requires analysis before execution. |
Dispatch and Automation
When the relevant capabilities are enabled in the current environment, Qoder CN CLI can use dispatch and automation capabilities.
| Capability | Description |
|---|---|
| Subagents | Dispatch specific work to specialized Agents. |
| Workflows | Run configured, repeatable workflows. |
| Goals | Track and pursue longer-running goals. |
| Worktrees | Work in a separate Git worktree when parallel sessions are needed. |
| Scheduled tasks | Create or manage scheduled tasks when the scheduling capability is enabled. |
MCP Tools
Qoder CN CLI can connect to Model Context Protocol (MCP) services to use external tools and data sources. Once MCP services are configured, their tools appear in the same /tools view and go through the same permission system.
MCP tools are well suited for connecting to issue systems, code hosting platforms, databases, browser automation, internal platforms, or enterprise-custom services.
For MCP configuration, see MCP services.
Controlling Tool Usage
Whether a tool is visible and whether a tool is allowed to run are two separate things.
| Control | Description |
|---|---|
--tools | Restrict the tools visible in the current session. |
--allowed-tools | Pre-allow specified tools or tool patterns. |
--disallowed-tools | Block specified tools or tool patterns. |
permissions.allow / permissions.ask / permissions.deny | Persistent permission rules written in the settings file. |
tools.exclude | Remove tools from discovery results at startup. |