Home

cie — Code Insight Engine

The only code graph that knows which tasks and tests actually implement your code. This wiki is the developer home: architecture from the codebase, and how-tos for everything. The README stays lean — demo, install, contributors — everything else lives here.

New here? Watch the 30-second demo on the README, install with one command, then read Architecture — it's written from the codebase with file references, not marketing.

Navigation

Start with	Page
How the pieces fit (graph → policy → front-ends)	Architecture
Install + serve to Claude Code / Cursor / Codex	How-to: install and serve to your MCP client
Embedded SQLite vs Neo4j — the one selection rule	How-to: choose your storage backend
Ask "what breaks, and which tests catch it?"	How-to: ask impact questions

How-tos

• Install and serve to your MCP client — one-click, the one-liner, multi-project
• Choose your storage backend — auto, --backend, CIE_BACKEND, and when Neo4j
• Run the Neo4j team mode — shared graph, --project namespaces, env config
• Index and keep it fresh — index, reindex, watch, freshness_report
• Ask impact questions — callers/affected_by/test_map workflows
• Use the task & QA layer — tasks, PRD hierarchy, traceability
• Enable semantic search — env-gated embeddings, hybrid retrieval
• Share a snapshot or serve HTTP — export-html, the HTTP tool-mount
• Understand policies and the write boundary — readonly vs full, server-side enforcement
• Troubleshoot — real errors and their real fixes

Reference

• Extraction pipeline — three passes, 9 languages
• Data model — node kinds, edge kinds, confidence
• Tool reference — the ~135-tool surface
• Security and determinism
• Two tiers · Project layout · Where everything lives
• Contributing (details) — dev setup, suite, conformance harness, the honesty bar
• Benchmarks — headline numbers with links to raw artifacts

Where the truth lives

This wiki is narrative. Evidence stays in the repo: benchmark methodology + raw JSON (docs/benchmarks.md), the demo's uncut casts + production log (docs/demo), and the dated record of every change (CHANGELOG.md). If wiki and code ever disagree, the code wins — then this wiki gets a fix.