> 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.md).

# Getting started

From nothing installed to a saved config, in four steps.

Cesium does not install into Minecraft. You install one program, the Cesium Launcher. When Minecraft is running, the launcher loads Cesium into it. Everything else (modules, keybinds, configs) happens inside the game through the ClickGUI.

{% hint style="info" %}
You need a Cesium account with beta access before step 1 does anything useful. Beta access is free and comes from the Discord server at [cesiumclient.com/discord](https://discord.gg/3QBFFwbbH).
{% endhint %}

{% stepper %}
{% step %}

### Install the launcher

Download it from your dashboard and sign in with your Cesium account. [Full steps](/cesium-docs/getting-started/install-the-launcher.md).
{% endstep %}

{% step %}

### Load Cesium into a running game

Open Minecraft first, then press Load Cesium. [Full steps](/cesium-docs/getting-started/load-cesium.md).
{% endstep %}

{% step %}

### Open the ClickGUI and bind keys

Turn modules on and give them keys. [Full steps](/cesium-docs/getting-started/clickgui-and-keybinds.md).
{% endstep %}

{% step %}

### Save and switch configs

Keep more than one setup and swap between them. [Full steps](/cesium-docs/getting-started/configs.md).
{% endstep %}
{% endstepper %}


---

# 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.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.