cix for Gemini CLI

Stop letting Gemini CLI guess your codebase.

Gemini CLI can reason about code it can see. The hard part is deciding what it should be looking at. cix gives it a live index of your project, so that decision is a lookup rather than a guess.

$ cix install --client gemini

What Gemini CLI 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 Gemini CLI

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 TOML, invoked with /

Gemini CLI reads its commands from TOML files, so cix-init, cix-index and cix-errors are installed there and invoked as /cix-init — the same shape as Claude Code, from a different place on disk.

Registered as a trusted MCP server

cix is added to your Gemini settings as a trusted server, so the tools are available without a per-session approval step, along with a session-start hook that announces them.

Guardrails is a deny policy

With --guardrails, cix writes a deny-file-tools policy into your Gemini configuration, so the built-in file tools are refused on files cix has indexed and edits route through the cix tools instead.

What it does not do

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