cixlisted

# Code Index (`cix`) — Semantic Code Search & Navigation You have access to `cix`, a semantic code index that understands the codebase via embeddings + AST parsing. The right reflex is **"cix when you don't have a pointer; grep when you do."** **Always invoke `cix` through the harness's shell or terminal execution tool — do not call human-facing cix slash commands from inside a turn.** An agent driving its own work should run `cix search …` / `cix def …` / `cix refs …` directly so the output flows through the normal tool-result pipeline and stays machine-parseable. The `cix` executable must be available in the environment; if it is missing, follow the installation instructions for the current integration rather than substituting MCP. ## When to use which **Reach for `cix` first when:** - The starting point is open-ended ("how does indexing work?", "find the authentication middleware", "where is the main entry point?") - You need cross-file navigation (definitions / references / callers) - You're searching by *meaning*, not by an exact string (`"JWT validation"` should find `verifyToken` even without that phrase) - You're exploring an unfamiliar package or codebase **Skip `cix`, use Read / Grep / Glob directly when:** - A failing test or stack trace already names the file and function — just `Read` it - You're chasing an exact literal: a specific error message, a config key, a commit-message phrase, an import path - You're inside dependencies (`node_modules`, `ven