> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/code/debugging.md).

# Debugging

This section collects tools and techniques for understanding, inspecting, and iterating on your Gum UI while your game is running.

* [Hot Reload](/gum/code/debugging/hot-reload.md) — push changes saved in the Gum tool into the running game without restarting, so you can adjust layouts, colors, and component structure and see the results immediately.
* [Runtime Snapshot](/gum/code/debugging/runtime-snapshot.md) — export the live UI tree to a Gum project you can open and inspect in the tool; the reverse of hot reload, and especially useful for code-only UIs.

## See also

Some debugging guidance lives alongside the subsystem it relates to:

* [Troubleshooting Events](/gum/code/events-and-interactivity/troubleshooting-events.md) — diagnosing why clicks, hovers, and other input are not reaching a control.
* [Measuring Draw Calls](/gum/code/performance-and-optimization/lastframedrawstates.md) — inspecting how many draw calls your UI produces.
* [Measuring Layout Calls](/gum/code/performance-and-optimization/measuring-layout-calls.md) — finding excessive layout work.
* [Files and Fonts Troubleshooting](/gum/code/files-and-fonts/troubleshooting.md) — resolving missing textures, fonts, and content-path problems.


---

# 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.flatredball.com/gum/code/debugging.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.