> For the complete documentation index, see [llms.txt](https://modelmesh.gitbook.io/cline-zhong-wen-ban-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://modelmesh.gitbook.io/cline-zhong-wen-ban-docs/exploring-clines-tools/cline-tools-guide.md).

# Cline Tools Guide

### What Can Cline Do? <a href="#what-can-cline-do" id="what-can-cline-do"></a>

Cline is your AI assistant that can:

* Edit and create files in your project
* Run terminal commands
* Search and analyze your code
* Help debug and fix issues
* Automate repetitive tasks
* Integrate with external tools

### First Steps <a href="#first-steps" id="first-steps"></a>

1. **Start a Task**
   * Type your request in the chat
   * Example: "Create a new React component called Header"
2. **Provide Context**
   * Use @ mentions to add files, folders, or URLs
   * Example: "@file:src/components/App.tsx"
3. **Review Changes**
   * Cline will show diffs before making changes
   * You can edit or reject changes

### Key Features <a href="#key-features" id="key-features"></a>

1. **File Editing**
   * Create new files
   * Modify existing code
   * Search and replace across files
2. **Terminal Commands**
   * Run npm commands
   * Start development servers
   * Install dependencies
3. **Code Analysis**
   * Find and fix errors
   * Refactor code
   * Add documentation
4. **Browser Integration**
   * Test web pages
   * Capture screenshots
   * Inspect console logs

### Available Tools <a href="#available-tools" id="available-tools"></a>

For the most up-to-date implementation details, you can view the full source code in the [Cline repository](https://github.com/cline/cline/blob/main/src/core/Cline.ts).

Cline has access to the following tools for various tasks:

1. **File Operations**
   * `write_to_file`: Create or overwrite files
   * `read_file`: Read file contents
   * `replace_in_file`: Make targeted edits to files
   * `search_files`: Search files using regex
   * `list_files`: List directory contents
2. **Terminal Operations**
   * `execute_command`: Run CLI commands
   * `list_code_definition_names`: List code definitions
3. **MCP Tools**
   * `use_mcp_tool`: Use tools from MCP servers
   * `access_mcp_resource`: Access MCP server resources
   * Users can create custom MCP tools that Cline can then access
   * Example: Create a weather API tool that Cline can use to fetch forecasts
4. **Interaction Tools**
   * `ask_followup_question`: Ask user for clarification
   * `attempt_completion`: Present final results

Each tool has specific parameters and usage patterns. Here are some examples:

* Create a new file (write\_to\_file):

  Copy

  ```
  <write_to_file>
  <path>src/components/Header.tsx</path>
  <content>
  // Header component code
  </content>
  </write_to_file>
  ```
* Search for a pattern (search\_files):

  Copy

  ```
  <search_files>
  <path>src</path>
  <regex>function\s+\w+\(</regex>
  <file_pattern>*.ts</file_pattern>
  </search_files>
  ```
* Run a command (execute\_command):

  Copy

  ```
  <execute_command>
  <command>npm install axios</command>
  <requires_approval>false</requires_approval>
  </execute_command>
  ```

### Common Tasks <a href="#common-tasks" id="common-tasks"></a>

1. **Create a New Component**
   * "Create a new React component called Footer"
2. **Fix a Bug**
   * "Fix the error in src/utils/format.ts"
3. **Refactor Code**
   * "Refactor the Button component to use TypeScript"
4. **Run Commands**
   * "Run npm install to add axios"

### Getting Help <a href="#getting-help" id="getting-help"></a>

* [Join the Discord community](https://discord.gg/cline)
* Check the documentation
* Provide feedback to improve Cline


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://modelmesh.gitbook.io/cline-zhong-wen-ban-docs/exploring-clines-tools/cline-tools-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.