> 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/actions/desktop/window/select-window.md).

# Select Window

This is a pre-built action located under the **@Window Element**. The functionality of this action in Avo Assure is to select the desktop window specified in the Input Value.

### Syntax

**Input Value:** `<Desktop_Application_Window_Name/Process ID>;<index(Optional)>`

| Argument                                                              | Description                                                                                                   |
| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| <p>\<Desktop\_Application\_Window\_Name/Process ID><br>(Required)</p> | Provide either the exact name of the application window or its Process ID to identify the target application. |
| <p>\<index><br>(Optional)</p>                                         | Specify the index to select window                                                                            |

{% hint style="info" %}
**Note:**\
The Select Window action allows interactions to be directed to the specific desktop window. It must be used before performing any operation within a new or secondary window.
{% endhint %}

**Output Value**

| Argument                                                    | Description                                                 |
| ----------------------------------------------------------- | ----------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable holds result as **True** or **False** |

**Example 1**

**Selects a specific desktop window**

The **Select Window** action takes the value from the Input Value column (e.g., **Avo Bank**) to identify and activate the specified desktop window based on its title.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FxiZRv3WLVMNY9vWsvJvb%2Fimage.png?alt=media&amp;token=a163b800-94d2-4865-a3f6-5f746b655a6a" alt=""><figcaption></figcaption></figure>

**Example 2**

**Selects a specify desktop window using optional parameter**

The **Select Window** action takes the value from the Input Value column (e.g., **Avo Bank;1**) to identify and activate the specified desktop window based on its title and index.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FhjzIbRvz0OW35wwzxBkf%2Fimage.png?alt=media&amp;token=dc5a61ea-023b-47f4-a620-bdfb56c8b3dd" alt=""><figcaption></figcaption></figure>


---

# 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/actions/desktop/window/select-window.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.