[BUG] Connector scope granted on claude.ai never reaches an open desktop session; status stays "connected", /clear and reconnect don't refresh the token

What happens

A claude.ai connector (Google Calendar) is used from the Claude desktop app, Code tab. A write tool call (create_event) fails with:

This connector requires additional permissions. The user needs to reconnect it from connector settings with the appropriate access.

The user goes to claude.ai connector settings, reconnects Google Calendar and grants write access. The consent page shows the write scope and the grant succeeds.

Back in the desktop app, the same tool call still fails with the same message. /clear in the session changes nothing. The session's connector status (session_connectors_status) reports Google Calendar as connected with 9 tools, so reconnect_session_connector refuses to act:

Google Calendar is connected; only a failed server can be reconnected.

The only thing that picks up the new grant is quitting the desktop app and starting a new session. Each time a connector needs a new scope, that is the ritual: grant in settings, quit the app, reopen, new session, repeat the request.

Expected

After the user grants a scope on claude.ai, the next call from an already-open session should use the new token, or at least:

• the session should report the connector as needing reconnect rather than connected, so the Reconnect path (/mcp or reconnect_session_connector) can re-dial it, or
• the "requires additional permissions" error path should invalidate the session's cached token so the next call re-authorizes.

/clear should be enough to pick up a new grant, and a running session should not need an app restart.

Environment

• Claude desktop app, Code tab, Windows Server 2022
• Claude Code 2.1.299
• Connector: Google Calendar (claude.ai first-party connector), scope added: calendar write
• Seen more than once, with Google Calendar; same symptom reported by others for Gmail (#81044)

Related

• #98097: consent page never requests the challenged scope (different failure; here the scope is granted but the session never sees it)
• #81044: connector shows "connected" in Settings but isn't available to sessions