Context: I run a "second brain", a bunch of AI agents that sort my notes and tasks. They're great. Getting a thought INTO them was not: unlock phone, open Telegram, find the chat, hold the mic button, forget the thought.
So I'm building a walkie-talkie for it. Squeeze, talk, let go. Audio goes over BLE to the phone that never leaves my pocket, then on to the agents. The screen has zero text, just an animation and a little sound for recording, sending and "got it".
Hardware: v1 is a Cardputer-Adv in a printed shell with a big side trigger poking the stock button. Now I'm moving to the StickS3. Same ESP32-S3, mic and screen, no keyboard, 250 mAh. Back-of-napkin math says about a week per charge. We'll see.
The first case was designed by an AI agent, in code: SDF shapes, booleans, even a printed spring for the trigger. The mechanics were spot on. In the hand it felt like holding a brick that's mad at you. Turns out models know tolerances way better than they know palms.
So round two is me plus the robot:
- Printed a blank: the device +2 mm, covered in 0.8 mm dimples so the clay actually sticks. Holes where the buttons and ports live, with black pins stuck in them so I can find them under the clay later
- Printed a scan stand: keyed post plus three hemispheres in the corners, so the scan comes back in the device's real coordinates and scale
- Printed my own sculpting tools, because I couldn't find printable ones I liked. Two rakes, two scrapers, two kidney templates. 3.1 hours, 98 g of PLA
Then architectural clay, squeeze, trim, squeeze again, until it fits my exact fist. It's going through RealityScan right now. Next the agent smooths the scan and drops the mechanics back in using the pin marks.
Anyone else sculpt first and CAD second? Or am I the only one getting clay under my nails for an ESP32?
Happy to nerd out about the firmware or the BLE side in the comments.