Skip to content
Back to News
release
v9.4
announcement

CKB 9.4.0: Fresh Answers Between Reindexes, a Done Check, and a Plugin That Needs No Setup

By CKB Team

CKB 9.4.0 is out. The short version: answers stay correct while you edit, there is a check for "did I finish this change", the Claude Code plugin works without setup, and a few things got smaller or went away. The full list is in the CHANGELOG; the release is on GitHub.

Fresh answers between reindexes

Until now, a query after an edit answered from the index as it was at the last ckb index. In 9.4.0 the server diffs the working tree against what the index was built from and patches the loaded index in memory. Unchanged files are shared, changed ones are remapped (occurrences on unchanged lines move, those on changed lines are dropped), deleted files are removed and renames are followed. The index on disk is never touched.

For Go and TypeScript, declarations on changed lines and in new files are added under the indexer's own IDs. References on changed lines are resolved exactly or left out: there is no edge from a name alone. References that come from the overlay carry source: "overlay" on analyzeImpact items and prepareChange dependents.

Replayed over CKB's last 30 small Go commits (index at the parent plus the overlay, against a fresh index at the commit), there were 0 differences on 130,951 occurrences on unchanged lines and 1,411 of 1,411 overlay references were identical. Building the overlay takes 20-90 ms, median 39 ms. CKB_OVERLAY=0 turns it off.

The done check

assessChange and ckb changes now include a doneCheck. It lists each use of a changed declaration that your diff left as it was, with file, line and code, under one of three statuses: open, clear or not_assessed.

ckb changes --check

The exit code is 0 for clear, 2 for open, 3 for not assessed. It compares text and compiles nothing, and clear has to be earned: an index behind HEAD, a cut reference list, a failed lookup or a changed file outside the index all give not_assessed.

It does not catch everything, and open does not mean broken: a use the diff left alone may still compile. Treat open as a list to look at, not a verdict.

A Claude Code plugin that works without being asked

claude plugin marketplace add SimplyLiz/ckb && claude plugin install ckb@lisa

The plugin starts a ckb pinned to its release: one on your PATH if it has the plugin's major version and at least its minor, otherwise a copy installed once into the plugin's data directory, otherwise npx -y @tastehub/ckb@9.4.0. /ckb:review now runs ckb review before the model reads the skill and injects the result, so the structural pass no longer depends on the model choosing to run it. ckb review --compact is new for this: one line of JSON instead of the 38 KB the full output reached on 4 commits of CKB, which is past what Claude Code inlines from an injected command.

Smaller output over MCP

findReferences over MCP used to answer with one JSON entry per reference. The default is now plain text, one file:line: [use] code per reference. detail: "files" gives line numbers per file as JSON, detail: "full" the original list, and ckb refs prints the same text. getCallGraph now has a response budget: it returns the 20 nodes closest to the symbol and says in truncation how many it cut.

Upgrades no longer need a fresh .ckb

The derived symbol cache, FTS content and cached answers are versioned and rebuilt automatically, so upgrading does not mean deleting .ckb. The SCIP index also loads without .ckb/scip_derived.gob now: on four repos with 15-50 MB indexes the cache made loading 20-150 ms slower, and the file is deleted on the next load.

Cartographer is removed

CKB no longer links the Cartographer library. Cycles, co-change, bridges and god modules now come from CKB's own SCIP index and git history, in every build and every indexed language.

  • Import cycles are read off the SCIP index and classified by import site, so import type and lazy imports cannot close a cycle. This covers TypeScript, JavaScript and Python. arch-health reports a cycle only when your change touches one of its files.
  • A bridge is an articulation point of the file graph that cuts off at least 3 files. The risk multiplier is 1 + min(cut, 50)/50, capped at 2.0, and the factor is named bridge_cut.
  • Co-change reads the last 500 commits directly.
  • Removed with nothing in their place: the MCP tools queryContext, contextHealth, getArchitecturalEvolution, getBlastRadius and renderArchitecture. CKB now has 106 tools, down from 111. getArchitecture no longer returns healthScore or layerViolationCount.

Notable fixes

  • Security: ckb review wrote co-changed file paths into a sh -c script, so a path containing $(...) or backticks, committed on a PR branch, ran as a command when you reviewed that PR. The lookup now runs one git log with the paths as argv and no shell. If you run ckb review on untrusted PRs, for example in CI, update.
  • A Flutter app now indexes on the first try. A root manifest names the primary language; before, a nested package.json made a Dart repo count as JavaScript.
  • ckb unwired on CKB went from 1,938 unwired symbols to 620 after the walk started following Go init functions.
  • analyzeImpact, prepareChange and compareAPI point agents to assessChange instead of the deprecated analyzeChange.
  • MCP tools now carry annotations: 88 tools are marked readOnlyHint, so Claude Code can run them in parallel. CKB also answers the stateless MCP 2026-07-28 revision next to the old handshake.
  • ckb init keeps .ckb/ and index.scip out of git status through .git/info/exclude.

There are many more fixes, mostly in the done check across Go, TypeScript, Python and Rust. Read the full CHANGELOG or the release notes for the list. Questions and bug reports go to GitHub Discussions.