VibeDesk — narration script Voice: Dane – Conversational (existing authorized ElevenLabs clone) Tone: first-person builder story. No music. 01 — A desk for my AI agents I built VibeDesk because the more coding agents I used, the more time I spent figuring out what each one was doing. I wanted one place to see the work, understand what needed me, and send a reply. Let me show you the desk we built. 02 — Start with what needs you These are fictional projects in the real app. On the left, I can see my sessions across projects and providers. Needs You brings waiting sessions and failures into view. That gives me a useful starting point when I come back to the desk: which decision is holding up the work? 03 — Keep the work where you put it One of the details I care about most is that the list stays where I put it. Activity doesn't keep rearranging my sessions. I can drag them into my own order, and the child sessions stay grouped with their parent. I can also reorder children within that family. 04 — One agent. One conversation. When an agent starts a smaller piece of work, that relationship belongs in the sidebar. Clicking the child opens just that conversation. Here, I'm reading the keyboard review on its own. I don't have to untangle it from an expanded section inside the parent's conversation. 05 — Read back without losing your place The reading pane turns saved session messages into a conversation I can follow. Earlier and Newer let me page through saved history, and Latest returns me to the live view. New activity doesn't pull me out of the page I'm reading. The depth depends on what the provider actually saved. 06 — Reply with room to think For a reply, I can type, insert a reusable snippet, or dictate when the microphone and local transcription are configured. Drafts belong to their sessions. There's also a preview and cancellation window before delivery. Those details matter when several agents are open and a reply needs to reach the right one. 07 — Keep the Coordinator in reach The Coordinator is a destination I choose. It can be the existing Grok Bot integration, or a local session from my desk. That choice stays independent of the conversation I'm reading. I can ask the Coordinator about the release while I stay here reviewing this agent's work. 08 — Useful numbers, with context I also want a quick sense of usage without turning the whole screen into a spreadsheet. I choose which providers appear at the top. Opening a provider separates its reported cost, reporting coverage, usage windows, and model details. These are session reports, so I don't treat them as an invoice. 09 — Make the controls fit the habit The optional Ulanzi pad gives this a physical side: a knob, buttons, and push to talk. Settings exposes the supported button gestures, including double press and hold. The browser works on its own too. Searchable settings keep those choices together, instead of making the main screen carry every control. 10 — Built around the work Underneath, VibeDesk connects the browser to local session information, hooks, and the tools already running on my Mac. Optional bots and notifications can use outside services. What I like about it is simple: I spend less time looking for the right window, and more time understanding the work in front of me.