M5Stack StickS3 + AIFlow

Modular stick form factor + AI-assisted programming — the low-friction lane into the same agent I/O loop

← Cyborg wave hub · Shopping list · Principles · E‑paper path · Character path

Status: platform research / field notes — kit not required for the e‑paper first build.

Source post: M5Stack — “No PC, no phone, just StickS3. AI programming with AIFlow.”

What this path is

M5Stack sells modular ESP32-class devices (sticks, cores, atoms) with batteries, screens, and accessory ecosystem. The StickS3 post is selling:

Form factor: pocket / desk stick — good for demos, badges, “always there” triggers
AIFlow: AI-assisted programming/flow story aimed at less traditional embedded pain
Narrative: “no PC, no phone” for the interaction demo (bring-up still needs a computer once)

Same cyborg architecture as the hub: stick = sensors + UI + Wi‑Fi; agents + vault do the thinking.

What this path is not

Not a replacement for understanding HTTP + agent APIs (you still need endpoints)
Not automatically better e‑paper (StickS3 is a different UI class than Waveshare e‑paper AIoT)
Not free of vendor lock-in tradeoffs — ecosystem speed vs bare-metal control

When to choose M5 vs bare Waveshare

Choose M5 StickS3 (or Core/Atom)	Choose bare e‑paper ESP32 kit
Want demos this week with modules	Want the Vinny-style e‑paper console specifically
Event badge / stick / pocket form	Always-on desk status with paper-like display
Prefer ecosystem cases + HAT-style addons	Prefer lowest cost / full control of every pin
AIFlow / UIFlow learning curve fits you	PlatformIO + Arduino samples fit you

Default order on this site: prove dump + status on e‑paper path or a cheap stick; use M5 when you care about demo reliability and form factor.

Parts list

Cart C: /cyborg-shopping#m5 · shop: shop.m5stack.com

Priority	Item	Search	Why
P0	Main unit	`M5Stack StickS3` / M5StickS3	Stick form factor from the source post
P1	Mic unit	M5 Unit matching your series	Voice without soldering
P1	Speaker unit	Only if talk-back	Optional for dump-only
P0	USB‑C data cable	—	Flash + power

Buy one stick + one unit for the first demo. Confirm AIFlow / battery on the current SKU before checkout — M5 product lines move quickly.

Tutorial ladder

Unbox → official “hello” + Wi‑Fi sample (vendor docs first, not random GitHub)
One button or IMU gesture → serial log (prove input)
HTTP GET to a public JSON URL; show one field on screen
Point GET at your /status stub (same contract as e‑paper path)
One AIFlow (or UIFlow) path: button → webhook POST with device id
Server: webhook → HEOS note or Arthur inbox text
Optional: mic unit → voice path shared with character / e‑paper backends
Event mode: badge-style label + single “dump” affordance for meetups

Skills & docs to follow

M5Stack docs for StickS3 (Arduino / UIFlow / AIFlow as available)
M5 product examples for Wi‑Fi HTTP client and display
Your shared API: keep /status and /voice-in identical across boards so firmware is the only fork
Event badge prior art on this site: content notes on ESP32 + e‑ink badges (see eventbadge ideas in the knowledge base)

Map to agents & events

Use	Agent / system
Pocket dump stick	`arthur.agent` → HEOS inbox
Ops “what’s next” stick	`janice.agent`
Conference badge presence	Stage Agent / host mic moments

Design rules

Same API as other paths — don’t invent a second backend for M5
Demo > cleverness — one reliable button story beats five half-broken sensors
Still write to vault — stick taps that vanish after the demo are theater
Blast radius — webhook key is dump/status only

First ship definition

Done when:

Stick shows one live status field from your API
One physical action creates a HEOS / agent inbox entry
You can redo the demo cold in under two minutes

Related paths

Cyborg wave hub

All three paths compared.

Hub →

E‑paper console

Vinny-style status + voice dump.

Path →

Character device

Product / face / gift framing.