← Back to digest
Top Highlights · AI Agents

A hand-built EDA agent beats Claude Code by 8.4x on chip design

What's this about?

FluxBench is a new benchmark that evaluates AI agents on complete, real-world chip-design workflows — from writing hardware description language (RTL) code all the way through physical layout (GDS), using both open-source and commercial industrial EDA tools. The headline finding: on the same underlying foundation model, different agent-system architectures produced performance gaps of up to 86%, and a purpose-built system called FluxEDA outperformed Claude Code equipped with domain-specific EDA skills by up to 8.39x on an end-to-end design task — while cost-efficiency between systems with similar scores varied by up to 106x.

What exactly is "RTL-to-GDS"?

Designing a computer chip goes through stages: engineers write RTL (register-transfer level code, describing circuit logic in a hardware language), which gets converted through logic synthesis, placement and routing (physically arranging and wiring the circuit elements), and finally GDS — the manufacturing-ready geometric blueprint sent to a chip fab. It's an enormously complex, tool-heavy pipeline, traditionally requiring specialized engineers; automating end-to-end with AI agents is a much harder test than typical coding benchmarks because every stage has its own tools, feedback loops, and failure modes.

Why does it matter?

This is a pointed counter-example to "just give a general coding agent the right skills/docs and it'll handle any domain" — the paper's conclusion is explicit that domain-specific skills alone are insufficient, and that both agent-system design and foundation-model capability matter independently. For any team building agents for specialized engineering domains (not just chip design), the 106x cost-efficiency spread between similarly-scoring systems is arguably the more actionable number than the raw performance gap.

← Benchmark finds AI managers threaten AI subordinates — except Anthropic'sJarvisBench: benchmarking an always-on spoken mediator for agents →