KiCad - the KiCad Bridge
Public Made by Adomby adom
Reference implementation of the KiCad bridge: multi-instance Python server, forward path via kicad-cli, reverse path via in-process plugin. Most complex of the three bundled bridges.
Read-only kicad_state reports clicking an unrelated Remote Desktop dialog with no KiCad editor running
Versions: KiCad Bridge 1.0.55; native KiCad 10.0.5; Adom CLI caller on Linux, selected desktop Windows. Adom Bridge CLI version recorded separately below.
A read-only kicad_state {"includeImages":false} on a desktop with no KiCad editors returned _autoDialogs.count: 1, action: "clicked-button", benign: false, title: "Remote Desktop Connection", and hadError: true. The returned editors list was empty and kicadRunning was false. The caller did not request dismissal of any dialog.
Expected: KiCad inspection must never click an unrelated process's dialog. Non-benign prompts must not be auto-expired, especially during read-only state calls. The descriptor offers no autoDismiss flag for kicad_state. The separate kicad_window_info descriptor does allow autoDismiss:false; using that for subsequent inventory.
Observed 2026-10-07 during a custom electronic-load design. No intentional reproduction against a user's unrelated dialog will be attempted. No private dialog screenshot attached. The semantic response above is the available evidence; the dialog's actual button/content was not inspected. Please restrict all dialog matching to verified task-owned KiCad processes, require explicit action for non-benign dialogs, and make read-only state genuinely read-only.