> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/recording-a-test-case-with-avo-genius/prerequisite-to-work-with-avo-genius/install-avo-genius-from-store.md).
# Install Avo Genius from Store
Here is the step-by-step process to Install Avo Genius from Web Store **for Chrome:**
1. Click **three dots (...)** located on top right corner in browser.
2. Then, Click **Extensions** and select **Manage Extensions option.**
3. On the top left, Select **Chrome Web Store**
4. In **chrome web store**, Search **Avo Genius** and select the below extension.
5. Click **Add to chrome** button. A pop up will appear for adding the extension.
6. Click **Add Extension.** Avo Genius will now be visible in manage extension window.
{% hint style="info" %}
**Note:** For Edge, users cannot download the extension from the Web Store. They need to enable developer mode and manually upload the Genius package.
{% endhint %}
---
# 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/recording-a-test-case-with-avo-genius/prerequisite-to-work-with-avo-genius/install-avo-genius-from-store.md?ask=&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.
