Auto-Arch Tournament vs free-claude-code

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.

free-claude-code is an indie-built proxy server that intercepts Claude Code's API calls and silently redirects them to free or local providers — NVIDIA NIM, OpenRouter free tier, DeepSeek, LM Studio, or llama.cpp running on your own hardware. It maps Claude's three tiers (Opus, Sonnet, Haiku) to different backend models, parses thinking tokens from reasoning-capable models, and handles trivial in-session calls locally to minimize latency. The project shot from zero to 2,388 GitHub stars in a single day — the fastest-rising repository on the platform on April 23, 2026. That velocity reflects a brewing frustration in the developer community: Claude Code is powerful, but its token consumption during agentic sessions can generate hundreds of dollars in monthly API bills for heavy users. The approach is pragmatic rather than perfect. Coding quality degrades for complex tasks when routing to smaller free models, and the setup requires running a local proxy. But for developers doing exploratory work, quick scripting, or running Claude Code as a teaching tool, it offers a genuinely useful escape valve from the per-token pricing model.