> 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/devices.md). # Devices Cesium runs on one Windows PC during the beta, and new devices are approved from the dashboard. Cesium runs on one Windows PC during the beta, and new devices are approved from the dashboard. ## How it works The first time the launcher loads Cesium on a PC, that machine is registered to your account. The Devices page of the dashboard lists it, along with the Minecraft accounts that have been used on it. ## Approving a new sign-in When the launcher is used on a PC, or with a Minecraft account, that your account has not seen before, the load pauses and the dashboard shows a pending sign-in with Approve and Deny buttons. Approve it and press Load Cesium again. A pending request stays open for 24 hours. If you deny one, the launcher stops retrying for a few minutes. ## Moving to a new PC During the beta your account covers one device, and there is no self-serve reset yet. To move Cesium to a new PC, ask on the support page of the dashboard or in Discord at [cesiumclient.com/discord](https://discord.gg/3QBFFwbbH), and the team resets the binding for you. ## Signing in from a browser The dashboard is a website and does not count as a device. The device limit only applies to 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/account/devices.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.