Open Kioku is a local index your coding agent reads before it edits. It shows its evidence — which files, which streams answered, what is missing — declares an edit boundary in a plan, and verifies the finished diff against that plan. Nothing leaves your machine.
The 3.1.0 release lineage was validated end to end on a large Java repository — same protocol and same hardware as the 3.0.4 record; the before/after figures compare against main at c96f61a on the identical corpus.
main at c96f61a, same host as the 3.0.4 recordRetrieval is scored on the production ok context path — the same builder behind ok plan and the MCP build_context_pack tool — on four repositories indexed at a fixed base commit. Each case is a later commit: the query is its subject line, the answer is the source files it changed. Both splits are gated nightly; the table shows holdout.
| Corpus | Holdout cases | R@5 | R@20 | MRR |
|---|---|---|---|---|
| Java, about 10k files | 113 | 0.566 | 0.699 | 0.504 |
| Go application, ~800 files | 84 | 0.679 | 0.809 | 0.535 |
| TypeScript, ~900 files | 166 | 0.825 | 0.874 | 0.658 |
| Python library, ~4k files | 199 | 0.663 | 0.759 | 0.545 |
benchmarks/commit-derived/ by the scripts in the repository; the job fails when a watched metric drops more than 0.03 below its baseline. Queries are commit subjects, not issue text, so these numbers are not comparable with published benchmarks. Method, corpora, both splits, and scripts ↗Every claim on this page traces to a frozen corpus and a machine-readable artifact in the repository — including the numbers that are not good yet.
On the frozen 30-case fixture, all five no-gold tasks now come back at Low confidence instead of being presented as answers (no-gold false-positive rate 0.0; the CI ceiling is 0.25). A low-confidence pack still lists candidates — it tells the caller not to trust them rather than returning nothing. Calibrated abstention is built and gated on held-out performance, and off by default until it earns activation.
A file that merely shares a name can never become a “proven dependency” or a “required test.” Structural claims carry typed proofs; heuristic candidates stay clearly labeled suggestions.
Every index builds into its own generation and publishes with one atomic switch — designed so a reader never sees a half-built index; a kill mid-build or a downgrade falls back to the last good generation.
The evidence below identifies the exact build lineage, publishes aggregate results, and keeps caveats beside the claims they qualify. The newest record also publishes what got faster — and what still isn’t perfect.
Validated end to end on a large Java workload — and honest about the result. The adjacent artifacts are the source of record.
The JSON records build source, host profile, configuration, workload totals, measurements, quality checks, and limitations — including what still isn’t perfect. Repository identity is withheld, so exact replay is not claimed.
The repeated structural run reproduced identical totals, the exact class lookup returned the correct class in 0.02s, and missing compiler-grade SCIP evidence stayed visible instead of being treated as present.
Open Kioku combines deterministic code intelligence with explainable retrieval signals. Exact repository facts do not get demoted by a fuzzy match.
Definitions, references, paths, and exact evidence stay authoritative. Heuristics can help retrieval without rewriting repository truth.
Ranked snippets, exact line ranges, impact, nearby tests, and caveats give the next agent step a bounded evidence set.
Optional semantic retrieval stays on-device and can use persistent approximate nearest-neighbor search while exact-flat remains the correctness oracle.
Co-change, churn, ownership, reviewer, provenance, renames, and similar-change signals are derived from bounded local Git history.
Validation candidates are selected from indexed tests and repository evidence before a change begins, not as an afterthought.
Plans define edit boundaries. Verification compares the actual changed files with those boundaries and reports evidence caveats.
Click through the same sequence an agent can use before, during, and after a repository change.
The default workflow is designed for local repository intelligence rather than a hosted code-index service.
Core search and evidence are stored under the repository’s local .ok/ data.
The MCP server provides evidence tools; source edits remain in the normal editor and agent workflow.
Command execution and model downloads are policy-gated. Default configuration includes network denial, and denial fails closed. Local semantic search needs no hosted embeddings API.
ok prove reports index and validation signals while intentionally omitting source snippets.
Install from the channel you already use, run one setup command, then ask for evidence on the task you actually care about.
npm install -g open-kiokuPulls the native binary for macOS, Linux, or Windows through platform packages.
cargo install open-kioku-cliOr cargo binstall open-kioku-cli for the prebuilt binary.
ok-{linux,macos,windows}-*Binaries with SHA256SUMS, an SBOM, PROVENANCE.json, and build-provenance attestations. Release trust ↗
Formula/open-kioku.rbFormula tracked in the repository; no public tap is published yet.
claude_plugin.jsonPlugin manifest and .claude-plugin/ marketplace entry in the repository.
.cursor-plugin/ · .codex-plugin/Agent, rules, and skill for Cursor; plugin manifest for Codex.
glama.json · smithery.yamlServer manifests for the Glama and Smithery MCP directories.
ok setup agent claude|cursor --repo . --applyClaude Code · Cursor · Codex · Gemini CLI