#Google Antigravity hangs "Waiting for OAuth Callback"

1 messages · Page 1 of 1 (latest)

winged horizon
#

openclaw models auth login --provider google-antigravity --set-default
(Or via openclaw configure, same result)
It just says

◓ Waiting for OAuth callback…..

and then

â—‡ Antigravity OAuth failed
Error: Timed out waiting for OAuth callback

limpid roverBOT
# winged horizon `openclaw models auth login --provider google-antigravity --set-default` (Or via...

That flow is waiting for Google to redirect your browser back to a local callback server on the machine running the command:

  • Redirect URI: http://localhost:51121/oauth-callback
  • The plugin actually binds the listener on 127.0.0.1:51121.

So it’ll time out if the browser never hits that URL, which usually happens in one of these cases:

  1. You’re running openclaw in Docker/WSL/SSH/remote box, but the browser you’re using is on a different machine (so “localhost” is the wrong localhost).
  2. The browser does redirect to http://localhost:51121/..., but it can’t reach the listener (common IPv6-ish symptom: browser tries ::1 first; listener is IPv4-only on 127.0.0.1).

Fast workaround (forces the “manual paste” flow)

Force OpenClaw to treat the environment as “remote”, so it prints the Auth URL and asks you to paste the redirect URL back:

SSH_TTY=1 openclaw models auth login --provider google-antigravity --set-default
#

Then:

  • Open the printed Auth URL in your normal browser
  • Complete login/consent
  • When it redirects to http://localhost:51121/... (it may show “can’t connect” — that’s fine), copy the full URL from the address bar and paste it into the CLI prompt

If you are local and it redirects but still times out

When the browser lands on http://localhost:51121/oauth-callback?...:

  • If it errors, replace localhost with 127.0.0.1 in the address bar and reload:
    http://127.0.0.1:51121/oauth-callback?...

Quick questions so I can point to the right root cause

  1. What OS + terminal are you running this on (macOS / Windows / Linux / WSL / Docker)?
  2. Does a browser window open at all during the flow? If yes, what happens after you click “Allow”?
  3. openclaw --version?

(Refs: plugin enable/login steps are in https://docs.openclaw.ai/concepts/model-providers and plugins overview at https://docs.openclaw.ai/plugin)

#

If the SSH_TTY=1 ... workaround fixes it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it.