Add a distinct sound notification whenever user input/authorization is required

I’d like to request a dedicated sound notification specifically for moments when Antigravity requires user input/authorization (for example, when an agent asks for approval before executing a command or action).

Right now, sound notifications are mostly tied to general activity (tasks finishing, agent responses, etc.), which makes it easy to miss critical prompts where the agent is actually blocked waiting for my decision. This is especially painful when:

  • I’m multitasking in other windows or on another monitor.

  • Long-running workflows eventually pause on an approval dialog, and I only notice much later.

  • I rely on Antigravity to run semi-autonomously but still want tight control over sensitive actions.

Requested behavior:

  1. Add a distinct, optional sound cue that is triggered every time Antigravity shows a UI element that requires explicit user input/authorization (e.g., “Approve / Deny”, “Allow / Block”, permission dialogs, etc.).

  2. Make this configurable in Settings, for example:

    • “Play sound when user input/authorization is required” (checkbox).

    • Ability to choose the sound or at least a distinct default separate from “task completed” or “new message” sounds.

  3. Ideally, expose this as a separate notification category at OS level as well, so users can tune or mute it independently from other Antigravity notifications.

Why this matters:

  • Prevents workflows from silently stalling just because I didn’t see an approval prompt.

  • Improves usability for power users who run long or complex agent flows in the background.

  • Helps accessibility and focus: the sound becomes a clear signal that my intervention is needed, instead of just “something happened”.

This seems like a small addition but would significantly improve reliability for anyone using agents that require explicit approvals for sensitive operations.

2 Likes

Hello @davidbragat ,

Welcome to AI Forum!
Thank you for your feedback. We appreciate you taking the time to share your thoughts with us, and we’ll be filing a feature request.
To help us prioritize this request effectively, any additional details you can provide regarding the impact this feature would have would be very helpful.

1 Like

Same UX gap exists in Claude Code, and the pattern you’re describing (different sound for authorization vs. turn-completion) is exactly what I ended up shipping as a VS Code extension after missing too many permission prompts myself.

A few implementation notes that might be useful to whoever at Google builds this:

  • Two distinct sounds work far better than one (permission requested vs. task finished). A single “something needs you” sound trains you to ignore it.
  • A short initial silent window (I default to 10s) is worth adding. If you’re already looking at the screen when the prompt appears, you don’t want a chirp.
  • Per-window scoping matters once people start running multiple agent sessions. Without it, you can’t tell which window is blocked.
  • Catch manually-rejected prompts too. In Claude Code’s case the normal hook doesn’t fire on user-rejection, so I have to tail the session transcript as a safety net. Worth designing around from day one.

For anyone on this thread who also runs Claude Code and wants the feature today: marketplace.visualstudio.mayerwin.ai-agent-sound-notification (source: GitHub - mayerwin/AI-Agent-Sound-Notification: VS Code extension that plays a distinct sound when Claude Code requires your authorization — configurable delays, back-off repeats, and Windows Focus Assist awareness. · GitHub). Free / OSS. Not Antigravity-specific, but the design notes above should transfer.