This account was recently reinstated following a bot-flag event. While general Gemini chat functionality has returned, the Antigravity Language Server deadlocks immediately during the authentication process. Specifically, the logs show the process initializing and then hanging indefinitely at the line: Setting GOMAXPROCS to 4.
Troubleshooting Verified:
-
Local Environment Health: The application and local environment are verified as functional. I am able to log into a different account on this same machine and installation without any issues.
-
Permissions: Full Disk Access has been granted to both Terminal and the IDE. All macOS security/TCC attributes (quarantine flags) have been cleared.
-
CLI Initialization: Attempting a manual headless login via the binary (
auth login --consumer) results in the same indefinite hang immediately after the PID is assigned and the processor count is set.
Request: The issue appears to be a backend “Security Challenge” or a stale “Identity Seed” triggered by the account’s recent history that the local binary cannot resolve in its current state. Please flush the server-side identity seed for the account associated with this post to allow the language server to generate a new, valid security key.