What they did
The poster, who does PCB design for a living and had already built and fabricated this board, gave Claude Code (Fable 5.2 at medium effort) a KiCad 10 project through a KiCad MCP server. The schematic was complete; the layout held only the fixed board outline and mounting holes. The board is a BLDC motor driver with an integrated encoder, an ARGB LED output and a UART header on a four-layer stackup. The prompt set placement rules (encoder centred on the bottom, parts on one side where possible, connectors at the edge), current limits (12 V in, 3 A motor, 1 A LED) and a 20 degree temperature rise for trace sizing, and asked the agent to clarify before starting. As a control, the same prompt, MCP and design rules went to the Codex CLI on GPT Astra 6 at high effort.
How it went
Claude Code asked two questions, including whether the KiCad editor was closed since it would edit the board file on disk. It skipped the autorouter and routed traces with a Python script it wrote, used copper pours on the high current paths, added stitching vias and kept most parts on one side. It took two iterations, the second only moving two traces that sat too close, and used about 96% of a Pro plan session limit. The poster said the result looked like a person had drawn it. The Codex run went past 30 iterations and 1 hour 40 minutes, leaned on the autorouter, put the debug connector in the middle of the board, placed vias in pads and failed the design rule check with unconnected nets.
Worth knowing
This was one run per agent at different effort levels, on a board the poster had already designed, so it is an exercise rather than a production job. A commenter pointed out that Codex asked the sharper electrical questions (phase versus supply current, stall limits). Close the KiCad PCB editor while the agent works, or a save there will overwrite its changes.