> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/reference/configuration-directives.md).

# Configuration Directives

Configuration directives index — every section of the ColdBox class at a glance.

All application configuration lives in the **ColdBox class** (`config/ColdBox.bx`, or `config/ColdBox.cfc` for CFML apps) inside its `configure()` method. Each top-level struct is a directive:

| Directive                              | Purpose                                                                           | Page                                                                                                        |
| -------------------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `coldbox`                              | Core framework behavior — app name, event name, handlers, caching, error handling | [ColdBox Directives](/reference/configuration-directives/coldbox.md)                                        |
| `conventions`                          | Override default folder/file conventions                                          | [ColdBox Directives](/reference/configuration-directives/coldbox.md#conventions)                            |
| `environments`                         | Per-environment config overrides                                                  | [ColdBox Directives](/reference/configuration-directives/coldbox.md#environments)                           |
| `flash`                                | Flash scope storage                                                               | [ColdBox Directives](/reference/configuration-directives/coldbox.md#flash)                                  |
| `interceptors` / `interceptorSettings` | Registered interceptors and their config                                          | [ColdBox Directives](/reference/configuration-directives/coldbox.md#interceptors)                           |
| `layouts` / `layoutSettings`           | Layout registrations and behavior                                                 | [ColdBox Directives](/reference/configuration-directives/coldbox.md#layouts)                                |
| `settings`                             | Custom application settings                                                       | [ColdBox Directives](/reference/configuration-directives/coldbox.md#settings)                               |
| `executors`                            | Named async executor pools for your app                                           | [ColdBox Directives](/reference/configuration-directives/coldbox.md#executors)                              |
| `sse`                                  | Server-Sent Events behavior (BoxLang only)                                        | [ColdBox Directives](/reference/configuration-directives/coldbox.md#executors--server-sent-events-settings) |
| `modules`                              | Module loading and behavior                                                       | [Modules & Module Settings](/reference/configuration-directives/modules-and-settings.md)                    |
| `moduleSettings`                       | Per-module settings                                                               | [Modules & Module Settings](/reference/configuration-directives/modules-and-settings.md#module-settings)    |
| `cachebox`                             | Caching — see the CacheBox book for the full DSL                                  | [CacheBox Directive](/reference/configuration-directives/cachebox.md)                                       |
| `logbox`                               | Logging — see the LogBox book for the full DSL                                    | [LogBox Directive](/reference/configuration-directives/logbox.md)                                           |
| `wirebox`                              | Dependency injection — see the WireBox book for the full DSL                      | [WireBox Directive](/reference/configuration-directives/wirebox.md)                                         |

## Environment Variables & Java Properties

Any directive can be overridden externally without touching code: [System Settings](/getting-started/configuration/system-settings.md).

## A Note on the Companion Frameworks

CacheBox, LogBox, and WireBox are standalone frameworks with their own books. ColdBox docs cover **how the `ColdBox` class wires them in**; their internal DSLs (cache providers, appenders, binder mappings) are documented in their own books — see [Companion Frameworks](/reference/companion-frameworks.md).


---

# 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://coldbox.ortusbooks.com/reference/configuration-directives.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.