From an idea to a working device.
Your agent designs the circuit, picks parts that are in stock, lays out the board and writes the firmware. PCBKit checks every pin against its datasheet, runs the firmware on a simulated copy of the board and sends the files to the factory.
- Design
- Parts
- Layout
- Firmware
- Simulation
- Verification
- Manufacturing
- Enclosure
Works withClaude CodeCodexClaudeChatGPTCursorGemini CLI
Have a KiCad board? Drop it anywhere on this page to open it in PCBKit.
Why
Most board mistakes are found after the board arrives.
An agent can write an app and test it. A board still goes through a schematic editor, parts sites, an autorouter, a review, a firmware IDE and a factory’s upload page, and none of them checks the others. So the footprint one size off or the two swapped pins show up on the bench, after you have paid and waited.
~70%
of 732 real fixes in open hardware histories were the part’s own data: footprints, unconnected pads, swapped pins
16–21 %
of 462 real respin faults we collected are found by four checkers together, KiCad’s and ours included
0
board checkers on the market we found that publish how often they are wrong or what they miss
How it works
One KiCad project, from the circuit to the order.
The board, the firmware, the simulation and the fab files all come from one plain KiCad project, the files KiCad itself opens. When your agent changes one, PCBKit reads the change and checks the whole device again, usually in seconds.
Design from a sentence
Your agent turns a wish into a KiCad project: proven circuits, values worked out, every change read and checked as it is written.
Find the right parts
Real parts in stock, picked for what they must meet. Any chip read from its datasheet and checked against its maker’s drawing.
Place and route
Parts placed and copper routed in minutes, by a router ahead of 12 routers and products on their own benchmarks.
Write the firmware
Agents write the program, from a blinking LED to Doom, compiled in the platform for the board’s own chips.
Simulate the whole device
The real firmware runs on the simulated board: chips, screen, buttons, sensors and supplies, at −40 °C, 85 °C and both supply ends.
Verify against every datasheet
Every pin, rating and footprint against its datasheet; power, heat and signals solved on the copper you routed; the factory’s rules.
Order in one click
The fab files frozen, read back and handed to the factory. The board that arrives is the board you simulated.
Print the enclosure
Your agent writes the case around the board. PCBKit checks that it fits and writes the parts for a 3D printer.
Hardware and firmware, simulated together
It runs 
Doom.
The firmware you flash runs on models of the board’s own chips, screen, buttons and supplies before the board is made. We made eleven Doom handhelds on seven processors this way; each is routed, checked and can be ordered. Pick one and play.
- RP2350Arm Cortex-M33
- ESP32-S3Xtensa LX7
- i.MX RT1062Arm Cortex-M7
- CH32V003RISC-V, 2 KB of RAM
- RP2040Arm Cortex-M0+
- ESP32-C3RISC-V
- STM32F411Arm Cortex-M4F
Enclosure
And the case around it.
Your agent writes the case as a program beside the board. PCBKit checks it against the board: every button reaches, every plug goes in, every screw has its insert. Then it writes the parts for a 3D printer and the list of screws to buy.
Step by step
What each step looks like today and in PCBKit.
| Step | Today | In PCBKit |
|---|---|---|
| Schematic | Drawn by hand in an EDA editor | Written by your agent as a KiCad schematic, checked at every change |
| Parts | Distributor sites, a spreadsheet, footprints downloaded from wherever | Picked in stock, each checked against its maker’s drawing |
| Layout | Days of routing by hand, or hours in a cloud autorouter | Placed and routed in minutes, beside you or behind your agent |
| Review | A colleague’s afternoon, if you have one | Every pin against its datasheet, each finding with its evidence |
| Firmware | Written after the board arrives | Written and run before the board exists |
| Testing | A bench, a test rig, a respin | The device simulated at every temperature and supply corner |
| Manufacturing | Export, zip, upload, check the preview by eye | One click; the files frozen by their digest and read back |
| Enclosure | Another CAD tool, measured by hand | Written around the board by your agent, checked against it, ready to print |
Numbers
Measured on other people’s benchmarks.
Other routers’ own benchmark sets, boards people routed by hand and faults people actually shipped. Each number is dated and can be re-run; click a tile for how it was measured.
12
routers and products PCBKit’s router beats on completion, each on the benchmark it publishes for itself
0.88×
the track length of the people who designed 1,049 PCBench boards, with 0.90× their vias
17.9 %vs 9.3 %
of 140 real respin faults found, against KiCad’s own checks; the fixed boards flagged 4.3 % vs 55.0 %
12/20
held-out wishes an agent turned into a verified board on the first try
39/39
boards whose real firmware meets its expectations at −40 °C, 85 °C and both supply ends
905/1,230
parts certified against their makers’ drawings; none of the planted defects passed
Renderer
Real open boards, drawn by our own renderer.
Routing replayed, layers pulled apart, current and heat coloured over the copper. It is the same view that opens next to your agent.
Rendered by PCBKit’s own renderer; the radio board routed by PCBKit from bare pads. Open boards by their authors: MIST.1010 by Eugene Lozovoy (MIT), HBR MK2 RX/TX by Aleksander Alekseev (MIT), Cynthion by Great Scott Gadgets (CERN-OHL-P-2.0), moco RD501 by ZiTe (CERN-OHL-P-2.0), ESP32-WROOM-32 USB Development Board by Habib Ur Rehman (CERN-OHL-S-2.0), pslab hardware by FOSSASIA (Apache-2.0).
Agent-first
It runs inside the agent you already use.
Install the plugin in Claude Code or Codex, or add the MCP server to Claude or ChatGPT. The agent calls PCBKit; you watch the board change in the browser.
Few tools, one build
A handful of tools instead of a hundred buttons. One build picks parts, places, routes, checks and simulates, then says whether the board is done.
You see the board
The board opens next to your agent and updates on every call, in 2D and 3D, with the reason for each change. Click a part and the agent knows which one you mean.
Laptop, phone or CI
Claude Code and Codex run it on your laptop, on your files. Claude and ChatGPT on a phone run it on our servers. The same check runs in CI.
Claude Code
claude plugin marketplace add pcbkit-io/agent-plugin claude plugin install pcbkit@pcbkitCodex
codex plugin marketplace add pcbkit-io/agent-plugin # then install PCBKit from /pluginsClaude and ChatGPT
https://pcbkit.io/mcp
Then ask: Make a handheld game with a colour screen and four buttons.
Get started
Next
Boards that work the first time.
Next come production firmware for any chip and boards that arrive assembled and flashed. The goal: a device an agent designs and a factory makes that works when it arrives, with a report anyone can re-run.
Blog
Recent posts
AI PCB design benchmark: 12 of 20 sealed wishes done first tryA coding agent got 20 one-sentence wishes nobody on the team has read. 12 became finished, verified boards on the first try, at a median of 47 tool calls.
Autorouter benchmark: ahead of 12 routers on their own testsPCBKit's router against 12 routers and AI layout tools, each on its own published benchmark and judge: ahead on all 14 rows, behind on vias and tier A.
PCB CI gate: a signed, reproducible report on every pull requestpcbkit-io/verify checks KiCad boards on every pull request. On 3 public boards GitHub and GitLab gave the same report digest; 44 boards check in 40 s.
Start with one sentence.
Free, in the browser or in your agent.
Made by Sergey Alekseev in Sydney. About the project