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+12@@ -10,6 +10,18 @@ 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.72 (2026-10-28 19:28 UTC)++NATIVE (Rust) build. 1.0.72: four more checks from the standard's engine 0.4.0 (EDA Bridge Standard 0.7.0), and a placement review.++- **Engine:** adom-eda-checks 0.4.0, vendored unchanged. Every engine reply now carries the engine's own `engine` field instead of a version written by hand.+- **kicad_thermal_vias and kicad_via_fence:** planned by the engine, as all three bridges now do (standard #18).+ - The via comes from the project's Default net class, and the fence's clearance from the board's largest clearance rule.+ - KiCad's DRC still runs before any via is placed, live or in the closed file.+- **kicad_height_check:** computed by the engine from kicad_bodies; `complete` says whether every part had a body (standard #19).+- **kicad_placement_check (new):** a placement review before routing, from the engine with the parts' 3D bodies.+ - It finds parts whose pads and bodies overlap on one side, parts off the board or over its edge, pads near the edge, and parts on a mounting hole.+ ## 1.0.71 (2026-10-28 19:00 UTC) NATIVE (Rust) build. 1.0.71: pictures of library parts, and layer visibility in the open board.