Getting Started
Install Kairn and help your coding agent find the right code faster.
Kairn helps coding agents find the right code faster.
It runs locally and points coding agents to the files that matter, reducing search, repeated reads, and unnecessary token use. You do not need a Kairn account or API key.
v0.2 public beta
The kairn enable workflow is published on npm as usekairn@0.2.0-beta.2 and is available through the beta dist-tag.
The latest dist-tag remains on the previous stable package; install @beta explicitly for the v0.2 workflow.
Install and enable
Install the beta once, then enable Kairn in the repository you want it to assist:
npm install -g usekairn@beta
cd /path/to/repo
kairn enableVerify kairn --version reports 0.2.0-beta.2 or a newer announced v0.2 beta before expecting kairn enable. The command detects supported local agents, shows the Kairn-owned changes it will make, configures selected integrations, builds the initial inventory, and runs setup checks. Re-running it is safe and reuses a healthy full index instead of replacing it with a shallow inventory.
Best-tested path
Codex CLI is the most-tested beta integration. Local MCP is the portable path for supported editors and agent clients. A supported setup path is not the same as equivalent benchmark validation; the evidence page keeps those distinctions visible.
Why it helps
Kairn uses exact paths, symbols, failures, repository structure, git state, and session history to reduce broad exploration. The intended result is earlier arrival at required source, fewer irrelevant and repeated reads, and lower observed token use without sacrificing verification quality.
Read How Kairn Works for the current local architecture and the planned calibrated ranker.
What to expect
Kairn may emit source, a compact path hint, a request for missing evidence, or nothing. Silence is correct when extra repository context would add noise.
The published v0.2 beta package is Apache-2.0 licensed. The GitHub source repository remains private today; its public source release and the stable v0.3 distribution are planned.