Tools - Qoder CN

Qoder CLI CN 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 set of tools actually available depends on the current session, enabled features, MCP configuration, and permission settings. Use /tools in the TUI to see the tools available in the current session.

Search and explore

Qoder CLI CN uses search and exploration tools to understand the task at hand before deciding its next move.

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 material.
Web content	Fetch the content of a given web page.

Read project context

Qoder CLI CN 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 portions when a file is too large.
Read document assets	Read document formats such as PDF where supported.

Edit files

When a task requires changes, Qoder CLI CN can create or modify files in the workspace.

Capability	Description
Modify files	Make targeted modifications to existing files.
Create files	Add new files such as source code, tests, documentation, or configuration.
Edit notebooks	Modify notebook content where notebooks are supported.

File edits go through the permission system. Depending on the permission mode and rules, Qoder CLI CN may apply changes directly, request confirmation, or block the operation.

Execute commands

When a task requires local execution, Qoder CLI CN can run shell commands.

Capability	Description
Run commands	Execute builds, tests, packaging, Git checks, project diagnostics, or custom shell commands.
Run long tasks	Track long-running commands such as test suites or dev scripts.

Background commands and event monitoring

When subsequent work does not depend on a command's immediate result, Qoder CLI CN can run the shell command in the background so the main session keeps working on other things. A command explicitly requested to run in the background creates a background task regardless of how long it takes; when the task completes, fails, or needs attention, the result is automatically returned to its session — no repeated progress questions or polling commands needed.

Background task starts -> main session keeps working -> completion notice returns -> main session handles the result

For scenarios that continuously produce events — logs, deployment status, test observation — Qoder CLI CN can start event monitoring. Every complete line the monitored command outputs is sent to the main session as an event notification. Monitoring commands should output only the events worth attention, rather than forwarding full high-frequency logs. Type /tasks in the TUI to check the status and output of background shells and Subagents, and to stop tasks still running. When a background task ends, the completion notice returns to the main session, and Qoder CLI CN continues based on the result. Shell commands are generally riskier than read-only operations. We recommend allowing routine commands via permission rules, and setting ask or deny for sensitive commands. When the shell command prefix is enabled via the QODERCN_SHELL_PREFIX environment variable, the Bash tool runs the fully assembled shell command through the configured executable wrapper. Permission checks and command display still use the original command. The wrapper must execute the single command argument it receives, and preserve the process's input/output and exit status.

Manage context

Some tools help Qoder CLI CN maintain the current task and session state.

Capability	Description
Track tasks	Maintain a lightweight plan or task list while working.
Ask clarifying questions	Ask the user when a decision or key information is missing.
Manage memory	Save long-term information when memory capabilities are available.
Use Skills	Load domain-specific instructions or workflows once configured.
Plan work	Enter or exit Plan Mode when a task needs analysis before execution.

Memory and Skills provide context to the model, but they are not a security boundary. When you need enforced policy, use permission rules and Hooks.

Delegate and automate

When the current environment enables the relevant capabilities, Qoder CLI CN can use delegation and automation.

Capability	Description
Subagents	Delegate specific work to dedicated Agents.
Workflows	Run configured, repeatable workflows.
Goals	Track and execute longer-horizon goals.
Worktrees	Work in separate Git worktrees when parallel sessions are needed.
Scheduled tasks	Create or manage scheduled tasks when scheduling is enabled.

The exact availability depends on product configuration, feature switches, and the current session.

MCP tools

Qoder CLI CN 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 a good fit for connecting 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 run are two different things.

Control	Description
`--tools`	Restrict which tools are visible in the current session.
`--allowed-tools`	Pre-allow specific tools or tool patterns.
`--disallowed-tools`	Block specific tools or tool patterns.
`permissions.allow` / `permissions.ask` / `permissions.deny`	Persistent permission rules written in settings files.
`tools.exclude`	Remove tools from discovery at startup.

Examples:

# Read-only exploration
qodercn --tools Read Grep Glob --allowed-tools 'Read,Grep,Glob'

# Allow common status-check commands
qodercn --allowed-tools 'Read,Grep,Bash(git status)'

# Disallow file edits in a non-interactive review
qodercn -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.