AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
tour nets reports OK after board_mismatch and zero selections; needs board-specific IPC socket
AI Flow 0.1.15 / KiCad Bridge 1.0.11 / KiCad 10.0.5 / ConfRoomROG.
Fable's esc-g431.kicad_pcb was already open. capture open opened Astra's esc-g431-astra.kicad_pcb in a second PCB editor and reported success. kicad_routing_state with Astra's exact filePath returned board_mismatch with openBoards=[Fable board]. tour nets then printed OK and eight successful-looking entries, each with zero selected items. The recording is the static Astra board, not a walkthrough.
Expected: refuse on a bridge semantic error or zero selected objects for a loaded net. Discover and verify the board-specific IPC socket, carry it in run.json through every IPC call, and verify the editor HWND belongs to the same board.
On this Windows installation there was only one named pipe, the default api.sock, despite two pcbnew processes. The second process could not provide its own usable default endpoint. Workaround: close ONLY Astra's saved editor, relaunch it with TEMP/TMP set to an Astra-specific directory, and pass the resulting socketPath to every IPC verb. Exact readback then returned Astra's 4042 track segments and 444 vias. A task-local PATH adapter supplies the verified socket because AI Flow does not currently expose it; installed packages, Fable's process and board geometry are untouched.
Candidate fix: add --socket-path / run.ipcSocketPath, propagate through Bridge IPC calls, validate selected item counts and semantic error fields in tour, and provide safe multi-instance IPC discovery. Attached adapter is a minimal reproduction/workaround, not a replacement released bridge.