> 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/getting-started/clickgui-and-keybinds.md).

# Open the ClickGUI and bind keys

The ClickGUI is where you turn modules on, tune them, and give them keys.

The ClickGUI is where you turn modules on, tune them, and give them keys.

## Opening it

Press the ClickGUI key while in game.

If nothing happens, see [The ClickGUI will not open](/cesium-docs/support/clickgui-will-not-open.md).

## Finding your way around

The left rail has five pages:

* Modules: the full catalog. Tabs at the top filter by category (All, Crystal, Sword, Mace, Misc). A search box filters by name.
* Configs: saved setups. See [Save and switch configs](/cesium-docs/getting-started/configs.md).
* Terminal: a text console for quick commands.
* Themes: the accent color and panel colors of the ClickGUI itself.
* Settings: interface options (Animations, Advanced Options, Blur Background) and a Restore interface defaults button.

Each module row has a switch to turn it on and a star to mark it as a favorite. Favorites sort to the top so the modules you use most are one click away.

## Tuning a module

Click a module's name to open its configuration panel on the right. The panel shows the module's description, then its settings: dropdowns, sliders, toggles, and ranges. A Reset button at the bottom returns that module to its defaults.

Turn on Advanced Options in Settings to see extra tuning fields in each module's panel.

## Binding a key

Most modules have a Keybind field at the top of their configuration panel.

{% stepper %}
{% step %}
Open the module's panel.
{% endstep %}

{% step %}
Click the Keybind field. It waits for a key.
{% endstep %}

{% step %}
Press the key you want. The field shows it.
{% endstep %}
{% endstepper %}

Some modules are keybind only (Auto Safe Anchor, for example) and do nothing unless a key is bound, so bind them before you expect anything to happen.

Keybinds are stored as part of your config. Save a config after binding so you do not lose them.

## Terminal commands

The Terminal page accepts short commands. The set shown in the client is:

* `help`: list commands
* `status`: current client state
* `modules`: list modules and their state
* `toggle <module>`: switch a module on or off
* `config <name>`: apply a saved config
* `theme <name>`: apply a theme
* `clear`: clear the console


---

# 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/getting-started/clickgui-and-keybinds.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.