> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/cline/cline/llms.txt
> Use this file to discover all available pages before exploring further.

# Web Tools

> Search the web and fetch content from URLs directly within Cline tasks.

Web Tools give Cline the ability to search the internet and fetch content from specific URLs during your tasks. This is useful when you need up-to-date information, documentation lookups, or research that goes beyond your local codebase and the model's built-in knowledge.

<Warning>
  Web Tools require the **Cline provider**. They are not available when using other providers such as OpenRouter, Anthropic direct, AWS Bedrock, or self-hosted models.
</Warning>

## How Web Tools work

Cline has two web tools:

<CardGroup cols={2}>
  <Card title="web_search" icon="magnifying-glass">
    Searches the web and returns a list of relevant pages based on your query. Useful for finding documentation, examples, and recent information.
  </Card>

  <Card title="web_fetch" icon="arrow-down-to-line">
    Fetches and analyzes content from a specific URL. Useful when you already know the page you need and want Cline to read its full content.
  </Card>
</CardGroup>

When Cline determines that web information would help complete your task, it uses these tools automatically. The tools call Cline's backend API, which handles the search or fetch operation and returns the results.

## Enabling Web Tools

<Steps>
  <Step title="Sign in to Cline">
    Make sure you're signed in to Cline and using the Cline provider.
  </Step>

  <Step title="Open Feature Settings">
    Go to **Cline Settings → Feature Settings**.
  </Step>

  <Step title="Enable Web Tools">
    Toggle **Web Tools** on.
  </Step>
</Steps>

<Note>
  Web Tools can be auto-approved using the **Use the browser** setting in [Auto Approve](/features/auto-approve). When enabled, Cline won't pause to ask permission before performing web searches or fetches.
</Note>

## Use cases

### Looking up documentation

When working with an unfamiliar library or API, ask Cline to:

* Search for the official documentation
* Fetch a specific API reference page
* Find usage examples and common patterns

```text theme={null}
Look up the latest React Query v5 documentation for the useInfiniteQuery hook
```

### Research before implementation

Before writing code, have Cline:

* Search for best practices and established patterns
* Find recent discussions about approaches or tradeoffs
* Identify known issues or limitations with a library

```text theme={null}
Search for best practices for implementing rate limiting in a Node.js Express API
```

### Checking the latest information

For time-sensitive details that may be outdated in the model's training data:

* Latest release notes and changelogs
* Recent bug fixes or security advisories
* Current recommended package versions

```text theme={null}
Fetch the changelog for Prisma 5.x and summarize the breaking changes
```

### Debugging with external resources

When you hit an error, Cline can search for it directly:

```text theme={null}
Search for this error: "Cannot read properties of undefined (reading 'map')" in a React component
```

## Browser automation

Web Tools handle search and fetch for text-based content. For interactive browser tasks — clicking elements, filling forms, taking screenshots of a running web app — Cline uses the `browser_action` tool instead. See [Web Tools](/features/web-tools) for more details.

## Related

* [Auto Approve](/features/auto-approve) — Auto-approve web tool use with the "Use the browser" toggle
* [Models & Providers](/models/model-selection-guide) — Choosing the right model for web tasks