How Tools Work

Kilo Code uses tools to interact with your code and environment. These specialized helpers perform specific actions like reading files, making edits, running commands, or searching your codebase. Tools provide automation for common development tasks without requiring manual execution.

Tool Workflow

Describe what you want to accomplish in natural language, and Kilo Code will:

1. Select the appropriate tool based on your request
2. Present the tool with its parameters for your review
3. Execute the approved tool and show you the results
4. Continue this process until your task is complete

Tool Categories

{% tabs %} {% tab label="VSCode" %}

{% /tab %} {% tab label="VSCode (Legacy)" %}

{% /tab %} {% /tabs %}

Example: Using Tools

Here's how a typical tool interaction works:

{% tabs %} {% tab label="VSCode" %}

{% callout type="info" title="Tool Approval UI" %} When a tool is proposed, you'll see an approval prompt in the Permission Dock at the bottom of the chat. You can approve once, approve always (saves to config), or deny. {% /callout %}

User: Create a file named greeting.js that logs a greeting message

Kilo Code: (Proposes the write tool)

The extension shows the file path and proposed content for review. Click Approve to execute or Deny to cancel.

{% /tab %} {% tab label="VSCode (Legacy)" %}

{% callout type="info" title="Tool Approval UI" %} When a tool is proposed, you'll see Save and Reject buttons along with an optional Auto-approve checkbox for trusted operations. {% /callout %}

User: Create a file named greeting.js that logs a greeting message

Kilo Code: (Proposes the write_to_file tool as shown in the image above)

<write_to_file>
<path>greeting.js</path>
<content>
function greet(name) {
  console.log(`Hello, ${name}!`);
}

greet('World');
</content>
<line_count>5</line_count>
</write_to_file>

User: (Clicks "Save" in the interface)

Kilo Code: (Confirms file creation)

{% /tab %} {% /tabs %}

Tool Safety and Approval

{% tabs %} {% tab label="VSCode" %}

Every tool use is subject to a permission check. The default action for any tool with no matching rule in your config is ask — meaning Kilo will pause and prompt you before executing it.

Default permissions by tool:

No tools are auto-approved out of the box. You must explicitly grant allow in your config, or approve them at runtime.

At runtime, the Permission Dock floating UI in the chat panel shows each pending approval. For each tool call you can:

• Approve once — execute this call only
• Approve always — save an allow rule to your config so future matching calls are auto-approved
• Deny — cancel the tool call

To pre-configure permissions in your config file:

{
  "permission": {
    "read": "allow",
    "glob": "allow",
    "grep": "allow",
    "edit": "ask",
    "bash": "ask"
  }
}

This safety mechanism ensures you maintain control over which files are modified, what commands are executed, and how your codebase is changed.

{% /tab %} {% tab label="VSCode (Legacy)" %}

Every tool use requires your explicit approval. When Kilo proposes a tool, you'll see:

• A "Save" button to approve and execute the tool
• A "Reject" button to decline the proposed tool
• An optional "Auto-approve" setting for trusted operations

This safety mechanism ensures you maintain control over which files are modified, what commands are executed, and how your codebase is changed. Always review tool proposals carefully before saving them.

{% /tab %} {% /tabs %}

Core Tools Reference

{% tabs %} {% tab label="VSCode" %}

{% /tab %} {% tab label="VSCode (Legacy)" %}

{% /tab %} {% /tabs %}

Learn More About Tools

For more detailed information about each tool, including complete parameter references and advanced usage patterns, see the Tool Use Overview documentation.