Summary
In Google Antigravity (tested on v2.28.0, Windows 10/11 desktop application), the voice dictation button in the chat prompt bar automatically binds to the OS-default recording device. There is currently no UI mechanism within the application to choose or prioritize a specific audio input device.
Current Pain Point
Developers utilizing dedicated audio hardware (e.g., XLR interfaces, standalone USB cardioid microphones, virtual audio cables) alongside secondary communications hardware (Bluetooth headsets, webcam mics) are forced to leave Antigravity and navigate deep into the OS settings (ms-settings:apps-volume on Windows) to route the correct microphone to the Antigravity process.
Proposed Solution
Introduce an audio input selector directly adjacent to the voice dictation microphone icon in the chat bar:
-
Dropdown / Chevron trigger: A discreet dropdown arrow next to the mic icon (similar to the model selector
Gemini 3.8 Flash Medium ∨). -
Device Enumeration: Populate the menu dynamically via standard web APIs:
const devices = await navigator.mediaDevices.enumerateDevices(); const audioInputs = devices.filter(d => d.kind === 'audioinput'); -
Selection Persistence: Store the chosen
deviceIdin the workspace or global user profile settings (settings.jsonunderantigravity.chat.audioInputDeviceId). -
Fallback: If the selected device is unplugged, cleanly fallback to the system default input device without throwing runtime exceptions.
Value & UX Impact
- Eliminates context switching to OS-level sound settings.
- Significantly improves accessibility and dictation accuracy for developers with multi-microphone configurations.
- Matches modern standards found in video conferencing and voice-enabled developer tooling.
