MaxIntel Scout · companion
Scout Studio
Plug a MaxIntel Scout (ESP32‑S3) into this computer over USB‑C and flash it, watch what it hears live, and send it commands — all in the browser, no app and no Arduino IDE. Flashing works on a blank board; the live monitor needs Scout firmware that emits the Scout protocol over USB‑CDC.
Firmware v1.0 · Updated 2026-10-27 · board: Waveshare ESP32‑S3‑Touch‑LCD‑1.54
Flash firmware
Flashing runs entirely in your browser over the Web Serial API (the browser’s interface to the board’s USB‑serial port) using esptool‑js — Chrome, Edge or Opera on a computer, or Chrome on Android. Plug the Scout in over USB‑C. If the board won’t connect, hold BOOT, tap RESET, release BOOT, then try again.
Full install erases the chip and writes bootloader + partitions + app (for a blank or recovered board). Update app only keeps your settings and rewrites just the app — use it to move to a newer build. Both pull the official v1.0 image (scout-firmware/) listed in the manifest.
Advanced / custom build — flash your own .bin
Offsets for a split build: bootloader 0x0, partitions 0x8000, boot_app0 0xe000, app 0x10000. A single merged .bin goes at 0x0.
Live monitor
Decoded stream
Device control
Real Scout commands (sent as framed protocol messages). Needs a live connection above.
These encode CMD_MODE, CMD_CFG, CMD_PORTAL and CMD_REBOOT from the Scout protocol. Pushing updated surveillance‑maker lists over USB needs a firmware message that doesn’t exist yet — for now, the maker list lives here and ships baked into the build.
Updates & connected mode
Scout’s datasets and firmware are versioned in a manifest on maxintel.org. A connected Scout (joined to Wi‑Fi in STA mode) polls this to pull newer surveillance‑maker and stalkerware lists and, when published, OTA firmware. It’s served same‑origin, so it loads here too.
The device’s other connected apps call the endpoints listed in the manifest: aircraft overhead (ADS‑B), the maker list, the stalkerware list, and DeFlock/Overpass ALPR cameras. OTA firmware links appear once a compiled .bin is dropped in /scout-firmware/ and recorded in the manifest.
What this is and isn’t
- Passive only. Scout and this companion listen and report. No deauth, jamming, spoofing or evil‑twin — by design, and that’s what keeps it legal to carry and run.
- Flashing is universal (any ESP32‑S3 in download mode). The live monitor needs firmware that tees the Scout protocol out over USB‑CDC; the UART targets do this today, the touchscreen flagship needs a small firmware hook.
- Nothing is uploaded. Serial data and firmware stay in your browser and the cable.