Back to corpus
architecturetechnical paper candidatescore 40

Agent Command Center — Voice-First Architecture

The ACC isn't just another iOS app — it's the **voice-first command interface** for the entire agent stack. Discord has been serving as the de facto command center. ACC formalizes that into a native experience where **voice is primary, visual is secondary**.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Agent Command Center — Voice-First Architecture **Status:** 🌱 Design Phase (from Mo's 1:21 AM voice notes, Feb 16 2026) **Origin:** Voice brainstorm → formalized spec > "The voice itself is the most intuitive... Discord was our Agent Command Center replicate." The ACC isn't just another iOS app — it's the **voice-first command interface** for the entire agent stack. Discord has been serving as the de facto command center. ACC formalizes that into a native experience where **voice is primary, visual is secondary**. ### Layer 0: Voice Interface (Primary) - **Always-on voice capture** → transcription → intent routing - Google Speech-to-Text API (enabled on `speech-to-order-476916` project) - Fallback: local mlx_whisper (on-device, offline-capable) - ElevenLabs voice clone (Mohamed voice ID: `TmSgyk1vGAD9YzdtJV3V`) for responses - VisionClaw's ambient voice pipeline patterns as reference (but actually functional, not stubbed) ### Layer 1: Command Center UI (Background) - SwiftUI + TCA (already built through Phase 4) - Mission Control view = visual confirmation of voice commands - Thread visualization = see Pulse execution trees - Infrastructure health = at-a-glance agent status

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.