> 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/support/move-device-slot.md).

# I got a new PC. How do I move Cesium to it?

There is no self-serve reset yet. Ask support and the team moves your device.

{% hint style="info" %}
There is no self-serve reset yet. Ask support and the team moves your device.
{% endhint %}

## Why this is needed

During the beta your account covers one PC, registered the first time the launcher loads Cesium there. A new PC is a new device.

## Steps

{% stepper %}
{% step %}
Ask on the support page of the dashboard, or in Discord at [cesiumclient.com/discord](https://discord.gg/3QBFFwbbH), and say you have moved to a new PC.
{% endstep %}

{% step %}
The team resets your device.
{% endstep %}

{% step %}
Install the launcher on the new PC, sign in, and load Cesium. The dashboard shows the new device as a pending sign-in. Approve it and load again.
{% endstep %}
{% endstepper %}

## Hardware upgrades on the same PC

Changing a major component can look like a new device. If the launcher stops recognizing your PC after an upgrade, follow the same steps.

See also [Devices](/cesium-docs/account/devices.md).


---

# 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/support/move-device-slot.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.