cix for Codex

Stop letting Codex guess your codebase.

Codex writes code well and starts each session knowing nothing about your repository. cix gives it a live index to query, so it can find what already exists rather than writing a second version of it.

$ cix install --client codex

What Codex 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 Codex

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, invoked with $

Codex's equivalent of slash commands is its Skills system, so the same three commands are reached as $cix-init, $cix-index and $cix-errors. Same intent as the Claude Code set, different invocation.

The same session-start behaviour

Codex supports the same hook events as Claude Code, so the cix tool surface is announced at the start of a session in exactly the same way.

Guardrails run as a policy mode

Rather than a set of separate hooks, Codex enforcement is a single policy that denies edits to indexed files, so --guardrails wires one registration instead of several.

Local only, for now

Pointing Codex at a remote cix server with --url is not implemented yet; the install reports it and skips rather than appearing to succeed. Local stdio is the supported path.

What it does not do

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