GoKawiilKuri 🌰
Browser automation & web crawling for AI agents. Written in Zig. Zero Node.js.
CDP automation · A11y snapshots · HAR recording · Standalone fetcher · Interactive terminal browser · Agentic CLI · Security testing
Quick Start · Benchmarks · kuri-agent · Security Testing · API · Changelog
Why teams switch to Kuri: 464 KB binary, ~3 ms cold start. On Google Flights, a full agent loop (go→snap→click→snap→eval) costs 4,110 tokens vs 4,880 for agent-browser — 16% less per cycle, compounding across multi-step tasks.
Why Kuri Wins for Agents
Most browser tooling was built for QA engineers. Kuri is built for agent loops: read the page, keep token cost low, act on stable refs, and move on.
The product story is not "most commands." It is "useful state from real pages at the lowest model cost."
A tiny output only counts if the page actually rendered. Empty-shell output is a failure mode, not a win.
The best proof is same-page, same-session, same-tokenizer comparisons.
... continue reading