Vision: hands-free shower-speaker agent direction over Bluetooth call

[heavygee]

Vision (north star, not actionable today)

Take a shower. Direct agents over a Bluetooth shower-speaker via audio call.

The capabilities this implies, all of which already exist in pieces:

• Voice IO -- already shipping with ElevenLabs / Gemini Live / Qwen Realtime (fix(web): use session flavor label in voice context formatters #1 STT separately).
• Hands-free -- no keyboard, no screen, no glance. Pure audio loop.
• Multi-agent context -- "ask the voice-dropdown agent how the rebase is going" -- needs UX: TL;DR-first response rendering with expand-to-full setting #9 (@autocomplete sessions) and Tooling: agent-driven fileFutureIdea tool that posts to fork issues #10 (project page / dispatcher) to make sense over voice.
• TL;DR-first -- absolutely mandatory (STT: OpenWhispr local listening pipeline -> HAPI things-to-do inbox #5). A shower call can't tolerate 800-word essays.
• Channels / push -- inbound events ("PR just got a review", "build failed") need to arrive as voice notifications (UI: @ autocomplete to reference other running sessions / agents #13).
• Bluetooth audio -- standard A2DP/HFP. The hard part is not the BT, it's the orchestration.
• Bandwidth-aware -- waterproof speakers usually have terrible mics; system must work with degraded input.

Use

This is the acceptance test for the whole product direction. If you can run a 20-minute shower call directing five concurrent sessions and end up productive, the rest of the stack is doing its job. If you can't, identify which sub-issue (#1, #5, #9, #10, #13) is the blocker.

Status

Pure vision. No work item. Closes when the shower call actually happens and works.

[heavygee]

Fleet Overseer architecture cross-reference (#19)

This hands-free / shower-speaker direction becomes live from Step 5 (#27, chrome-button move) of the Overseer architecture: once the chrome voice button is the primary surface across web / mobile-web / webXR, the "mobile-web + bluetooth audio routing" use case is reachable. Persistence groundwork is Step 1 (#21); the Overseer conversational entity is Step 3 (#25). See the umbrella #19.