> 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/configs-reset-after-update.md).

# My keybinds and configs reset after an update

Client updates should keep your configs; if they did not, look for the saved snapshot first.

{% hint style="info" %}
Client updates should keep your configs; if they did not, look for the saved snapshot first.
{% endhint %}

## Where your settings live

Keybinds are part of your module settings, and module settings are part of a config.

## Recover your setup

1. Open the ClickGUI and go to Configs.
2. If your config is listed, click Apply profile. Your modules and keybinds come back.

## Avoid it next time

Save a named config after you finish setting up. Default is the shipped baseline and applying it will drop your changes. Keep a copy of your config file somewhere safe. See [Back up or share a config](/cesium-docs/support/backup-or-share-config.md).

## If a config was wiped by the update

Tell us in [Discord](https://discord.gg/3QBFFwbbH) with the client build you updated from and to. Both are shown in the launcher's Session info panel.


---

# 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/configs-reset-after-update.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.