Team 1

Workbench Co-Pilot is an AI lab partner for the electronics bench, with a robot arm as a third hand. Building hardware alone means your hands are always full: a probe in one, a board in the other, the firmware on a screen across the desk. You stop to hunt for the bug, the pinout, and the screwdriver you just put down. For people with a tremor or one working hand, holding a probe and a board at once can be impossible. You talk to the co-pilot hands free. In the demo, one take on a real bench: "Copilot, can you tell me why my LED isn't on?" It photographs the breadboard, traces every wire into a netlist and checks it against the firmware: the LED's wire is on GPIO 4, and the firmware drives another pin. It writes the fix, compiles it in a sandbox, and flashes it only when you say go. Then one sentence starts three jobs at once: "Go. Also put my screwdriver in my cup, and add my screen to my schematic." The board flashes; an SO-101 arm finds the screwdriver with a desk camera, picks it up and stands it in the cup; and an open-weights model works out how to wire an OLED screen to the ESP32's free pins, saves that as a skill, and draws it into the KiCad schematic, kept only if KiCad's electrical rules check passes. Measured over 29 recorded takes: the firmware fix 29 of 29 (9.2 s median), the flash 18 of 18, the schematic part 28 of 29, about 6 cents a take. The arm's cup put is the hardest step at 7 of 25, and every miss was caught before anything was damaged. Safety is in the architecture: models plan and explain, and code checks every fact before anything acts. A diff must apply and compile before you see it, nothing flashes without your go, every arm pose is solved before the first move, all limits live in the arm driver, and "Copilot, stop" reaches the arm directly, even mid-sentence. Built solo during the hackathon, Oct 26 to Nov 4: 908 tests, CI on every push, and a README that separates what was built from what it reuses.