> 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/avo-assure-client.md). # Avo Assure Client The **Avo Assure Client** is the core component of the Avo Assure platform. It acts as a bridge between the Avo Assure Server and the application under test (AUT), enabling element capture, test case execution, and generation of detailed logs for each executed test step. Before you install and configure the Avo Assure Client, ensure that your system meets the required prerequisites, including supported hardware and operating system requirements, network connectivity, and valid server credentials. This article guides you through downloading and installing the Avo Assure Client, introduces its key features, and explains how to manage the Avo Assure Client token. ## **Prerequisites** Before you install and configure the Avo Assure Client, make sure the following requirements are fulfilled: **System Requirements** * **Operating System**: A supported OS such as Windows 10/11, Windows Server 2016/2019, or specified Linux distributions. * **Hardware**: Minimum 8GB RAM and CPU as per Avo Assure Client specifications. * **Disk Space**: Enough space for installation, logs, and temporary files (minimum **10 GB**). **Network Connectivity** * **Server Access**: Client must connect to the Avo Assure Server over the network. * **Firewall and Ports**: Ensure firewalls allow traffic on required ports for Client-Server communication. **Server Credentials** * **Valid Credentials**: Required to register and connect the Client to the Avo Assure Server. --- # 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/avo-assure-client.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.