Show HN: Open Kioku – local evidence layer for AI coding agents Open Kioku, a new open-source tool, provides AI coding agents with a local evidence layer by indexing codebases and offering read-only MCP tools for pre-edit analysis. The tool indexes symbols, references, and tests to help agents build evidence-backed plans before making changes, reducing token waste and improving accuracy. A public repo audit showed indexing of 4,600+ files and 46,000+ symbols in 33.1 seconds. Give Claude, Cursor, Codex, or any MCP-compatible coding agent an evidence layer before it edits your codebase, using local indexes and read-only MCP tools by default. Run these three commands on your own repo and see what changes: npm install -g open-kioku ok index . ok mcp install cursor --repo . or: claude, codex, gemini, windsurf, trae, zed, opencode Paste the printed MCP config into your agent, then paste this prompt: Use 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. Your agent now has indexed evidence — symbols, references, impact analysis, test candidates, and edit boundaries — before it touches a single file. Run ok prove on your repo to produce a shareable Markdown or HTML report with indexed counts, task scores, and validation signals. The report intentionally omits source snippets, so it is designed to be reviewed and shared from private repos: ok prove . --task "the feature you're working on" ok prove . --task "the feature you're working on" --html A representative public-repo audit indexed 4,600+ files, 46,000+ symbols, and 8,900+ tests locally in 33.1s. The exact Open Kioku version, repository revisions, caveats, and language limitations are recorded in docs/large-repo-proof.md /shivyadavus/open-kioku/blob/main/docs/large-repo-proof.md . search code → get definition → impact analysis → find tests for change → plan change → verify change An evidence-backed pre-edit plan with: primary files, relevant symbols, likely blast radius, exact validation commands, confidence scores, and the next MCP calls to make. ok plan and MCP plan change return concrete file ranges, validation candidates, and confidence caveats from the local index. On the bundled demo repo, a token task currently surfaces: - primary context in src/auth.rs , src/lib.rs , and tests/auth flow.rs - validation candidates such as issue token , validate token , and login returns valid token via cargo test - an edit boundary that allows the relevant source and test files while keeping generated, vendored, build, and .ok/ artifacts out of scope - explicit caveats when exact-reference, runtime, history, or coverage evidence is unavailable AI coding agents are strongest when they can ask the codebase for facts before editing. Without indexed context, they burn tokens on repeated file crawling, infer references from text matches, and often pick tests only after a change has already gone wrong. Open Kioku gives agents a pre-edit routine: - Search indexed code and files. - Resolve symbols and references. - Build an evidence-backed pre-edit plan with likely impact and validation targets. - Recall prior repo facts without letting memory outrank indexed code evidence. - Compress context into handles that can retrieve the original snippets later. - Serve those capabilities through MCP over local stdio. npm install -g open-kioku ok --version The open-kioku npm package is a JavaScript wrapper that installs the native ok binary through platform-specific optional dependencies. Published platform packages: @open-kioku/darwin-x64 @open-kioku/darwin-arm64 @open-kioku/linux-x64 @open-kioku/linux-arm64 @open-kioku/win32-x64 cargo binstall open-kioku-cli ok --version cargo install open-kioku-cli ok --version Tagged releases publish native binaries and SHA-256 checksums for Linux x86 64/arm64 musl, macOS x86 64/arm64, and Windows x86 64. Download from https://github.com/shivyadavus/open-kioku/releases https://github.com/shivyadavus/open-kioku/releases . git clone https://github.com/shivyadavus/open-kioku.git cd open-kioku cargo install --path crates/open-kioku-cli ok --help Requires a stable Rust toolchain. ok init /absolute/path/to/repo ok index /absolute/path/to/repo ok doctor /absolute/path/to/repo ok status /absolute/path/to/repo --markdown --write ok-status.md ok setup audit /absolute/path/to/repo ok --repo /absolute/path/to/repo search "the feature or bug you care about" --limit 5 ok index writes local data under .ok/ : SQLite metadata and graph rows in .ok/index.sqlite , plus BM25 search data in .ok/search/tantivy . Large indexes report progress phases such as scan , parse , occurrences , store , graph , search , and complete . Keep the index fresh while editing: ok watch /absolute/path/to/repo ok mcp install cursor --repo /absolute/path/to/repo ok mcp install claude --repo /absolute/path/to/repo ok mcp install codex --repo /absolute/path/to/repo ok mcp install gemini --repo /absolute/path/to/repo ok mcp install windsurf --repo /absolute/path/to/repo ok mcp install trae --repo /absolute/path/to/repo ok mcp install opencode --repo /absolute/path/to/repo ok mcp install zed --repo /absolute/path/to/repo Paste the printed MCP config snippet into your agent. The default server is read-only and runs locally over stdio. The install matrix is tested for Claude, Cursor, Codex, Gemini CLI, OpenCode, Zed, Windsurf, and Trae. Agent-specific setup guides: Claude https://www.openkioku.com/claude-code-setup.html · Cursor https://www.openkioku.com/cursor-setup.html · Codex https://www.openkioku.com/codex-setup.html · Gemini CLI https://www.openkioku.com/gemini-cli-setup.html . OpenCode, Zed, Windsurf, and Trae use the same verified ok mcp install