Make coding agents stop guessing.
Open Kioku is the local-first code intelligence layer for Claude, Cursor, and other MCP clients. It indexes your repo once, then gives agents precise search, symbols, impact analysis, tests, and context packs without sending code to a cloud service.
Replace blind file crawling with indexed evidence.
Open Kioku gives agents a reliable pre-edit routine: search the repo, resolve the symbol, trace references, produce an evidence-backed plan, pick validation targets, and generate a shareable proof report before touching code.
Typical agent loop
- !Repeated grep, glob, and read calls burn context before the agent understands the repo.
- !References are inferred from text matches instead of symbols, imports, and persisted graph edges.
- !Test selection often happens after the edit, when the agent has already guessed wrong.
Open Kioku loop
- OKOne indexed search returns ranked evidence and exact file ranges.
- OKSymbol, reference, impact, and architecture tools share the same local index.
- OKPlans include affected files, edit boundaries, validation candidates, and agent tool calls before edits start.
The pre-edit routine agents should run every time.
This is the workflow to show in Cursor, Claude, and short launch videos: install, index, search, inspect impact, then hand the agent a compact context pack from real indexed output.
One indexed path from question to validation.
The strongest product story is not search alone. It is the complete loop a coding agent needs before making a change.
Find evidence
Search code and files with ranked snippets, line ranges, and confidence signals.
Resolve symbols
Jump to definitions and references without asking the model to infer ownership from text.
Trace impact
Use local graph facts to identify changed files, affected modules, and likely callers.
Validate edits
Build context packs and pre-edit plans that keep agents focused on the smallest useful surface.
Show usefulness without posting source code.
Run `ok prove` on a demo repo or private codebase to produce a Markdown report with indexed counts, task scores, validation signals, and redacted path shapes. The report intentionally omits source snippets.
ok prove ./open-kioku-demo --task tokenok prove /path/to/repo --task "auth flow" --task "release workflow"Copy-paste setup for Claude and Cursor.
Open Kioku runs as a local MCP server over stdio. The install command prints client-specific configuration for your current repo.
ok mcp install claude --repo /absolute/path/to/repook mcp install cursor --repo /absolute/path/to/repoBuilt for codebases people cannot upload.
The trust message matters as much as the speed message. Open Kioku is designed for local indexing, explicit write controls, and predictable MCP behavior.
No hosted index
Metadata stays under `.ok/` in your repo. There is no hosted search service to provision or trust.
No embeddings API required
BM25 search, symbols, and graph operations work locally without uploading code to a model provider.
Write tools gated
Patch and command paths are opt-in, policy-controlled, and separate from read-only context tools.