LabWired documentation
Run real firmware on a digital twin of the board — in the browser, from an agent, or in CI. Same models. Deterministic results.
Start here
| Door | You want to… | Start |
|---|---|---|
| Playground | Try without installing | Playground first run · app.labwired.com |
| Agent (MCP) | Let Claude / Codex / Cursor drive the twin | Connect MCP · First agent run |
| CLI / CI | Run locally or in a pipeline | Run firmware · CI |
| Onboard hardware | Add a sensor, actuator, or board | Pick a track · Onboard a part |
What does a green pass mean? → Fidelity
Onboard hardware (quick pick)
| Track | Examples | Guide |
|---|---|---|
| Part (most common) | I²C sensor, SPI chip, servo, motor, buzzer | Onboard a part |
| Board / MCU | New chip or Nucleo / Pico / ESP board | Board playbook |
| On-chip peripheral | New timer / UART model inside a chip | Peripheral modeling |
Parts catalog: Parts · Support levels: Target rubric
Boards (popular)
ESP32-C3 · ESP32-S3 · nRF52840 · RP2040 · STM32F401
More (when you need it)
| Topic | Link |
|---|---|
| Agent tools | Tool reference |
| CLI flags | CLI reference |
| Troubleshooting | Troubleshooting |
| YAML config | Configuration reference |
| Architecture (engine) | Architecture |
| Agents working in this repo | Core agents manual |
Product
Hosted Playground and MCP use the same core models as the open CLI. Plans and tokens: labwired.com.