[BUG] Google Calendar connector returns "Not connected" after OAuth granted
Open 💬 0 comments Opened Jun 16, 2026 by ejmeeting10-cloud
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Steps to reproduce:
- Connect Google Calendar with a Google account (ej.meeting10@gmail.com)
- OAuth completes successfully — Google Account shows "Claude for Google Calendar"
with full calendar permissions granted
- Any API call (list_calendars, list_events) returns "Not connected"
- Refreshing tools list, disconnecting/reconnecting, restarting Claude Code
all have no effect
Expected: API calls succeed after OAuth is granted
Actual: Always returns "Not connected"
Note: A different Google account (ej.meeting8@gmail.com) connected successfully
with the same connector previously.
What Should Happen?
API calls (list_calendars, list_events, create_event) should work after OAuth is completed and calendar permissions are granted.
Error Messages/Logs
Steps to Reproduce
- Connect Google Calendar connector with Google account A (ej8) → works fine
- Disconnect, reconnect with Google account B (ej10) → OAuth completes, all permissions granted
- Call list_calendars → returns "Not connected"
- Restart Claude Code, refresh tools list → same error
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.154 (Claude Code)
Platform
Other
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_