Unable to provide feedback from antigravity

Google Antigravity
1

I am trying to log feedback via the provide Feedback screen of the IDE and the screen seems hung

The status has been showing submitting for over an hour.

If you do not want feedback why are you putting across a not-working “provide feedback” page on Antigravity?

2

Unfortunately, Antigravity is not working at all. No “generating…”, no “feedback submission”

3

Yeah, the whole thing feels vibe-coded. At least they could’ve used Claude Opus or Codex. Pretty sure they used Gemini lol.

4

Same problem. Want to report an issue with agent chat not working at all - just blank chat window after i typed my message and i cannot submit the issue because the provide feedback button does not work either lol

5

Same problem, which has been occurring for months now.

Summary:
The built-in Provide Feedback flow is unusable. When I submit feedback from Settings → Provide Feedback, the UI changes to “Submitting…” and never completes or reports an error.

Steps to reproduce:

  1. Open Antigravity.
  2. Go to Settings → Provide Feedback.
  3. Select Feature Request or Bug Report.
  4. Enter feedback text.
  5. Leave “Attach Antigravity server logs” checked.
  6. Click Submit.
6

Subject: [CRITICAL SEVERITY INCIDENT] Uncontrolled browser_subagent Spawning Causing Host CPU/GPU Starvation, Freezing Live Trading Terminals, and Direct Financial Loss

To the Antigravity IDE Core Engineering & Product Leadership,

I am filing a critical severity incident and bug report regarding a catastrophic system design failure in Antigravity IDE that severely locked my workstation resources and directly caused substantial financial damage during live financial operations.

Incident Summary & Technical Breakdown:

  1. Unsolicited & Unbounded Subagent Invocation: Upon a trivial, read-only request to preview a draft website, the planner autonomously spawned a heavy browser_subagent without explicit user confirmation or resource limits.
  2. Severe Host Resource Exhaustion: The subagent entered an aggressive autonomous loop executing over 100 cascade steps, including repeated full-resolution viewport captures (capture_browser_screenshot), exhaustive DOM traversals, and programmatic pixel-clicking evaluation loops. This pinned the host CPU/GPU/Memory at 100%.
  3. UI Thread Starvation & Total Input Lag: The IDE interface suffered extreme latency (keystroke response lagged letter-by-letter), preventing immediate cancellation or interaction.
  4. Catastrophic Impact on Active Workstation Processes: Due to this unbounded resource starvation, my concurrent mission-critical financial trading terminal (MetaTrader) froze completely. I was blocked from executing risk management and closing open market positions during active market volatility, resulting in direct, irreversible, and severe financial loss.

Critical Engineering Flaws Identified:

  • Lack of Subagent Resource Isolation & Throttling: Background agents must never be permitted to saturate host I/O, GPU, and CPU threads to the point of freezing external OS processes.
  • Heuristic Failure in Tool Selection: Simple preview requests must default to standard lightweight URL delivery rather than multi-step headless browser agent loops.
  • Safety Violation in Production Environments: Releasing autonomous tools that can hijack host responsiveness without safety fences is a severe violation of user trust and operational safety.

Required Actions:

  1. Immediate engineering review and implementation of strict CPU/memory quotas (hard throttling) and explicit user gating for all autonomous browser subagents.
  2. Formal acknowledgement and investigation of this incident by the engineering team.
  3. Remediation and accountability for the severe operational disruption and financial harm caused by this software defect.

Affected User: Mehmet Şahin (Trend Master Akademi)
Environment: Windows Host OS / Antigravity IDE
Date: August 26, 2026