> For the complete documentation index, see [llms.txt](https://docs.chromaticsffxiv.com/chromatics-4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chromaticsffxiv.com/chromatics-4/using-chromatics/console.md).
# Console
The **Console** tab is the first thing Chromatics opens to, and it gives you a live view of what the app is doing behind the scenes.
## What you'll see here
* **Startup messages** - which device providers loaded, which devices were detected, and any warnings from your vendor's lighting software.
* **Game connection status** - whether Chromatics has connected to Final Fantasy XIV and is reading game data.
* **Runtime events** - weather changes, zone changes, and other notable things Chromatics reacts to.
* **Errors and warnings** - if something goes wrong, it will appear here first.
You can scroll through the log while Chromatics is running. New entries are added at the bottom as they happen.
## When to check the Console
Most of the time you don't need to look at the Console. But it's the first place to check if:
* A device isn't lighting up the way you expect.
* Effects aren't triggering in game.
* You're about to report a bug and want to know what Chromatics is doing.
## Collecting logs for support
If you're filing a bug report or asking for help, the log here is useful - but the easier option is **Settings → Advanced → Collect Logs**, which bundles the console output, your config files, and some system info into a single ZIP you can share.
See [Troubleshooting](/chromatics-4/support/troubleshooting.md) for more help.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.chromaticsffxiv.com/chromatics-4/using-chromatics/console.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.