googlecodelabs
[getting-started-google-antigravity]
Antigravity Bug Report: Persistent ERR_CONNECTION_REFUSED and Setup Failures on Windows
This report details two major blocking issues encountered while attempting to set up and run a local project (static HTML/CSS) using the Antigravity application on Windows.
Issue 1: Forced Edge for Chrome Extension Install The application consistently forces a non-default browser (Microsoft Edge) to open the Chrome Web Store link, which causes the initial installation to fail.
Steps to Reproduce: Start the Antigravity application.
Click the "Install Extension" button in the setup flow.
Actual Behavior: The system opens the Microsoft Edge browser, even when Google Chrome is set as the system's default browser (confirmed via Windows Settings).
The installation fails in Edge with the error: "Download Interrupted" or "Erro no download: download interrupted".
Resolution/Workaround: The extension could only be installed successfully by manually copying the Chrome Web Store URL from the Edge address bar and pasting it directly into an already open Chrome window.
Issue 2: Silent Server Startup Failure (ERR_CONNECTION_REFUSED) After successfully installing the extension and configuring the Chrome binary path manually, the local project server fails to start, blocking all project previews.Steps to Reproduce:Create or open a simple static project (e.g., index.html and style.css).Go to the top menu and select Run $\rightarrow$ Start Debugging.The browser (Chrome, as configured) launches automatically.Actual Behavior:The Chrome browser opens to the correct address (http://localhost:8080 and later tested on http://localhost:8081).The page displays the error: ERR_CONNECTION_REFUSED (A conexão com localhost foi recusada).The Antigravity IDE fails silently: Checking the Terminal, Output, and Debug Console tabs shows absolutely no error messages or output after running the command (all logs remain empty).Technical Debugging Summary:Windows Firewall was confirmed to allow the Antigravity application (Inbound/Outbound rules were enabled).The port number was changed multiple times in launch.json (8080, 8081) to rule out port conflicts, but the error persisted.The Chrome Binary Path was manually defined in Antigravity Settings $\rightarrow$ Browser.The silent failure strongly suggests a core dependency issue (e.g., the application cannot locate or execute the Python/Node runtime needed to start the server) which is being terminated by the operating system before the IDE can capture the error log.
