Vehicle & Aircraft Control
Flight controllers, FPV, UGVs, robotic arms — the firmware layer.
Example: ESP32-S3 + ELRS receiver
Independent product line · device build workspace
The lab needs your participation.
I've sketched many configurations,
but most are not yet built.
Every failure of yours has value —
it belongs to you,
and to you alone.
Caveat —— Failure obeys diminishing returns too.
Too many of the same failure depreciate.
Four domains
It can defend; it can attack.
It can be the spear; it can be the shield.
Only your intent decides.
Flight controllers, FPV, UGVs, robotic arms — the firmware layer.
Example: ESP32-S3 + ELRS receiver
Smart switches, sensors, JLCPCB boards, Xianyu-built hardware.
Example: ESP32-C3 + custom PCB
Router firmware, zero-trust mTLS, encrypted tunnels, SPIFFE edge nodes.
Example: ESP32-S3 + SPIFFE workload
Camera vision, tinyML, local inference, LLM integration.
Example: ESP32-S3 + camera + ONNX
Workflow
Forge the gear you reach for first.
Sharpen your agent —
and yourself.
Three wizards — Sidecar for zero-trust mTLS, Bastion for standalone gateways, UGV for vehicle control. Fill in BOM, sensors, and protocol stack once; save as reusable profiles.
Every profile can be edited or replayed independently
Multiple ESP-IDF versions (v5.x / v6.x) coexist; pre-warmed caches let the remote agent handle the compile. Logs stream back over WebRTC. Your machine never installs ESP-IDF, Python, or CMake.
Failure is data too — failed builds can be signed into a triple
When the build is green, flash directly over Web Serial from the browser. For offline targets, download .bin and use esptool or espflash locally.
Billed per build, not per minute
Where it sits
An agent's agent.
A lieutenant's lieutenant.
Every line gets a reply; every thing finds its place.
Division of labor. Collaboration.
Agent writes the code. Browser tunes compile flags. Cloud compiles.
View ESPCTL MCPBig models do the exploratory work; small models do the deterministic verification. Picks up the cloud-built artifact → flashes the device → runs physical verification → signs the build into a requirement + code + verification triple in ~/maker-assets/. Triples never leave your disk.
View espctlYour agent counts and reports. You review, then plan.
View OpsIndependent product line · device build workspace
No ESP-IDF install, no Python venv, no CMake. Open the browser, work through the wizard, and ship your first ESP32 firmware.