> For the complete documentation index, see [llms.txt](https://cesium.gitbook.io/cesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesium.gitbook.io/cesium-docs/support/clickgui-will-not-open.md).

# The client loaded but the ClickGUI will not open

Check that Cesium is really in the game, then check the key.

{% hint style="info" %}
Check that Cesium is really in the game, then check the key.
{% endhint %}

## Confirm Cesium is loaded

Look at the launcher. Session info should show the instance, a module count, and a build. If the launcher says No instance running, Cesium is not loaded. Load it again. See [Load Cesium into a running game](/cesium-docs/getting-started/load-cesium.md).

## Check the key

If you changed it, use the key you set.

## Check what else has the key

Another program, an overlay, or a Minecraft keybind on the same key may be swallowing it. Try the ClickGUI key with other overlays closed.

## Check the game state

The ClickGUI opens in game. It will not open from the main menu or while another screen (inventory, chat) is open.

## Last resort

Close Minecraft, start it again, load Cesium again, and try the key before doing anything else. If it still does not open, ask in [Discord](https://discord.gg/3QBFFwbbH) with your client build (from Session info in the launcher).


---

# 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://cesium.gitbook.io/cesium-docs/support/clickgui-will-not-open.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.