Built-In Tools (ClineCore)
When running throughClineCore, these built-ins are available:
A session offers
editor or apply_patch, never both. By default, Act mode offers apply_patch to GPT and Codex models and to every model on the OpenAI (openai-native) provider, and editor to other models; Plan mode offers neither. SDK callers can replace these defaults with the toolRoutingRules session option.
Agent from @cline/agents does not include built-ins by default. You provide tools explicitly.Tool Categories
- Codebase operations:
read_files,search_codebase,editor,apply_patch - Execution:
run_commands - External retrieval:
fetch_web_content - Skills:
skills - Human-in-the-loop controls:
ask_question - Completion:
submit_and_exit
Approval and Policy Controls
Cline can run tools with approval or auto-approval, depending on settings/policies. Typical patterns:- Require approval for risky tools (for example
run_commands, write/edit operations) - Auto-approve low-risk tools (for example read/search operations)
- Disable specific tools entirely when needed
MCP Tools
Cline can also call tools discovered from MCP servers configured in~/.cline/data/settings/cline_mcp_settings.json.
MCP tools are loaded alongside built-ins, so Cline can use both local tools and external integrations in one task.
See MCP Overview and SDK Tools → MCP Tools.
Custom Tools
Beyond built-ins and MCP, you can create custom tools and add them through plugins.- Define tool behavior and input schema in plugin code
- Register tools during plugin setup
- Expose those tools to agents alongside built-ins
Legacy Tool Names vs Current Runtime Tools
Some older docs/examples reference XML-style names likeread_file, replace_in_file, execute_command, or use_skill. Current SDK/ClineCore runtime uses the built-in tool names listed above (read_files, apply_patch, run_commands, skills, etc.).