> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.1/user-guide/user-interface.md).

# User Interface

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="/9.1/user-guide/user-interface/menu-bar.md">Menu Bar</a></td><td>Learn about the various options in the main menu bar</td></tr><tr><td><a href="/9.1/user-guide/user-interface/desktops.md">Desktops</a></td><td>Understand how to create, save, and switch between different desktops</td></tr><tr><td><a href="/9.1/user-guide/user-interface/command-line.md">Command line</a></td><td>Check IDA command-line input field to execute advanced operations</td></tr><tr><td><a href="/9.1/user-guide/user-interface/license-manager.md">License Manager</a></td><td>Manage your license access, including floating licenses</td></tr><tr><td><a href="/9.1/user-guide/user-interface/how-to-use-list-viewers-in-ida.md">How To Use List Viewers in IDA</a></td><td>Discover how to efficiently interact with IDA's list viewers</td></tr><tr><td><a href="/9.1/user-guide/user-interface/database-conversion-from-idb-to-i64.md">Database Conversion from idb to i64</a></td><td>Learn how to convert 32-bit database files (IDB) to 64-bit format</td></tr></tbody></table>


---

# 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.hex-rays.com/9.1/user-guide/user-interface.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.