> Agent-readable docs index: /llms.txt. Download /docs.zip to grep all markdown files locally.

---
title: Manage Extensions
description: "The cheat's extension manager: your developer extensions, market downloads, extension settings, and snapshots."
icon: package
sidebar_position: 2
---

# Manage Extensions

**Manage Extensions** in the cheat menu lists your local projects and market
extensions:

* **Developer**: your own extensions, loaded from disk. This section requires
  active [Developer mode](/cs2/product/developers/developer-mode).
* **Market**: extensions you downloaded from the market. Developer mode is not
  required; your CS2 subscription and the extension's access terms still apply.

After buying or renewing Developer mode, restart the cheat so the client
receives the updated access on the next injection.

<Frame caption="Your extensions under Developer, downloaded ones under Market">
  <Image src="/images/cs2/developers/manage-extensions.webp?v=674e6c0b" alt="Manage Extensions with the menu of a developer extension open" width="1927" height="1375" placeholder="data:image/webp;base64,UklGRoQAAABXRUJQVlA4WAoAAAAQAAAADwAACgAAQUxQSDkAAAABYBPbVqMnABeowAM1eKGmxAGSchSBAbbcjuAgIiaA220F6H87PhuUHHxVHiwnDqZhBxF4x+22AgAAVlA4ICQAAABQAQCdASoQAAsAAsBMJZwABAAAAP71wDZ7oOULMatHL6BIYAA=" />
</Frame>

## Create a developer extension

<Steps>
  <Step title="Create the extension" icon="folder-plus">
    Press **Create new developer extension** at the end of the **Developer**
    section and give it a name.
  </Step>

  <Step title="Open its folder" icon="folder-open">
    Choose **Open Folder** from the extension's **…** menu and open `main.lua`
    in your editor. This is the extension's entry point; `extension.json`
    contains its language and dependency settings.
  </Step>

  <Step title="Run your code" icon="play">
    Save your code and enable the extension in **Manage Extensions**. Check
    the client's console for `print` output and any errors.
  </Step>
</Steps>

Scripts and libraries are created the same way. Whether an extension is a
library is decided on the market, when you
[publish it](/cs2/product/developers/publishing).

## The extension menu

The **…** menu next to each developer extension holds the actions you need
most:

| Item                 | What it does                                                                                                                        |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Open Folder**      | Opens the extension's folder on disk.                                                                                               |
| **Upload to Market** | Uploads the current files as a build of a market item. Submit it for review from the item page to complete the publication process. |
| **Settings**         | Opens the extension's settings.                                                                                                     |

## Check changes in the game

Save your changes, return to the game, and open the Neverlose menu. An enabled
local extension reloads when the client detects the changes. If the extension
is disabled, enable it to load the updated files.

Reloading runs `main.lua` again. See the
[reload rules](/cs2/api_reference/extensions/anatomy#hot-reload) for the
technical details.

## Extension settings

<Frame caption="Snapshots on the left, requirements on the right">
  <Image src="/images/cs2/developers/extension-settings.webp?v=ae4db477" alt="Extension Settings with Snapshots and Requirements" width="1673" height="1335" placeholder="data:image/webp;base64,UklGRogAAABXRUJQVlA4WAoAAAAQAAAADwAADAAAQUxQSDkAAAABT6AmABI2yvj4CEIFMxkR8Ypm9ghFkSQ1v7NyWk5GAAxECxiIfpcfAiL6PwG5Q54XyhyP+wtNkAAAVlA4ICgAAABQAQCdASoQAA0AAsBMJZwABAAAAP71w6d+VYW7ntpHgN5Nmty6tsAA" />
</Frame>

**Requirements** lists the modules the extension depends on: `neverlose/<name>`
for a market library, `local/<name>` for one of your own local extensions, or a
bare name such as `ffi` for a built-in module. Load the module with `require`
in your code as well. See [Requirements](/cs2/api_reference/extensions/requirements)
for the exact forms and module rules.

Before publishing, replace `local/...` dependencies with published libraries.
Lua files inside the same extension, such as `helpers.lua`, are loaded with
`require("helpers")` and do not need separate Requirements entries.

**Snapshots** keep earlier versions of the extension:

* **Published**: uploaded builds, including entries marked **Pending**. A
  Pending snapshot is not confirmation that the build has been approved or
  that you have completed the submission on the market.
* **Local drafts**: copies the cheat saves before every upload.

Open a snapshot to see what changed and roll the extension back to it. Check
the item page on the market for its submission and approval state.
