It is saying it failed to Login to Google. Is this why I am suffering from suddently ending up on days of cooldown

Google Antigravity
1

Here are my Anti-Gravity Logs
2026-01-28 08:24:55.472 [info] 2026/01/28 08:24:55 maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined

2026-01-28 08:24:55.540 [info] I0128 08:24:55.536689 480666 server.go:1152] Starting language server process with pid 480666

2026-01-28 08:24:55.540 [info] I0128 08:24:55.536745 480666 server.go:287] Setting GOMAXPROCS to 4

2026-01-28 08:24:55.540 [info] I0128 08:24:55.540266 480666 server.go:479] Language server will attempt to listen on host 127.0.0.1

2026-01-28 08:24:55.540 [info] I0128 08:24:55.540617 480666 server.go:494] Language server listening on random port at 36867 for HTTPS

2026-01-28 08:24:55.540 [info] I0128 08:24:55.540663 480666 server.go:501] Language server listening on random port at 46689 for HTTP

2026-01-28 08:24:56.280 [info] I0128 08:24:55.862111 480666 server.go:472] Created extension server client at port 45639

2026-01-28 08:24:56.280 [info] W0128 08:24:55.891961 480666 client.go:137] failed to set auth token

2026-01-28 08:24:56.280 [info] W0128 08:24:55.893088 480666 log_context.go:106] Cache(userInfo): Singleflight refresh failed: You are not logged into Antigravity.

2026-01-28 08:24:56.442 [info] (Antigravity) 2026-01-28 08:24:56.441 [INFO]: Language server started

2026-01-28 08:24:56.457 [info] I0128 08:24:56.447841 480666 server.go:1504] initialized server successfully in 911.071652ms

2026-01-28 08:24:57.203 [info] 2026/01/28 08:24:57 http: TLS handshake error from 127.0.0.1:39460: remote error: tls: unknown certificate

2026-01-28 08:24:57.301 [info] (Antigravity) 2026-01-28 08:24:57.301 [INFO]: LS lspClient started successfully

2 Likes
2

Hello @MonkeyDrone, welcome to AI Forum!

These two behaviors are likely connected. If the tool fails to authenticate you, it cannot validate your usage quota and often defaults to a ‘cooldown’ or error state as a fallback. We recommend performing a full Sign Out and Sign In cycle. This usually clears the stuck ‘failed login’ state and restores your correct access limits immediately.

3

I have tried logging out, closing the app, starting it up again and logging in, after that when I restart, I see the same logs,
2026-01-29 06:11:58.807 [info] W0129 06:11:58.495453 904179 client.go:137] failed to set auth token

2026-01-29 06:11:58.807 [info] W0129 06:11:58.501193 904179 log_context.go:106] Cache(userInfo): Singleflight refresh failed: You are not logged into Antigravity.

I don’t think this is a simple ‘tried turning it off and on again’ situation.

4

Yeah I’m having the same thing
2026-01-28 22:53:07.487 [info] W0128 22:53:07.486472 58506 client.go:137] failed to set auth token
Cannot use Claude since one week. I’m a pro user.
Simply not serious from Google since the bug is here for a week almost now.