This topic describes the tool capabilities provided by Qoder CN CLI, including search and exploration, reading project context, editing files, executing commands, managing context, delegation and automation, MCP tools, and ways to control tool usage.
The new Qoder CN documentation site is now available. Content on this site may not reflect the latest product features and changes. Visit docs.qoder.cn for the latest product documentation.
Qoder CN CLI uses tools to interact with the local workspace and external information sources. Tools can search and read project content, modify files, execute commands, fetch web content, maintain context, and connect to external services through MCP.
Tools are available in both interactive TUI sessions and non-interactive Print mode. The actual set of available tools depends on the current session, enabled features, MCP configuration, and permission settings.
Use /tools in the TUI to view the tools available in the current session.
Search and exploration
Qoder CN CLI uses search and exploration tools to understand the current task before deciding on the next step.
|
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 resources. |
|
Web content |
Fetch the content of a specified web page. |
Read 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 |
Read only the relevant sections when a file is too large. |
|
Read document assets |
Read document formats such as PDF when supported. |
Edit files
When a task requires changes, Qoder CN CLI can create or modify files in the workspace.
|
Capability |
Description |
|
Modify files |
Make targeted edits to existing files. |
|
Create files |
Add new source code, tests, documentation, or configuration files. |
|
Edit notebooks |
Modify notebook content in scenarios that support notebooks. |
File edits go through the permission system. Depending on the permission mode and rules, Qoder CN CLI may apply changes directly, prompt for confirmation, or block the operation.
Execute commands
When a task requires local execution, Qoder CN CLI can run shell commands.
|
Capability |
Description |
|
Run commands |
Execute 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. |
Shell commands generally carry higher risk than read-only operations. It is recommended to use permission rules to allow common commands and set sensitive commands to prompt or deny.
Manage context
Some tools help Qoder CN CLI maintain the current task and session state.
|
Capability |
Description |
|
Track tasks |
Maintain a lightweight plan or task list during work. |
|
Clarify questions |
Ask the user when decisions or critical information is missing. |
|
Manage memory |
Save long-term information when memory capabilities are available. |
|
Use skills |
Load domain-specific instructions or workflows when configured. |
|
Plan work |
Enter or exit Plan mode when a task requires analysis before execution. |
Memory and skills provide context to the model, but they are not security boundaries. Use permission rules and hooks when you need to enforce policies.
Delegation and automation
Qoder CN CLI can use delegation and automation capabilities when the current environment enables them.
|
Capability |
Description |
|
Subagents |
Delegate specific work to specialized agents. |
|
Workflows |
Run configured repeatable workflows. |
|
Goals |
Track and execute longer-term goals. |
|
Worktrees |
Work in isolated Git worktrees when parallel sessions are needed. |
|
Scheduled tasks |
Create or manage scheduled tasks when scheduling capabilities are enabled. |
The specific capabilities available depend on the product configuration, feature flags, and the current session.
MCP tools
Qoder CN CLI can connect to Model Context Protocol (MCP) servers to access external tools and data sources. Once MCP servers 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 trackers, code hosting platforms, databases, browser automation, internal platforms, or custom enterprise services.
For MCP configuration, see MCP Servers.
Control tool usage
Whether a tool is visible and whether it is allowed to execute are two separate concerns.
|
Control |
Description |
|
|
Restrict the tools visible in the current session. |
|
|
Pre-approve specified tools or tool patterns. |
|
|
Block specified tools or tool patterns. |
|
|
Persistent permission rules defined in settings files. |
|
|
Remove tools from discovery results at startup. |
Examples:
# Read-only exploration
qoderclicn --tools Read Grep Glob --allowed-tools 'Read,Grep,Glob'
# Allow common status-checking commands
qoderclicn --allowed-tools 'Read,Grep,Bash(git status)'
# Disallow file editing in a non-interactive review
qoderclicn -p "review this repository" --disallowed-tools 'Write,Edit'For permission modes, rule syntax, and evaluation order, see Permissions. For hooks that intercept tool calls, see Hooks.