[BUG] Claude for Gmail connector lacks gmail.modify scope — label_thread returns permission error
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?
Problem
The label_thread tool returns a permission error when called via the Gmail connector in Claude Code.
Root Cause
Checking Google Account permissions at myaccount.google.com/permissions shows that "Claude for Gmail" only has:
- View profile info
- Manage drafts and send emails
- View email messages and settings
The gmail.modify scope (required for labeling) is NOT included.
Reconnection Blocked
Attempting to reconnect the Gmail connector shows a hard "This app is blocked" screen from Google with no way to bypass it. There is no "Advanced" / "Proceed anyway" option.
Expected Behavior
The Gmail connector should request the gmail.modify scope so that label_thread and similar write operations work.
Environment
- Claude Code on macOS
- Gmail connector (Claude for Gmail)
What Should Happen?
The Gmail connector should request the gmail.modify scope during OAuth authorization, so that label_thread and other write operations work correctly.
Error Messages/Logs
This connector requires additional permissions. The user needs to reconnect it with the appropriate access.
Steps to Reproduce
- Set up a scheduled task that calls
label_threadvia the Gmail connector - Run the task
- Error occurs: "This connector requires additional permissions"
- Attempt to reconnect the Gmail connector in Claude Code settings
- Google shows a hard "このアプリはブロックされます" (This app is blocked) screen with no way to proceed
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
1.569.0(49894a)
Platform
Other
Operating System
macOS
Terminal/Shell
Other
Additional Information
Platform: Claude Code (desktop app, macOS)
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗