> For the complete documentation index, see [llms.txt](https://docs.burpgpt.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.burpgpt.app/analysis-and-prompts/use-ai-chat.md).

# Use AI Chat

Ask questions about selected HTTP traffic in the AI Chat editor.

## Before you start

[Activate your licence](/getting-started/activate-your-licence.md) and [test your provider](/model-setup/test-and-validate-model-provider-settings.md). Have a captured request available in a supported HTTP request editor, such as Proxy HTTP history or Repeater.

`AI Chat` does not require `Scan: On` or use the scanner's role, prompt template, or placeholders. It uses the provider, model, timeout, and request parameters from `Provider settings`.

## Ask a question

1. Select a request in Burp Suite.
2. Open the `AI Chat` tab in its message editor.
3. Type your question.
4. Select `Request`, `Response`, or both to include that traffic with your next message. A response can only be included when one is available.
5. Click `Send` or press `Ctrl+Enter`.

**Expected result:** The model's reply appears in the chat history. Ask another question to continue the conversation; chat replies do not create Burp issues.

## Conversation context

The chat retains up to 16 successful question-and-answer exchanges for model context. Each new request includes up to 15 previous exchanges plus your new message. Failed requests are not added to this context. Older exchanges remain visible in the editor but are no longer sent to the model. Restate important details when continuing a long conversation.

The current request and its available response are selected automatically when traffic is loaded into the editor. You can deselect either before sending. When you send a message, each included traffic toggle is deselected immediately, even if the model request later fails. Select it again to attach the current request or response to a later message.

{% hint style="warning" %}
Clearing a traffic toggle does not remove traffic already sent in earlier messages: that traffic can still be included in subsequent conversation context. Selecting another request in the same editor does not clear the conversation. Use `Clear chat` before starting a separate investigation.
{% endhint %}

`Clear chat` clears the displayed conversation and the context held by that editor; it does not delete data already received by your provider. Chat history is held in memory rather than saved as Burp issues or restored by the extension after reload.