# Quick Start

This walkthrough gets from installation to first AI analysis quickly.

## 0. Pick a Backend (Prerequisites)

* **Using Burp AI built-in (Burp Pro only)**: open Burp's **Settings → Burp AI**, enable **Use AI for extensions**, and confirm there are AI credits available. No URL or key is needed on the extension side. See [Burp AI (Built-in)](https://burp-ai-agent.six2dez.com/backends/burp-ai).
* **Using Ollama / LM Studio**: install the server locally and pull at least one model.
* **Using NVIDIA NIM / Generic OpenAI-compatible**: have the base URL, model name, and API key handy.
* **Using a CLI backend (Gemini, Claude, Codex, Copilot, OpenCode)**: the CLI must already be installed and authenticated in the same shell environment that launches Burp.

If you skip this step, the backend will show `Offline` in the top bar until the prerequisite is satisfied.

## 1. Enable MCP (Optional but Recommended)

* Click **MCP** toggle in the top bar of the **AI Agent** tab.
* Verify indicator turns active.

![Screenshot: Top bar toggles](https://741304880-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaQ3pR328GUzNEoYZ2fgc%2Fuploads%2Fgit-blob-24f99c9ee6173183dc4a1478de122dcccdb7257f%2Ftop-bar-toggles.png?alt=media)

## 2. Select Agent Profile (Recommended)

Bundled profiles are installed automatically into `~/.burp-ai-agent/AGENTS/`.

To add custom profiles, place `*.md` files in that directory and refresh profiles in **AI Backend** settings.

## 3. Configure AI Backend

1. Open **AI Backend** tab in Settings.
2. Choose backend.
3. Set CLI command or HTTP URL/model fields.

{% hint style="warning" %}
If using cloud CLIs, required credentials must exist in the runtime environment where Burp is launched. GUI launchers often do not inherit shell env vars.
{% endhint %}

For backend-specific values, see [Backends Overview](https://burp-ai-agent.six2dez.com/backends/overview).

![Screenshot: Backend selection](https://741304880-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaQ3pR328GUzNEoYZ2fgc%2Fuploads%2Fgit-blob-44bf0dc11922d6b8a62ae76ca3ea3c0cbe2df17b%2Fbackend-selection.png?alt=media)

## 4. Analyze a Request

1. Go to **Proxy -> HTTP History**.
2. Right-click a request.
3. Select **Extensions -> Custom AI Agent -> Find vulnerabilities**.

![Screenshot: Context menu on request](https://741304880-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaQ3pR328GUzNEoYZ2fgc%2Fuploads%2Fgit-blob-c5851be28915a1733822cd7a616de384626e0208%2Fcontext-menu-request.png?alt=media)

## 5. Review Response

A new chat session opens and streams AI analysis.

![Screenshot: Chat response](https://741304880-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaQ3pR328GUzNEoYZ2fgc%2Fuploads%2Fgit-blob-9b4e1ccc820f71ff72137010ee800c8a51aa9844%2Fchat-response.png?alt=media)

## 6. Enable Background Scanning (Advanced)

1. Toggle **Passive** ON in top bar.
2. Browse target traffic.
3. Review findings in passive scanner view and Burp issues.

<figure><img src="https://741304880-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaQ3pR328GUzNEoYZ2fgc%2Fuploads%2Ft81LNvO8huPtscq0n8Tn%2Fimage.png?alt=media&#x26;token=a9cfd8fb-baa5-47ce-9adf-bd6224beec4d" alt="Passive scanner toggle enabled in top bar"><figcaption></figcaption></figure>

## Next Steps

* [UI Tour](https://burp-ai-agent.six2dez.com/user-guide/ui-tour)
* [Context Menus](https://burp-ai-agent.six2dez.com/user-guide/context-menus)
* [Passive AI Scanner](https://burp-ai-agent.six2dez.com/scanners/passive)


---

# Agent Instructions: 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:

```
GET https://burp-ai-agent.six2dez.com/getting-started/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
