DOCS Get started

Get started in four steps.

Install Cheburnexus, let it set itself up, and run your first verified query. Pick your setup — the steps below adapt to it.

1

Install the plugin

One extension covers TypeScript/JavaScript, Python and Java. Install it straight from your editor's marketplace — nothing is downloaded from this site.

# VS Code — Quick Open (Ctrl+P)
ext install conceptual-games.cheburnexus
# Cursor, Windsurf, VSCodium — via Open VSX
Extensions → search "Cheburnexus"

TypeScript / JavaScript · Python · Java — VS Code, Cursor, Windsurf, VSCodium

2

Let it install the engine

On first run the extension downloads the analysis engine — one time, verified by checksum. It is not bundled in the extension, so the download is not instant; progress is shown in the status bar.

After that it registers the engine as an MCP server automatically, injecting your project folder — there is nothing to configure.

The Cheburnexus panel in the activity bar shows your plan, engine status and token savings.

3

Activate your plan

Cheburnexus runs at Free limits with no key. For a paid plan, place your claims.json license file in the path shown in the status panel, then restart the IDE.

The key is stored securely in the OS secret store. Enforcement is soft today.

See what each tier unlocks →
4

Run your first query

Open your project and ask — but point the model at Cheburnexus:

“Give me a Cheburnexus summary of this codebase, then explain the main entry points.”

It answers from compiled facts — real numbers, not guesses — and reports how many tokens it saved.
1

Import the package

Cheburnexus for Unity ships as one importable package. Grab it either way:

  • Direct: download the .unitypackage, then Assets → Import Package → Custom Package
  • Asset Store: add to My Assets, then Package Manager → import

Requires Unity 2021.3 LTS or newer.

2

Enable SceneBridge & license

A Cheburnexus panel appears under Window → Cheburnexus. The read-only scene viewer runs free out of the box; paste a Pro / ProMax key there to unlock live edits.

Compare engine tiers →
3

Connect your coding agent

The Unity package runs the same MCP server. With the Editor open, connect your agent:

# Claude Code
claude mcp add cheburnexus -- cheburnexus mcp --unity
# scene tools appear once the Editor is running
4

Run your first query

Ask your agent about the open scene — it reads the live hierarchy, prefabs and editor-time wiring that grep can't see.
Troubleshooting
Tools not visible

Ensure the engine finished downloading, then restart the window so the MCP server registers.

Engine not installed

Use the Engine node in the Cheburnexus panel to (re)download it. Plans are per-family: a code-plugin license won't unlock the Unity package.

Unity: scene tools missing

Live scene tools only appear while the Editor is open. If they're still absent, reopen the Window → Cheburnexus panel to restart the bridge.

"0 usages" looks wrong

That's grep talking. Ask the agent to run locate_instances — it sees serialized references grep never will.

Still stuck? [email protected] — we answer with facts, not guesses.