> 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/core/user-interface/concepts/configuration-files.md).

# Configuration files

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

See documentation about the [IDAUSR](/core/disassembler/concepts/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
* IDAGUI.CFG - graphics mode interface config file
* IDAPYTHON.CFG - configuration file for IDAPython. Controls settings such as the Python interpreter path and startup behavior. See the comments inside the file for available options.

{% hint style="info" %}
The IDA text UI and its configuration file (`IDATUI.CFG`) were removed starting with IDA 9.2.
{% endhint %}

In addition, the file `idapythonrc.py` in your IDA user directory (`$IDAUSR`) runs after IDAPython initializes. It can contain any Python code — for example, importing commonly used modules or configuring logging. See [IDAPython Environment](/getting-started/idapython-environment.md) and the [IDAPython examples](/developer/idapython/idapython-examples.md#idapythonrc) for details.


---

# 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/core/user-interface/concepts/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.