> 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/configuration/configuration-files.md).

# Configuration files

The configuration files are searched first in %IDADIR%\cfg, then in %IDAUSR%\cfg.

See documentation about the [IDAUSR](/9.1/user-guide/user-interface/menu-bar/windows/environment-variables.md) environment variable.

In the configuration files, you can use C,C++ style comments and include files. If no file is found, IDA uses default values. IDA uses the following configuration files:

```
 IDA.CFG    - general config file
 IDATUI.CFG - text mode interface config file
 IDAGUI.CFG - graphics mode interface config file
```

In the IDATUI.CFG, you can define the hotkeys and keyboard macros for the text version of IDA. Syntax:

```
        "ActionName" = Value
```

where value may be:

```
        a string:       "Ctrl-F5"
        a char:         'F'
        a scancode:     0x4900
        zero:           0
```

Zero scancode disables the hotkey.

To define the keyboard macros:

```
     MACRO key { key1 key2 key3 ... keyN }
```

where key is a string (key name), char or a scancode. Example:

```
        MACRO   "Alt-W" // this sample macro jumps to "start" label
        {
                "Ctrl-G"
                's' 't' 'a' 'r', 't'
                "Enter"
        }
```


---

# 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/configuration/configuration-files.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.