The phone app for running the studio's agents. It lists every live agent session on the Mac and lets each one be read, answered and steered from the phone. It is the phone skin of the dashboard's Command Center, so the two share one set of logic.
Draft for OtoWhat the app does, written in third person from its own docs, for Oto to rewrite. His reasons are the dashed slots.
[screen: Command on the phone. Every live session shows client and family names, so it needs a staged session]
[Oto: why the studio is run from the phone, and what a session from it looks like]
How it works
6 parts
01
The session list
The app opens on the list of agent sessions, in Clients, Internal and Personal tabs, with Solo and Rooms above. Each row has a status dot, the agent's name and how long since it last moved; rows waiting on Oto are bold. Waiting clears only when he replies or marks it handled, not when he looks. The order is set by dragging and is the same on every device.
[screen: the session list. Live rows are client and personal folder names; needs a staged list]
02
A session
Tapping a row opens it full screen, on the conversation as chat bubbles, or on the live terminal when the agent is asking a question or for a permission. A toggle switches between the two, a key row sends Enter, arrows, Tab, Esc and Ctrl-C, and a gauge above the composer shows the model, how full its context is and the effort level.
[screen: one session open, on the conversation. Needs a staged session]
03
Voice and hands-free
A mic button records a voice note, which is transcribed on the Mac by a local speech model and sent as Oto's words with the audio kept. A speaker button reads each new reply aloud, and hands-free mode loops listening, thinking and speaking until he says stop.
[screen: recording a voice note over an internal session]
04
Rooms
Group threads with Oto and several agent sessions in one conversation, laid out as a group chat with each sender labelled and the members along the top.
05
Queue and Brief
A Queue row at the top of the list shows how many cards wait for Oto's yes and opens the approvals queue in place, with Send, Reject or Try again on each draft. A Brief row above it opens the latest morning brief, laid out as cards.
[screen: the Queue. Live cards are drafts to clients]
06
Usage, Files and Posts
Rings beside the title show the week's plan usage and the image credits left. Header buttons open Files, every file the agents have sent, newest first and shareable to WhatsApp or anywhere, and Posts, finished social posts with their captions, ready to share.
[screen: the header and the Posts shelf]
How it connects
To the other apps
Dashboard
Command is the dashboard's Command Center page in a phone skin, served by the same server.
Each row is a live Claude Code or Codex session on the Mac. Messages and voice notes are typed into it, and a session can be handed to the other model with a handover note.
The approvals queue
The Queue shows the same cards as the dashboard's Approvals page and the Desk's Cards sheet.
Vault Reader
Built from the same Mac app source, and used beside Command: the conversation on one side, the screen on the other.
Meetings
A record button in a session records a call for the meetings tool.
What it runs on
The plain version
A web app installed to the phone's home screen, served by the same Node server on the Mac as the dashboard and reached over a private network. Agent sessions run in terminal sessions on the Mac. Voice notes are transcribed on the Mac with a local speech model; spoken replies use a text-to-speech service.
I'm starting a new brand called The Agentic Operator.
It's a space to share what I'm learning around AI and agentic workflows. Builds, software, design and the future of work.