> 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/menu-bar/windows/output-window.md).

# Output window

The **Output window** appears at the bottom of IDA's interface by default and serves two key purposes:

* Displays various IDA messages and notifications.
* Provides a command line interface (CLI) for executing IDC or IDAPython commands.

![Output window](https://2148706108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI8M5PHYsEEeI7qsOcPAD%2Fuploads%2Fgit-blob-0db414a06137c81b3fe6201a1e28e59b0733cc3a%2Foutput-window.png?alt=media)

If closed, you can reopen it via **Windows -> Output window**.

## Context Menu Options

Right-click in the Output window to access these options:

* **Select All**: Selects all content in the window
* **Find/Find next**: Searches for a specific string
* **Clear**: Removes all previous messages from the window
* **Copy to CLI**: Places selected text into CLI field
* **Save to file**: Exports window content to a .log file
* **Show timestamps**: Displays time information with each message
* **Font...**: Customizes the text appearance (font, style, size)

You can duplicate all messages appearing in this window to a file. To do this, you have to define an environment variable before starting IDA:

```
set IDALOG=logfile
```


---

# 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/menu-bar/windows/output-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.