Oko: code search for coding agents
Oko uses Jev to rank code for agents. Its author reports 0.48 vs BM25's 0.21 for needed code within 8k tokens, and faster Claude Code sessions across nine tasks.
Oko</h1>
<p align="center">
<strong>Help your coding agent find code faster and use fewer tokens.</strong>
</p>
<p align="center">
<a href="https://github.com/bartlomein/oko/actions/workflows/ci.yml"><img src="https://github.com/bartlomein/oko/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
<a href="https://github.com/bartlomein/oko/releases/latest"><img src="https://img.shields.io/github/v/release/bartlomein/oko" alt="Latest release"></a>
<a href="LICENSE"><img src="https://img.shields.io/github/license/bartlomein/oko" alt="MIT license"></a>
</p>
Oko gives Claude Code, Codex, Cursor, OpenCode and Pi a better code search. When
you ask your agent about your code, Oko has already found the relevant source,
so the agent spends fewer rounds searching and reading files it does not need.
<p align="center">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="docs/images/agent-sessions-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="docs/images/agent-sessions-light.svg">
<img alt="Bar chart: with Oko, Claude Code spends 47% less time, 44% fewer tokens and 89% fewer tool calls; Codex 26%, 43% and 80%; OpenCode 47%, 43% and 87%; Pi 51%, 33% and 85%; Cursor 6%, 40% and 65%." src="docs/images/agent-sessions-light.svg" width="760">
</picture>
<br>
<sub>Nine coding tasks on Astro, HTTPX and ripgrep, three runs each, with and without Oko. <a href="#results">Results</a> · <a href="docs/benchmark-results.md#agent-sessions">Method</a></sub>
</p>
- **Faster:** about half the time in Claude Code, OpenCode and Pi; a quarter less in Codex.
- **Cheaper:** 33–44% fewer tokens with every tool we measured.
- **Fewer detours:** 65–89% fewer tool calls.
- **Better ranking:** puts the right file first more often than any published metho