# Recording

In the context of Stoobly, recording means to intercept HTTP requests with the agent and save them to the local filesystem.

## Why record HTTP requests?

Recording HTTP requests saves previously seen requests and their responses. This enables you to:

* Mock future requests that match and return realistic data
* Replay requests at any time
* Gain deeper insight into a scenario's requests

## What gets recorded?

The following HTTP request components get recorded:

* Hostname
* Port number
* Path
* Headers
* Query Parameters
* Body
* Response Headers
* Response Body

## When are HTTP requests recorded?

<figure><img src="/files/amvKhodUXdINJUU6Svmq" alt=""><figcaption><p>Recording a HTTP request with Stoobly</p></figcaption></figure>


---

# 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.stoobly.com/core-concepts/agent/intercept-modes/recording.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.