> For the complete documentation index, see [llms.txt](https://docs.getcelsius.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getcelsius.net/troubleshooting/unsupported-executor.md).

# Unsupported Executor

What happens on unsupported executors.

If you run the script on an executor that is not [supported](/getting-started/executor-requirements.md), it may refuse to start or be kicked from the game.

## Typical signs

* The script loads nothing and no menu appears.
* You are kicked out of the game immediately or shortly after running the loader.
* A message appears mentioning a missing capability your executor doesn't provide.

## What to do

1. Confirm your executor is on the [supported list](/getting-started/executor-requirements.md).
2. Update your executor to the latest version, then re-run the loader.
3. If you're on an unsupported executor (Solara, Xeno, Sirhurt, or anything unlisted), switch to a supported one. We do not provide support for unsupported executors.

## Why this happens

Scripts like ours need executor capabilities that free or restricted executors often lack. If the capability isn't present, the script cannot run safely and stops instead of half-working.


---

# 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://docs.getcelsius.net/troubleshooting/unsupported-executor.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.