Summary Kuri provides a Zig-native, token-efficient solution for browser automation and web crawling, specifically designed for AI agents. It replaces heavy Node.js dependencies with single, compact binaries, drastically reducing LLM processing costs and simplifying deployment for automated web interactions.

How It Works Built entirely in Zig, Kuri compiles into highly performant, small binaries, eliminating runtime dependencies. It offers four modes: a CDP server for Chrome automation, a standalone fetcher (kuri-fetch) for server-side rendering, an interactive terminal browser (kuri-browse), and an agentic CLI (kuri-agent). The project prioritizes token efficiency for AI agents by generating compact accessibility snapshots instead of verbose HTML or screenshots. It also integrates automatic stealth techniques to bypass common bot detection mechanisms.

Quick Start & Requirements Installation is straightforward via a curl script (macOS/Linux) or npm/bun package managers. Building from source requires Zig 0.16.0+, and CDP automation needs Chrome/Chromium. Kuri binaries are exceptionally small, with the core kuri binary around 866 KiB.

Highlighted Details

• Token Efficiency: Benchmarks show a full kuri-agent loop on Google Flights consuming ~3,392 tokens; kuri snap --interactive yields ~795 tokens.
• Performance: Minimal memory footprint, with RSS remaining stable.
• Bot Evasion: Automatic patches for navigator.webdriver, WebGL/Canvas spoofing, and UA rotation bypass detection by Akamai, Cloudflare, etc.
• Standalone Fetcher: kuri-fetch (~2MB) executes JavaScript via QuickJS without a browser.
• Security Audits: kuri-agent supports login flows, cookie/header audits, and bot block detection.

Maintenance & Community Active development is indicated by recent benchmarks (April 2026) and Zig 0.16.0 requirement. No specific community channels or prominent contributors are detailed in the provided README excerpt.

Licensing & Compatibility Released under the permissive Apache-2.0 license, Kuri is suitable for commercial use and integration into closed-source projects.

Limitations & Caveats Some anti-bot measures (e.g., PerimeterX on Booking.com) may require a proxy. Building from source might depend on specific Zig versions or environments.