cix for Claude Code

Stop letting Claude Code guess your codebase.

Claude Code is good at writing code and has no memory of your project between sessions. cix gives it a live index to query — so it looks things up instead of inferring them from whatever files it happened to open.

$ cix install --client claude

What Claude Code 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 Claude Code

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 slash commands

Installing adds /cix-init, /cix-index and /cix-errors to your session, so re-indexing or checking parse errors is a command rather than a trip to the terminal.

The tool surface is announced at session start

cix registers a session-start hook, so Claude Code learns which tools exist and when to use them at the beginning of a session rather than discovering them by accident mid-task.

Claude Desktop is configured too, on Windows

Claude Desktop reads a different configuration file from the CLI. On Windows, installing for Claude Code configures both, which is the one case where two products share a name and not a config.

The fullest guardrails support

The optional --guardrails profile covers the most ground here: it blocks the supported built-in write and edit tools on indexed files, guards markdown edits and shell workarounds, and routes reads toward the cix equivalents.

What it does not do

cix does not write your code or replace Claude Code. 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.