None of these tools edit source. That split is the point: the agent gathers evidence, states what it intends to change, applies the edit with its normal tools, and then the same evidence model checks whether the result stayed inside the boundary it declared. Memory and compressed-context tools do write local `.ok/` artifacts so facts and handles survive the session. Exact evidence stays authoritative over heuristic evidence, and ambiguity is returned as ambiguity rather than promoted to a fact.
A local repository evidence layer for coding agents. It indexes code, symbols, references, tests, git history, docs and architecture into one model, compiles the smallest useful context for a task, and verifies the resulting change. No hosted index and no source upload.
- Navigation first: `repo_status`, `search_code`, `search_symbols`, `get_definition`, `get_references` and `get_symbol_context` resolve the code facts before an edit
- `impact_analysis` returns direct and indirect dependents with a risk score; `find_tests_for_change` and `recommend_validation_plan` pick the validation targets
- `ownership_lookup` ranks owners from CODEOWNERS, local git history and repo memory, with source breakdown, confidence and staleness; `reviewer_suggestions` ranks reviewers from stored review evidence
- `preflight_change` returns a short evidence-backed verdict — confirmed edit files, likely affected files, validation commands, risks and evidence quality; `plan_change` and `build_context_pack` return the full grounding
- `create_change_contract` stores a versioned pre-edit contract; `verify_change_contract` checks the changed files, a diff or a git range against it, and `explain_verification` summarises the verdict
- `build_compressed_context` stores snippets locally and hands back handles that `retrieve_context` expands
- `remember_fact` and `search_memory` keep append-only repo facts with provenance
- Search responses paginate with returned, limit, offset, has_more, truncated, warnings and caveats
Install `open-kioku` globally from npm and run `ok setup agent claude --repo .` or `ok setup agent cursor --repo .` — without `--apply` first, to see the changes. The MCP server runs over stdio as `ok mcp serve --repo <path> --read-only`. Command execution and validation attestations are opt-in behind `--approval-required`, `--allow-command` and `--deny-network`. Optional semantic retrieval runs locally.
One command — npm install -g open-kioku