Auto-Arch Tournament vs Kuri

Auto-Arch Tournament is an autonomous research system where an AI agent iteratively proposes, implements, and validates microarchitectural improvements to a RISC-V CPU. Starting from a standard 5-stage pipeline, the loop runs hypotheses in parallel, each going through formal verification (53 symbolic checks), cycle-accurate simulation, multi-seed FPGA place-and-route, and CoreMark CRC validation. Only hypotheses that beat the current champion get merged; everything else gets discarded. Starting from 301 iterations/second, the system hit 577 iter/s (+92%) across 73 attempts in 9.8 hours — producing a design 26% faster and 40% smaller in LUTs than the baseline. The insight the author drives home is that the real innovation isn't the AI agent — it's the verifier. The orchestrator is hardcoded to prevent agents from manipulating their own evaluation gates, a simple but critical design constraint that turns a creative process into a trustworthy one. Without a rigorous verification harness, agent-driven optimization becomes a confidence trick. This is early but fascinating proof that AI-driven hardware design loops can produce commercially meaningful gains. The repo uses Claude Code or Codex as the coding agent, SystemVerilog for the RTL, and standard open-source EDA tooling (Yosys, nextpnr, Verilator). It's a compelling template for anyone building agentic optimization loops where correctness matters.

Kuri is a browser automation tool written in Zig, designed specifically for AI agent workloads. The entire binary weighs 464KB with a cold start of approximately 3ms — a stark contrast to Playwright or Puppeteer, which drag in hundreds of megabytes of Node.js runtime and dependencies. Kuri ships 40+ HTTP API endpoints and bundles four capabilities in one: a Chrome DevTools Protocol (CDP) server, a standalone page fetcher, a terminal browser, and an agentic CLI. The key engineering insight is that AI agents spend a lot of their latency budget waiting for browser tooling to spin up. By rebuilding the whole stack in Zig, Kuri eliminates that cost. It also includes built-in anti-detection stealth layers — useful when agents need to scrape or interact with sites that gate on bot signals. The team claims a 16% reduction in tokens-per-workflow cycle compared to Playwright-based setups, which has real cost implications at scale. Early community reception on Hacker News was positive, with developers noting the Zig choice as a credible engineering decision rather than a language hipster move. With 119 GitHub stars within hours of posting, the project is clearly scratching a real itch for the growing population of agent developers who treat browser automation as table stakes but hate paying Playwright's overhead tax.