LabWired Agent included — our model for Zephyr and pro firmware. Validated private twins. Debug without a board on the desk.
Write, run, and debug without leaving your editor — and without a bench to test against.
Describe the task. The agent writes Zephyr code, compiles it with your toolchain, and iterates until it builds. Bring your own Claude or Codex, or use LabWired’s agent.
Zephyr developmentRun it on a model of your chip and watch real behavior — serial, pins, registers — without flashing a board. Fast enough to stay in flow.
No board on your deskSet breakpoints, inspect registers and memory, and step the code. Because the run is deterministic, you can step backwards — straight to the cycle a fault started.
Reverse-step, which no bench can doZephyr development against your own toolchain, frameworks, and libraries. It builds the way your project already builds.
Private projects on a priority build queue. Your code stays yours, and your builds don’t wait in line.
Engineering support and onboarding for your own chips and boards. You talk to people who know firmware.
On-prem LabWired model and private twins in your vault. Builder has no network access. Runner is a single binary. Nothing calls out.
No. Pro runs entirely against the simulator, in the browser and in VS Code. The HIL device is an optional add-on (in development) for teams that also want to check against real silicon.
Yes. Claude or Codex over MCP, or LabWired Agent. Same tools either way.
On Pro, builds run on our cloud and your projects are private. If firmware can’t leave your network at all, that’s what Enterprise self-hosting is for.
Zephyr development plus Arduino and bare-metal targets across a wide board matrix, with more boards landing continuously. See the validation matrix.
The full workbench, in your editor. Start free on Playground, or get Pro today.