cix for Cursor

Stop letting Cursor guess your codebase.

Cursor's agent moves fast through the code it can see. cix gives it a live index of the whole project, so what it cannot see is a lookup away rather than a guess.

$ cix install --client cursor

What Cursor gains

Find what already exists

Search functions, components, hooks, and types by name before writing a new one — the check that stops a second implementation of something you already have.

Read one symbol, not one file

Pull a single function or class instead of a two-thousand-line file, which is most of why an indexed assistant stays coherent deeper into a session.

See who calls it

List the callers and importers of a symbol before altering its signature, so a signature change starts from the list rather than from hope.

Work from your real schema

Read the actual tables and columns before writing a model, a migration, or a query, instead of inferring column names from how they are used.

Follow your conventions

Check where a new file belongs in your project before creating it, so it lands in the right place the first time.

Trace impact and dependenciesIndividual+

Ask what a change would affect, and what becomes unreachable if a symbol goes away — the questions that decide whether a refactor is safe.

Everything unmarked is on the free tier. Items marked with a plan are available from that plan up — see pricing.

What’s specific to Cursor

The index is the same whichever assistant you use. How you reach it, and how much of the optional enforcement applies, is not.

Commands are Skills on disk

cix-init and cix-index are installed as Cursor skills under ~/.cursor/skills — kept strictly apart from Cursor's own bundled skills, which cix never touches.

Guardrails is a real pre-write gate

With --guardrails, cix registers Cursor's preToolUse hook, and a deny there actually blocks: a convention-violating write is refused before it lands, not flagged after.

Trust is per directory

Cursor loads hooks and tools only in folders you have trusted. In an untrusted folder cix is absent rather than degraded — trust the folder and it appears.

The workflow layer installs here too

On a paid plan, the workflow skills — research, design, plans — install under ~/.cursor alongside the basics, the same surface Claude Code gets.

What it does not do

cix does not write your code or replace Cursor. It answers structural questions — where something is defined, what calls it, what a change would reach — so the assistant spends its context on the problem instead of on rediscovering your project.

Your code is processed to build the index and is not used to train models. See what leaves your machine.