> For the complete documentation index, see [llms.txt](https://gaffa.dev/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gaffa.dev/docs/changelog/2026/august.md).

# August

### API Updates

#### `loop` action now available

You can now repeat a sequence of nested actions to paginate through multi-page results in a single browser request, rather than sending a request per page. Set `max_iterations` or `iterations` to control how many times it runs, and `stop_on_fail` to have it exit automatically once a "next page" control disappears. Marked as beta while we gather feedback. [Read the docs.](https://gaffa.dev/docs/features/browser-requests/actions/loop)

#### `log_redirects` setting now available

You can now see every URL a browser request passes through before it reaches the final page. Set `log_redirects` to `true` in `settings`, and each redirect hop, including any triggered by actions like `click`, is returned in a new `redirects` field. This is useful for checking campaign links, auditing affiliate routing, or debugging unexpected destinations. [Read the docs.](/docs/features/browser-requests/settings.md#redirect-logging)

#### New API Playground example: pagination with `loop`

Added a ready-to-run template showing `loop` in action, paginating through a listing page and capturing each one. Test it directly in the Playground or read through the request and response. [View the example.](https://gaffa.dev/docs/features/browser-requests/api-playground-examples/loop-through-pagination)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gaffa.dev/docs/changelog/2026/august.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.