The broken loop
AI coding agents are now good enough to write embedded firmware. What they can't do is run it. On the web, an agent writes code, executes it, reads the output, and tries again — a tight loop measured in seconds. On embedded, that loop is broken: to know whether the firmware works you need a specific board, a flashing probe, and a human to wire it up and watch a UART. The agent is writing blind.
You can't close that loop with real hardware. Hardware is serial (one board, one job at a time), non-deterministic (timing-dependent bugs that don't reproduce), and destructible (the agent's third attempt shouldn't fry a power stage). To close the loop you need a substrate that is fast, deterministic, parallel, and disposable — which is a description of a simulator, not a bench.
The loop, closed
flowchart LR
A["Agent writes /<br/>edits firmware"] -- "build · PlatformIO" --> B["firmware.elf"]
B -- "run · LabWired sim<br/>(deterministic)" --> C["structured result<br/>result.json · UART · VCD · PC history"]
C -- "agent reads & diagnoses" --> A
Every step is headless and scriptable, so an agent can run it unattended — and run fifty of them in parallel across boards and configs.
Why LabWired is the substrate
- Deterministic by construction. The same firmware binary yields the same result on every run, so an agent's observations are reproducible — a precondition for reasoning about cause and effect.
-
Structured observability. Each run emits machine-readable output —
result.json, a UART log, a VCD trace, PC history — so the agent works from structured data rather than a screenshot. -
An MCP server, built in. The open-source core ships a Model Context
Protocol server exposing
simulate,validate_system,list_boards, and more — so an agent drives the hardware twin directly. - Real cores, validated peripherals. ARM Cortex-M, RISC-V, and Xtensa instruction-level models with peripheral blocks diffed against physical silicon on a hardware-oracle bench.
What works today
The build half of the loop is already wired to the world's most popular embedded build
system. pio test compiles a firmware and hands the ELF straight to LabWired,
which runs it and reports per-test PASS/FAIL, without a board or anything installed
locally. That is a complete, reproducible build-run-result cycle today.
Read: PlatformIO without hardware →
Where it's heading
The frontier is breadth of firmware that boots unmodified. The deterministic kernel, the MCP control surface, and the PlatformIO build path are in place; the ongoing work is bringing full framework stacks — Arduino and ESP-IDF, RTOS schedulers, wireless — through clean boot so an agent can take any PlatformIO project around the loop, not just bare-metal ones. Follow along on GitHub.
If you're building an agent that needs a hardware sandbox, write to contact@labwired.com or book 30 minutes.
