Install, connect, ask for a plan.
Indexing time depends on the size of the repository; a few thousand files take seconds. Everything is stored under the repository's own .ok/ directory.
cargo install open-kioku-cli, orcargo binstallfor the prebuilt binary.- Binaries with checksums, an SBOM and provenance on GitHub releases ↗.
- The server is read-only by default: source edits remain in Claude Code's own workflow.
Install Open Kioku
The npm package pulls the native binary for macOS, Linux or Windows.
npm install -g open-kioku
Connect Claude Code
One command indexes the repository, writes a repository-scoped
.mcp.jsonand managed guidance, and checks that the local server answers. Run it without--applyto preview; nothing is written.ok setup agent claude --repo . --apply
Or print the server entry and paste it into your Claude Code MCP settings:
ok mcp install claude --repo .
.mcp.json{ "mcpServers": { "open-kioku": { "command": "ok", "args": ["mcp", "serve", "--repo", "/absolute/path/to/repo", "--read-only"] } } }Tell the agent to use it
Add this to
CLAUDE.md. The setup command writes managed guidance of its own; this is the short form.CLAUDE.mdUse Open Kioku before editing. Check repo_status, search_code, get_definition, get_references, impact_analysis, and find_tests_for_change. Build a plan with plan_change first, then edit, and verify after the edit with verify_change.
Turn on the hooks
With the hooks, a boundary is planned from each prompt, a secret-like path is refused, and after an edit the agent is told which calls elsewhere no longer fit what it changed. The Claude Code plugin installs them for you.
ok gate install claude --apply
Sixteen tools, each answering one question.
These are the ones an edit usually needs. Every tool runs against the local index and says what it could not find.
| Tool | What it answers |
|---|---|
plan_change | An edit plan with primary context, impact candidates, validation targets and the edit boundary. |
verify_change | The finished change checked against the plan's boundary. |
build_context_pack | The files, symbols and tests for one task, with confidence and caveats. |
search_code | Ranked code search with paths, line ranges and confidence. |
get_definition | Where a symbol is defined, from the local symbol index. |
get_references | Where a symbol is used, from indexed relationship edges. |
impact_analysis | What a change to a file or symbol reaches, proven edges apart from possible ones. |
find_tests_for_change | The tests that cover what is about to change. |
repo_status | Index health, coverage by language, and what was skipped and why. |
Measured every night on four real repositories: on a TypeScript repository of about nine hundred files, the right file is in the top five about four times in five. The numbers ↗ · All sixteen tools ↗