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.
kicad_close ends with forceKilled:[pcbnew.exe] after the graceful pass (winvm 0.9.340, KiCad 10.0.6)
From Codex's clean-install run on winvm (issue #81 thread): kicad_close {} closed three windows and reported success, but data.forceKilled lists pcbnew.exe, so the PCB editor did not exit on the graceful path within the wait and was terminated. Evidence: https://wiki.adom.inc/attachments/adom/kicad-bridge/674e542790b9a158d0b8c6cee9e661832adf1b7f4a6458e3632646b2bce1c819/winvm-fresh-cleanup.json (durationMs 7605). To check: whether pcbnew was answering a save prompt or the OpenGL fallback at the time, whether the graceful wait is long enough on a software-rendering VM, and whether a forced kill can leave the fp-info-cache or the project lock file behind. Not a data-loss report: the fixture was disposable and unsaved edits were expected to be discarded.