KiCad Bridge · AI control for KiCad
connecting...

Boxes & actions

Demos

Guided demo
Six beats on a real Adom board from the wiki, the ESC G431 motor controller: its STM32 symbol, that chip's footprint, the chip in 3D, the full schematic, the board in 2D and the board in 3D. Each window is brought to you once, a caption names every beat, and the glass remote at the bottom right is yours: play, pause, next, back, mute, stop.
Tour a wiki part end to end
Pulls a part page from wiki.adom.inc, installs its symbol, footprint and 3D model into KiCad, then generates a single-component project you can open.

KiCad surfaces

A real wiki part, end to end. Each button fetches the part's files from its wiki page, installs them into your real KiCad, opens JUST that surface in the background, and renders it from kicad_state. This is the whole circle: a wiki component to the app the EE designs in.

Verb times on this box

Every dispatch is logged with its outcome; these numbers converge just by the bridge being used. p50 15s beside p90 400s is two code paths wearing one name.
not loaded - press refresh

Copy-paste prompts for your AI

KiCad Bridge Settings

Taskbar activity

While a verb is driving KiCad, the bridge marks the KiCad taskbar button so you can tell the window is busy and who is busy in it. The progress bar is painted through the Windows taskbar API (ITaskbarList3) and sized from this box's own measured verb timings: it fills over the time that verb usually takes here, creeps past the end when a run is overdue, and shows an indeterminate marquee when nothing has been measured yet. The flash is Windows' own attention highlight. The bridge never triggers it, it only decides whether to cancel it while a bar is showing.

The difference is what each one asks of you. A flash stays lit until you click the button, so it reads as something you have to deal with. A bar removes itself the moment Adom stops driving, so when the bar and the overlay badge are both gone, the window is yours again. Read-only verbs such as status checks never mark activity in any mode.

Taskbar: Activity indicator

What the KiCad taskbar button does while Adom is driving it. Each picture is a 1:1 capture of this machine's taskbar at its native resolution.
Default: Progress bar

Keep KiCad in the background

When Adom opens a KiCad window, KiCad tries to bring it to the front of whatever you are doing. With this on, the bridge sends the window it is opening right now behind your window. It only ever touches the window being opened at that moment: a KiCad window that is already open is yours to raise by clicking its taskbar button, Alt-Tab or anything else. With this off, the bridge never moves or pushes any KiCad window, so you see exactly what KiCad does by itself. Off by default while it is still being tuned: with it on, KiCad can behave oddly (wiki #114). Flip it to compare the two; the change applies at once and the bridge's focus log keeps recording what it would have done.

Windows: Send new KiCad windows behind mine

Send a KiCad window Adom is opening behind my window
Default: Off

Overlay badge

The Adom mark is stamped in the corner of a KiCad window's taskbar button while a verb is running against that window, and comes off by itself five minutes after the last verb, so a badge always means "Adom is driving this right now". It is a per-window overlay through the same taskbar API, so it never changes the button's own icon or how Windows groups it, and it is never stamped by read-only verbs like status checks. A bridge restart clears every badge, because a freshly started bridge is driving nothing.

The KiCad taskbar button with the small teal Adom mark in its top right corner
On: the Adom mark sits on the KiCad PCB Editor button while a verb drives it.
The same KiCad taskbar button with no mark on it, only its own icon
Off: the same button, same moment, nothing added.

Taskbar: Adom overlay badge

Show the badge while Adom is driving
Default: On

Setup