> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/automation/desktop-client/creating-an-automation-agent.md).
# Creating an Automation Agent
Learn how to create an automation agent in the Desktop Client. Step-by-step guide covers setup process, key features, and tips for efficient workflow automation.
To run the test case, a corresponding aqua agent must be configured. Each agent has an individual access code. The code is generated in aqua and assigned to the agent. To do this, click on aqua in the main window then select -> Project Configuration -> Automation
Click on Add in the menu and choose a name for the new agent. An access code is automatically generated and must be assigned to the agent by the user. To do this, copy the access code to the clipboard or write it down for later.
The access key is needed for the configuration of agents. It has to be inserted into config file at local agent.
An XML file can be found in the folder where the agent is located like aquaAgentRanorexGui.exe.config
The generated access code must be entered into this file. The corresponding position is highlighted in the following excerpt:
```xml
<…
```
---
# 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.aqua-cloud.io/documentation/automation/desktop-client/creating-an-automation-agent.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.
