> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/echo/scanning.md).

# Scanning

Scanning is when Echo goes through each item in the list automatically.

You can enable scanning in the settings. The other settings have no effect until scanning is enabled.

Scan speed is the speed at which Echo goes through the items in the list. It is measured in seconds its the amount of time that Echo waits after reading an item before it moves on. For example if its set to 2 seconds it will read an item, wait to seconds then move onto the next item.

Scan on app launch means that the app will start automatically scanning as soon as the app is launched. If disabled it will not automatically start

Scan after selection means the app will continue scanning even after you make a selection. If disabled the scanning will stop after you select an item.

Scanning will automatically loop back to the start once it reaches the end. You can adjust how many times it scans through before stopping in the settings.

{% embed url="<https://youtu.be/i5KYUj7epeo?si=vsy-sKbDRZVmATky&t=234>" %}


---

# 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://docs.acecentre.org.uk/products/echo/scanning.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.
