Documentation

Start with evidence.
Keep uncertainty visible.

Install Open Kioku, connect your coding agent over local MCP, and use the plan → edit → verify loop on the repository you already have.

Quickstart →All reference docs ↗

First win

Install and connect

The setup command indexes the current repository, writes repository-scoped agent guidance and MCP configuration, and checks that the local server responds.

npm install -g open-kioku
ok setup agent cursor --repo . --apply

Use claude instead of cursor for Claude Code. Run without --apply first to preview changes.

CursorRepository-scoped MCP setup→ Claude CodeLocal stdio MCP setup→ CodexConnect Open Kioku tools→ Gemini CLILocal repository evidence→

Core workflow

Plan before editing. Verify after.

Build local evidence

ok index . stores symbols, relationships, tests, history, documentation, and optional semantics under .ok/.

Compile a plan

ok plan "your task" returns bounded context, impact candidates, validation targets, provenance, and explicit caveats.

Verify the change

Use verify_change or the CLI verification flow to compare actual edits with planned boundaries and validation evidence.

Evidence you can inspect

Proof, methodology, and limitations.

Performance claims are observations tied to a release and host—not universal guarantees.

Large-Java JSON evidenceRelease, environment, workload, results, and caveats↗ Validation methodologyProcedure, evidence boundary, and limitations↗ Public large-repository proofReplayable repository audit↗ Proof modelHow Open Kioku reports usefulness and uncertainty↗