CKB works behind your agent
You talk to your coding agent the way you always do. CKB sits underneath it, feeding it evidence about your codebase.
In the normal coding workflow, CKB works behind your agent. It does not replace it.
We call the tool the developer already uses — Claude Code, Cursor, Windsurf, VS Code and other supported agents — a consumer. A consumer talks to CKB the same way it talks to any other MCP server: it asks a question, CKB answers with evidence gathered from your codebase. You never talk to CKB directly.
What happens at setup
One command, and CKB stays fresh from there.
npm install -g @tastehub/ckbInstall the CKB CLI.
ckb initSet up CKB in your project.
ckb indexBuild the symbol index CKB queries from.
ckb setupConnect CKB to your coding agent.
How your agent picks capabilities
CKB exposes 106 capabilities in total. Your consumer doesn't load all of them — it starts with a default set of 27 core capabilities.
When a task needs something outside that default set, the agent expands its own access to the full 106, once per session. You don't configure this or pick from a list.
Evidence sources
CKB layers multiple backends. Not all of them are available in every environment — here's what each one needs.
| Source | Precondition | What it gives you |
|---|---|---|
| Git | Always available. | History, blame, co-change — works the moment your project is a git repo. Co-change partners are read from the last 500 commits. |
| SCIP | Needs ckb index and a language indexer. | A compiler-grade symbol index for precise navigation and references. Import cycles, bridges and god modules are computed from it, in every build. |
| LSP | Needs a language server on PATH. | Falls back to whatever language servers you already have installed. |
| LIP | Optional, separate install. | Live introspection for languages where static analysis alone falls short. |
CKB never modifies your source code
CKB analyzes and explains your code — your agent decides what to change, CKB only tells it what it's looking at. A few capabilities do write, but only into CKB's own store, never your codebase: recording a decision (recordDecision) or annotating a module writes a Markdown file and database entry inside CKB's data, not your source tree.