# BugBug test recorder

When you run a test in the recording mode, you can notice that there is an additional BugBug action panel on the right. 

{% hint style="info" %}
To run or record the tests, you need to install[ BugBug Chrome extension](/quick-start/install-test-recorder.md).
{% endhint %}

<figure><img src="/files/u7xiSsSeGa7ujd2KHdSB" alt=""><figcaption><p>BugBug test recorder</p></figcaption></figure>

By default, BugBug is [recording all clicks](/recording-tests-steps/recording-clicks.md), but also it catches selecting form elements and navigating to URLs, and [typing in the text fields](/recording-tests-steps/recording-keyboard-typing.md).&#x20;

Use the recorder's buttons to change what you want to:

* [record hover](/recording-tests-steps/recording-hover.md)
* [add assertions during recording](/recording-tests-steps/recording-assertions.md)
* [record drag & drop](/recording-tests-steps/recording-drag-and-drop.md)


---

# 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://docs.bugbug.io/recording-tests-steps/bugbug-test-recorder.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.