Critical Path Issue on Windows: Leading Slash in Resource URLs prevents UI from Loading #1198
Description
Environment:
OS: Windows 10/11 (x64)
Software Version: Antigravity v2.x (Latest Download)
Installation Path: D:\Antigravity\ or C:\Users\Administrator\AppData\Local\Programs\Antigravity\
The Issue:
The application fails to load UI components (specifically the Cascade Panel) and cannot complete the OAuth login process. Upon inspecting the main process logs, it appears the application is attempting to resolve local file paths with an incorrect leading forward slash on the drive letter (e.g., /d:/ or /c:/).
Error Logs:
Plaintext
[main 2026-01-08T05:19:55.223Z] [AgentClientServer] Cascade initializing for workspace
[main 2026-01-08T05:19:55.225Z] [AgentClientServer] HTML file does not exist: /d:/Antigravity/resources/app/extensions/antigravity/cascade-panel.html
Analysis:
The path /d:/Antigravity/... is not a valid absolute path in Windows. It seems the pathname derived from file:// URLs is being used directly without removing the leading slash that new URL() often prepends on Windows systems. Because the HTML file fails to load, the BrowserOnboardingClientServer cannot receive the auth-code callback, rendering the login process unusable.
Steps Taken (All Failed):
Reinstalled in default C: drive location.
Attempted to create directory symbolic links (e.g., mklink /D "D:\d:" "D:") which Windows rejected due to invalid characters.
Manually passed --auth-code via CLI (Warning: 'auth-code' is not in the list of known options).
Modified main.js to strip the leading slash in the Kqn function, but the error persisted in other internal modules.
Requested Fix:
Please ensure that file paths for local resources are correctly normalized for Windows by stripping the leading slash from the URL pathname (e.g., converting /C:/... to C:/...) before attempting to check for file existence or loading the renderer.
