> For the complete documentation index, see [llms.txt](https://unixx.shop/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unixx.shop/docs/games/cs2-cheat-setup-download-and-installation-guides/choose-a-cs2-product-setup-guide/pellix-cs2-cheat-setup-guides/pellix-cs2-cheat-user-guide.md).

# Pellix CS2 Cheat User Guide and Keybinds

Use the Pellix CS2 cheat interface with the default menu controls. Find the Delete keybind, navigation method, settings guidance, and troubleshooting links.

## Pellix CS2 cheat user guide and keybinds

Open the Pellix CS2 interface with `DELETE` and navigate using your mouse. Complete the [Pellix CS2 installation](/docs/games/cs2-cheat-setup-download-and-installation-guides/choose-a-cs2-product-setup-guide/pellix-cs2-cheat-setup-guides/download-and-install-pellix-cs2-cheat.md) before using the menu.

### Default keybinds

* Open/Close: DELETE
* Navigate: Mouse

{% hint style="info" %}
You can modify keybinds within the settings of the software.
{% endhint %}

### Frequently Asked Questions

#### How do I open the Pellix CS2 menu?

Press `DELETE` after starting the loader.

#### Where can I find Pellix troubleshooting?

Use the [Pellix CS2 support guide](/docs/games/cs2-cheat-setup-download-and-installation-guides/choose-a-cs2-product-setup-guide/pellix-cs2-cheat-setup-guides/pellix-cs2-cheat-support-and-troubleshooting.md) for current issues and support options.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://unixx.shop/docs/games/cs2-cheat-setup-download-and-installation-guides/choose-a-cs2-product-setup-guide/pellix-cs2-cheat-setup-guides/pellix-cs2-cheat-user-guide.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 `build a script that syncs our docs to a CMS` 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.