> 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/releases/launcher-1-0-0.md).
# Cesium Launcher 1.0.0
The first launcher release, replacing the jar loader as the one thing you install.
{% hint style="success" %}
Requires Windows 10 or newer. Sign in with your Cesium account; the launcher does the rest.
{% endhint %}
## What changes
The old Cesium Loader (.jar, version 0.8, Java 17) is retired and no longer offered for download. The launcher takes over everything the jar did, and it does the sign in, download, and update work for you.
## Sign in and load
You sign in to the launcher with your Cesium account. The launcher uses that account to check your access and fetch the client. There is no separate client download.
* **Load Cesium.** One button. It attaches Cesium to the Minecraft instance you already have running.
* **No instance running.** What you see when the launcher cannot find a Minecraft process. Open Minecraft, and the button becomes available.
## Session panels
Once Cesium is loaded, the home screen shows three panels.
Session activity
A live activity chart for the current session.
Client timeline
Recent module changes, so you can see what was turned on or off and when.
Session info
Instance, Modules, Memory, Process, Build, and Launcher version.
## Automatic client updates
The launcher keeps the client up to date on its own. When a new client version ships, it fetches the update the next time you open it, before the client starts.
---
# 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/releases/launcher-1-0-0.md?ask=&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.