LabWired Core CLI
LabWired Core runs firmware on a virtual copy of a real chip and gives an agent UART and GPIO traces plus an exit code.
- 168 ★ on the repository
- Last commit
Extended access
Why this level
- The installer runs as a script from the network.
- The cloud MCP receives your firmware and board description.
Install
- Works in
Manual install
curl -fsSL https://labwired.com/install.sh | shInstalls the CLI for Linux, macOS and Windows via WSL2; set the version with `LABWIRED_VERSION`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The installer runs as a script from the network.
- The cloud MCP receives your firmware and board description.
This is third-party code. Review the repository files before installing.
What it does
The `labwired` CLI loads a firmware ELF and runs it against a chip model: CPU, buses, peripherals, sensors, displays and protocol devices. Output is UART text, GPIO and bus traces, register state and an exit code suited as a CI gate. Runs are deterministic: the same ELF and board manifest give the same trace on any machine. Supported cores are ARM Cortex-M0 Plus, M3, M4, M7 and M33, RISC-V and some ESP32 paths on Xtensa. For an agent there is an MCP connector at `https://api.labwired.com/mcp` that assembles a board, runs firmware and returns the result. The Fidelity Ledger in the repository lists where the model simplifies hardware.
Who it is for. Firmware developers who want to test code without a board on the desk, in CI and through an AI agent.
Good fit when
- An nRF54L15 firmware must pass a boot test with no physical board.
- CI needs a deterministic gate: exit code 0 when checks pass.
- An agent assembles a virtual board and reads UART output through MCP.
- You need to check I2C or SPI traffic to a sensor or display.
Not a fit when
- You need exact timing or analog effects: the model simplifies in places.
- The chip or peripheral is missing from the model list.
- You cannot use the cloud connector: install the local CLI instead.
Example request
Run examples/nrf54l15-dk/io-smoke.yaml with labwired test and show which four checks passed.Limitations
Model coverage is limited and simplifications are listed in `FIDELITY.md`. The install is a `curl | sh` script from labwired.com; Windows has no script, so unpack the archive by hand or use WSL2. The cloud MCP opens a browser to sign in on first use. For exact timing, analog effects and rare peripheral blocks you need a real board: the simulator does not replace the final bench. The cloud connector needs a LabWired account sign-in, while the local run needs none.
How to disable. Delete the `labwired` binary from the install directory and for the cloud remove the connector with `claude mcp remove labwired`.
FAQ
Is a physical board needed?
No, firmware runs on the chip model and no board is required. Real boards remain for final checks of exact behavior.
Which processors are supported?
ARM Cortex-M0 Plus, M3, M4, M7 and M33, RISC-V and some ESP32 paths on Xtensa LX6 and LX7.
How do I connect it to Codex?
Run `codex mcp add labwired --url https://api.labwired.com/mcp`; the client opens a browser to sign in.
Is there an editor extension?
Yes, the VS Code extension downloads the needed archive on first use, including on Windows, and calls `labwired-dap` for debugging.
How can I look without installing?
Open the browser playground at app.labwired.com: it has ready labs with an SSD1306 display, a BME280 sensor and IO-Link.
Discussion
No questions or reviews yet.
Related
CLI toolsClaude Code skills and a Raspberry Pi testbench: the agent writes ESP32 firmware, flashes the board and tests it on hardware
ESP32 Workbench gives an agent 11 skills and 13 MCP tools for ESP32 firmware: pins, panics, build logs, partitions.
auto-embedded gives firmware projects five stages, a pin and DMA lock and a task log so the agent stops guessing.
24 skills for microcontroller firmware: build, flash, GDB debugging, UART, Modbus, CAN, logic analyzers and static analysis
A Claude Code skill for designing PCBs, CAD and firmware as code that writes fab files only after every gate passes
A terminal AI agent for microcontrollers: writes board code, builds, flashes and diagnoses logs from real hardware.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| LabWired Core (this card) | no | 168 | ||
| embed-ai-tool | no | 1,073 | 24 skills for building, flashing and debugging on hardware; LabWired runs firmware on a virtual chip | |
| ByteAsk Embedded MCP | yes | not required | 26 | serves register references; LabWired runs the ELF itself and returns a trace |
README in short
The README explains that this is the engine behind labwired.com: an ELF loads, runs on a model and the result is an exit code. It covers install, an nRF54L15 example, CI integration, MCP for agents and a table of supported chips with fidelity tiers.