app
KiCad - the KiCad Bridge
Public Made by Adomby adom
Drive your own KiCad from an AI, in the background: open every editor, read the whole board as data (the EDA Bridge Standard board model), stack-up, part heights, netlists, place, route, pour, DRC and exports.
← Commit history
RELEASE_NOTES.md+13@@ -10,6 +10,19 @@ unnamed. These entries were reconstructed after the fact from the work they contain, which is exactly the situation the mandatory-notes gate now prevents. Treat them as accurate but secondhand. +## 1.0.75 (2026-10-28 21:05 UTC)++NATIVE (Rust) build. 1.0.75: decoupling caps sorted by the IC they belong to, routes planned at the board's net class, and the standard's engine 0.7.0.++- **kicad_place_decoupling:** by default it now leaves out two kinds of cap, listed in leftOut[] (standard #22):+ - signal_net: a net not named like a supply with only one cap to ground, such as a crystal's load cap;+ - nearer_another_ic: a cap nearer another IC's pin on the same net.+ - On the ESC board, U1 no longer takes every +VBAT cap: they split between U1 and U2. Naming caps still places them as asked.+ - A through-hole pad of a part on the other side now blocks the spot too.+- **kicad_plan_route:** the project's Default net class goes to the engine as the board's width and via rules, and planner.widthFrom / viaFrom say which rule set them.+- **kicad_open_board:** when KiCad's API serves another PCB editor's board, it now says so (api_serves_another_board), not "a different board with the same file name".+- **Engine:** adom-eda-checks 0.7.0 (EDA Bridge Standard 0.10.0).+ ## 1.0.74 (2026-10-28 20:40 UTC) NATIVE (Rust) build. 1.0.74: 3D bodies made from package dimensions and routes planned between pads, both from the standard's engine 0.6.0.