> 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/account/minecraft-accounts.md). # Minecraft accounts Up to three Minecraft accounts can use Cesium on your device. Up to three Minecraft accounts can use Cesium on your device. ## Adding an account Sign in to Minecraft with the account you want to use, then load Cesium. The first time an account is used, the dashboard shows a pending sign-in for you to approve. Once approved, it appears on the Devices page with its username. ## The limit Three Minecraft accounts per device during the beta. If you already have three and want another, remove one from the dashboard first. ## Removing an account On the Devices page, hover an account and click Remove. ## Which account is in use Cesium loads into whatever Minecraft account is signed in to the running game. --- # 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/account/minecraft-accounts.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.