/slaa.sh
DrawingThe closed loop
Parts02
Board families4
Rev2026.10
68.6
PART 01Your boardSTM32 · ESP32 · nRF · RP2
Real silicon, real faults
PART 02slaa.shDaemon · CLI · MCP server
Allow-list · deadlines · journal
PART 01Your boardSTM32 · ESP32 · nRF · RP2
PART 02slaa.shDaemon · CLI · MCP
slaa.sh — pronounced “slash”

Agents write firmware blind. slaa.sh gives them the board.

A small daemon, CLI and MCP server that lets Claude Code, Cursor and Codex build firmware, flash it to a real microcontroller, read serial, RTT and defmt output and fix their own code. No human copy-pasting logs in the loop. Deployed on your bench or in our cloud, under contract.

Request a pilot ↗
The problem — and the fix

Close
the loop.

Today agents write firmware blind. They cannot see the board, so they invent registers, brick boards and ship code that passes on the bench and freezes weeks later. slaa.sh lets the agent flash, watch and iterate on real hardware.

How it works

On your bench.
Four steps.

01 — SET UP

We set up the daemon on the host next to your board. It detects the probe and board.

02 — CONNECT

Add slaa.sh as an MCP server in Claude Code, Cursor or Codex. Takes one config line.

03 — WORK

The agent builds, flashes, reads the board's output, and fixes its own code. You review the journal and the diff.

04 — SCALE

Reserve cloud benches for parallel runs, or deploy the same daemon on a team rack.

Why slaa.sh

Sees it.
Can't wreck it.

The agent can see the board.Serial, RTT and defmt output comes back as structured text the agent can reason about, not a terminal a human has to watch.
The agent cannot wreck the board.Writes go through an allow-list, dangerous operations are dry-run by default, and the daemon, not the model, enforces limits. Hardware-side safety never depends on the AI.
Every action is on record.A journal of every flash, reset and read, so you can audit what the agent did.
Works with the tools you already have.No new IDE. It is a CLI and an MCP server; the agent you use today calls it.
Local first.Nothing leaves your machine unless you choose the cloud bench. Firmware and schematics stay private.
Works with
Claude CodeCursorCodexAny MCPZephyrESP-IDFSTM32CubePlatformIO
First-class boards: STM32, ESP32, nRF52/nRF54, RP2040/RP2350. Plus anything probe-rs, OpenOCD or esptool can flash.
From the bench · placeholder log

Crash. Read.
Fix. Reflash.

One session on a Nucleo board. The agent flashed, read a HardFault from the serial log, fixed the driver and flashed again.

12:04:01sessionstart · agent=claude-code · board=nucleo_f446re
12:04:02buildwest build -b nucleo_f446re · ok · 14.2s
12:04:17flashprobe-rs · 48.3 KiB · verified
12:04:19resetok
12:04:19readserial ttyACM0 · deadline 5s · cap 4 KiB
12:04:21serial*** HardFault · PC=0x08001a3c
12:04:21serialsensor_read(): i2c dev not ready
12:04:30editsrc/sensor.c +6 −2 · check device_is_ready()
12:04:31buildok · 13.8s
12:04:45flash48.4 KiB · verified
12:04:47readserial · temp=23.41C ×10 · ok
12:04:48sessionend · 2 flashes · 0 blocked writes
Pricing

Built for
your plant.

01 · PilotPilotFixed scope

Six weeks on one of your boards and one toolchain. We wire the bench, you keep the journal and the verdict.

One email. We reply within two business days.
02 · Cloud benchCloud benchPer board-hour

Hosted boards your agents lease under contract: STM32 Nucleo, ESP32-S3/C6, nRF52840 and nRF54L15 DK, Pico 2. Capacity reserved per team.

hello@slaa.sh ↗
03 · EnterpriseOn-premAnnual

The same daemon on your own bench rack, inside your network. Leases, queues, audit trail, instruments, SSO.

hello@slaa.sh ↗
FAQ

Plain answers.

Anything probe-rs, OpenOCD or esptool can flash. First-class: STM32, ESP32, nRF52/nRF54, RP2040/RP2350.

Claude Code, Cursor, Codex, and any MCP-capable agent.

No, unless you use the cloud bench.

The daemon blocks fuse writes and protection changes by default and dry-runs anything destructive. Nothing is impossible, so the journal records every action.

Pilots are fixed-scope. After that, per bench-hour in our cloud or an annual on-prem licence.

Capacity is allocated per contract. Ask for a pilot first.

About

Built on
the bench.

“I build with AI agents every day. I got tired of watching them write firmware they could not test, so I built the tool that lets them flash a real board and read what it says back.”

Aljan Shikhiyev, Founder
hello@slaa.sh ↗LinkedIn ↗