Skip to content
Roadmap — not shipped

Where CKB is going

Today your agent asks CKB questions. This page describes where that goes next.

Next and Later are not shipped yet. This is direction, not a promise with dates. Everything under Next and Later is written in future tense on purpose.

Shipped — CKB 9.4

An after-change check

ckb changes and the MCP tool assessChange report what your agent actually touched: affected tests, changed public symbols (flagged as a possible contract change, a heuristic, not a guarantee), related decisions and suggested reviewers. In 9.4.0 they also list every use of a changed declaration that the diff left as it was, and ckb changes --check turns that into an exit code.

An activity ledger

A local record of what your agent asked CKB, how long each call took, and how much it returned. It stays on your machine; read it with ckb activity.

Next — CKB 1.x

Honest benchmarks

We will measure an agent working with CKB against an agent working alone, on real sessions, by joining the activity ledger with session transcripts — and publish how we measure it.

Not planned for 1.x: a browser UI, and per-call "tokens avoided" numbers.

Later — CKB 2.0

A console

A console to see what CKB knows about your system, and what evidence your agent received before it acted.

Your agent will state its intent

Instead of your agent asking CKB one question at a time, it will state what it is about to do, and CKB will assemble the relevant evidence itself.

Knowledge you can correct

Corrections to what CKB knows — ownership, decisions — will be kept in versioned files in your repo, not buried in a database.

Tell us what you need

This direction isn't final. If you have a use case it should cover, say so.