BUREAUDevice · 2026 · M5Stack Core2 and Mac
A pixel you that waits for agents instead of you.
The desk console watches every AI agent session on your Mac and calls when one needs you. Tap or speak, and the answer lands in exactly that chat.
Built it end to end: firmware, the Mac server, the sound and the call, a pixel twin of ~110 frames.
The agent is waiting for your decision
How it works every day on the desk- The agent asked a question and waits in silence.
- Five sessions open, no way to see which one is stuck.
- You notice only when you happen to check the terminal.
Two notes, a buzz, the pixel twin waves. The screen shows the project and the agent's question in plain words. Tap "go" and work continues, or "say" and your voice types straight into its chat.
How the console knows you're needed
Each session reports its own state to the console. The queue goes: asking, waiting, stuck, working. The card opens by itself only when an agent asks a question or needs permission.
A raw terminal command says nothing. Within seconds a fast model writes the gist on the card: "Deploy the site to Hetzner", with the command in small print below.
Your voice types into that very session's tab, not wherever the cursor is. Buttons send exactly what's written on them: the console can't speak for you.
What's on the screen
Clock, plan limits as a traffic light, and one line: who's waiting.
One at a time: decide, next one up, "1/3" in the header.
Who's asking, who's thinking and how many minutes they've waited.
The last six events in words, with times.
Speech without an agent's name goes to the cursor on the Mac.
Blinks, listens with a hand to its ear, falls asleep after three quiet minutes.
