Skip to content
hw.dev
hw.dev/signal/kdock-agent-lab-tools-single-workspace-2026
SignalKDock

KDock Gives an AI Agent the Same Bench Tools as the Embedded Engineer

KDock's first test build lets an AI agent flash firmware, read the serial port, and query a scope itself, so it can check its own work on real hardware.

Thesis connection

An agent that can flash a board and read the results itself shortens the gap between writing firmware and knowing whether it works.

#embedded#testing#tools#software
Read Original

KDock is a desktop workbench for embedded developers, and its first downloadable test build puts an AI agent in the same window as the lab equipment. The serial port, network connections, firmware updates over the YMODEM file-transfer protocol, the common programmers and debuggers (OpenOCD, J-Link, STM32CubeProgrammer), files on the device, a RIGOL oscilloscope, and a logic analyzer that decodes 19 protocols are all available to the agent as tools it can call. Today an engineer usually sits between those applications, copying output from one into another.

With direct access, the agent can check its own work. It can flash a build, read the device's serial output, pull a file off the device and verify its checksum, ask the scope for any of 13 measurements, read decoded bus traffic, and decide what to try next based on what came back. KDock can also run conditional sequences across local commands and device connections, so a board bring-up procedure can live as a repeatable script instead of in someone's chat history.

It's an unsigned Windows prerelease, so it belongs on a spare machine with a board you don't mind bricking. Our bet is that within 12 months, people choosing an embedded AI agent will care most about what it can measure on real hardware after flashing, and how much firmware it can write will matter less.