When it will not connect
The failures worth recognising, and what each one means.
The browser step never opens
Authorisation happens in a browser window that the client opens on a fixed local port. If nothing appears, something else is usually holding that port. Close whatever it is and run the authorisation again.
It opens, but you are asked to sign in
The consent screen is an ordinary unpitch page and needs you signed in on the same browser. Sign in, then start the authorisation again from the client rather than reloading the consent page — the request it carries is single-use.
It says the request is no longer available
That request was already used or replaced. Start a fresh authorisation from the client.
Authorising twice in a row is the usual cause: the second attempt replaces the first, and the first stops working the moment it does.
Every request is refused after it worked before
Three things end a connection, and all of them are permanent for that connection:
- you revoked it in Settings → Integrations;
- you authorised again, which replaces it;
- you lost access to the organisation.
Reconnecting gives you a new connection. It does not revive the old one, and tokens from it stay dead.
A run is refused but you still have credits
You have crossed the organisation's spend window for Claude Code. The refusal names when it resets. See Credits and limits — the ceiling counts what has been committed rather than what has settled, so it can refuse while your balance still looks healthy.
An edit is refused as a conflict
The document changed in the browser since Claude Code last read it. That refusal is the feature: the alternative is silently overwriting the newer version. Have Claude Code read the document again and reapply the change.
Still stuck
Everything about the connection's current state is on Settings → Integrations — which workspace it is bound to, when it was last used, and the button that ends it. Revoking and authorising again resolves most states that nothing above explains.