[BUG] Google Drive connector shows connected but tools not exposed in Cowork

Open 💬 57 comments Opened Mar 3, 2026 by javigoile

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?

Subject: Bug: Google Drive connector shows connected but tools not exposed in Cowork

Hi,

I'm experiencing an issue with the Google Drive connector in Cowork that persists after multiple reconnection attempts.

Symptoms:

  • The UI shows Google Drive as "connected"
  • However, the connector state shows "connected": false and "tools": []
  • No Google Drive tools are available in Cowork sessions
  • The OAuth flow appears to complete successfully on the surface, but the token exchange is not finalizing correctly in the backend

Steps already attempted:

  • Disconnected and reconnected via Settings > Integrations
  • Revoked access from myaccount.google.com/connections and reconnected
  • Tried in incognito mode

This appears to be a backend issue where the OAuth callback is not completing the authentication properly, similar to issues reported on GitHub (e.g., #30166).

Please advise or escalate.

Thank you.

What Should Happen?

Cowork should access my Drive files correctly

Error Messages/Logs

Steps to Reproduce

Connect Cowork with Google Drive successfully.
Try to prompt something using Drive with connector and not Chrome plugin

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude 1.1.4498 (24f768) 2026-02-26T19:47:09.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

57 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/30385
  2. https://github.com/anthropics/claude-code/issues/30166
  3. https://github.com/anthropics/claude-code/issues/29697

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

koszta5 · 4 months ago

same issues here

danielo515 · 4 months ago

Same here. IT says it is connected, but it says no tools available

Aurora-Boreal · 4 months ago

Same issue.

brcego · 4 months ago

same issue here

AlanLSavoy · 4 months ago

Same issue on Windows 11.

stenthepm · 4 months ago

When can we expect a fix? More than half of my productivity gains are gone :/

kss2002 · 4 months ago

same issue - mac

ben-edgar · 4 months ago

Same issue here trying to use cowork on a mac.

ben-edgar · 4 months ago

The drive connector is working for me again this morning. I'm not sure exactly why but I did perform these steps yesterday so sharing in case this helps others:

  1. Go to https://myaccount.google.com/connections and remove all Claude related integrations
  2. In cowork disconnect all the google connectors
  3. Restart cowork
  4. Reconnect all google connectors (drive, gmail, calendar, etc)
  5. Wait some amount of time -- initially it still didn't work but a few hours later when I checked it did 🤷

Goodluck everyone!

javigoile · 4 months ago
The drive connector is working for me again this morning. I'm not sure exactly why but I did perform these steps yesterday so sharing in case this helps others: 1. Go to https://myaccount.google.com/connections and remove all Claude related integrations 2. In cowork disconnect all the google connectors 3. Restart cowork 4. Reconnect all google connectors (drive, gmail, calendar, etc) 5. Wait some amount of time -- initially it still didn't work but a few hours later when I checked it did 🤷 Goodluck everyone!

Thanks @ben-edgar, tried that (had already tried it before) and it worked.
Connector does not support access to Google Sheets yet (have to use it via Chrome plugin), but it was able to access Docs without any problems now :)

danielo515 · 4 months ago
> The drive connector is working for me again this morning. I'm not sure exactly why but I did perform these steps yesterday so sharing in case this helps others: > > 1. Go to https://myaccount.google.com/connections and remove all Claude related integrations > 2. In cowork disconnect all the google connectors > 3. Restart cowork > 4. Reconnect all google connectors (drive, gmail, calendar, etc) > 5. Wait some amount of time -- initially it still didn't work but a few hours later when I checked it did 🤷 > > Goodluck everyone! Thanks @ben-edgar, tried that (had already tried it before) and it worked. Connector does not support access to Google Sheets yet (have to use it via Chrome plugin), but it was able to access Docs without any problems now :)

Can you please don't close the issue until this is confirmed to be a working solution for most of us?

javigoile · 4 months ago

Sorry about that @danielo515, issue re-opened.

jordivanvelzen · 4 months ago
The drive connector is working for me again this morning. I'm not sure exactly why but I did perform these steps yesterday so sharing in case this helps others: 1. Go to https://myaccount.google.com/connections and remove all Claude related integrations 2. In cowork disconnect all the google connectors 3. Restart cowork 4. Reconnect all google connectors (drive, gmail, calendar, etc) 5. Wait some amount of time -- initially it still didn't work but a few hours later when I checked it did 🤷 Goodluck everyone!

Worked for me. I didn't have to wait after performing these steps, it could see and access google drive right after

danielo515 · 4 months ago

Happy that it worked for all of you.
I followed all the steps that @javigoile indicated, reconnected and I am still at the same problem. Claude sees the connector,but it says that I need to connect it (despite, it is connected):

<img width="469" height="763" alt="Image" src="https://github.com/user-attachments/assets/82f2b429-9da8-403f-8f73-fea598b2c602" />

AndrewSav · 4 months ago

Same issue, steps above did not fix it

TungstenLION · 4 months ago

tried steps above, doesn't work for me either

JoshuaRedd · 4 months ago

Same issue here, tried the above steps, did not resolve.

ameliagoodson · 4 months ago

Same issue here on Mac. Reconnecting all of the connectors did not help.

JMarcos2000 · 4 months ago

Same issue, I need help.

JMarcos2000 · 4 months ago

I have same issue with Github connector. I am new en claude.ai

jantenna · 4 months ago

I was able to get it working by checking the google drive box. For some reason it was defaulted off.
<img width="546" height="398" alt="Image" src="https://github.com/user-attachments/assets/09c4a194-bcf4-449d-9eee-f27953333291" />

pluce · 4 months ago
I was able to get it working by checking the google drive box. For some reason it was defaulted off.

same here, it was defaulted off

danielo515 · 4 months ago
I was able to get it working by checking the google drive box. For some reason it was defaulted off. <img alt="Image" width="546" height="398" src="https://private-user-images.githubusercontent.com/209025645/563191548-09c4a194-bcf4-449d-9eee-f27953333291.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzM2NzcwODAsIm5iZiI6MTc3MzY3Njc4MCwicGF0aCI6Ii8yMDkwMjU2NDUvNTYzMTkxNTQ4LTA5YzRhMTk0LWJjZjQtNDQ5ZC05ZWVlLWYyNzk1MzMzMzI5MS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMzE2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDMxNlQxNTU5NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wMmYxNTBjZjBmZTZkYzY5YzI5NTUwN2ViM2ZhYjExZGZlN2Y2N2U3ODhhNmJmYmExNzM0ODAzZjg1YjViN2VhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.kqHKtRSRSo2BtUHs5VB9q14QStBACL_5DthLgHm-qns">

No, that is not my problem either. I have it checked from the very beginning:

<img width="449" height="277" alt="Image" src="https://github.com/user-attachments/assets/7b5bdf28-456d-4142-ad7a-dd193149452f" />

BVandenWymelenberg · 4 months ago

My box will not allow me to clock on the google drive box, it states" Select a different mode" it works in chat, but not in cowork or code.

michaelpnash · 3 months ago

Same error here (and yes, tried all the above)

noxxgit · 3 months ago

Same issue on Claude Code CLI (WSL2/Windows) — not just Cowork

Experiencing the same bug, but in a different context: Claude Code CLI running on WSL2 (Windows 11), not Cowork.

Symptoms:

  • Google Drive connector shows as "Connected" in claude.ai/settings/connectors
  • The file attachment picker in claude.ai (web) correctly lists my Drive files
  • However, no Google Drive MCP tools are exposed to Claude Code CLI — they simply don't appear in the available tool list
  • When asking Claude directly about Drive files, it responds as if the connector is not connected

What I've tried:

  • Disconnected and reconnected the Google Drive connector multiple times
  • Revoked access from myaccount.google.com/connections and re-authorized
  • Restarted Claude Code CLI after each reconnection attempt

Key observation: The file attachment picker (UI feature) works fine — it can browse and select Drive files. This suggests the
OAuth token itself is valid, but the MCP tool registration is failing on the backend. Gmail and Google Calendar connectors
(connected via the same claude.ai OAuth system) work correctly and their tools are exposed without issues.

Environment:

  • Claude Code CLI (latest)
  • WSL2 on Windows 11
  • Gmail MCP: ✅ working
  • Google Calendar MCP: ✅ working
  • Google Drive MCP: ❌ tools not exposed

Update: The hidden "Tools" toggle in claude.ai chat is the missing piece — but only for web, not Claude Code CLI

Confirming @jantenna's finding: there is a toggle under the + button in the claude.ai chat interface (not in Settings →
Connectors) that enables/disables individual tools per conversation. Google Drive is off by default. Enabling it makes the
connector work in claude.ai web chat.

However, this does not resolve the issue for Claude Code CLI (terminal). The + toggle mechanism only exists in the web
UI — there is no equivalent in Claude Code. So even after enabling it in web chat, the Drive MCP tools
(mcp__claude_ai_Google_Drive__*) still do not appear in Claude Code sessions.

This suggests the bug has two separate layers:

  1. The Drive toggle is off by default in new conversations — easy to miss
  2. Claude Code CLI has no way to set this toggle — Drive remains unavailable regardless
SylWms · 3 months ago

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported (related: #30457)
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude

---

Subject: [BUG] Google Drive connector shows connected in Cowork UI but fails to execute tasks

What's Wrong?
The Google Drive connector displays as connected in the Cowork interface, but when attempting to execute a task using the Google Drive connector, Cowork reports that Google Drive is not connected and fails to proceed.

The issue persists after:

  • Closing and reopening Claude
  • Restarting the computer
  • Verifying no updates are available

The connector status indicator shows connected, but the underlying tool access is not functioning — consistent with the OAuth backend issue described in #30457.

Steps to Reproduce

  1. Open Cowork
  2. Confirm Google Drive connector shows as connected in the UI
  3. Create a new task that requires Google Drive access
  4. Attempt to execute the task
  5. Observe: Cowork returns an error stating Google Drive is not connected

Expected Behavior
Cowork should successfully execute tasks using the Google Drive connector when it displays as connected.

Actual Behavior
Task execution fails with a 'Google Drive not connected' error despite the connector UI showing an active connection. Issue persists after full system restart.

Additional Context

  • Closing and restarting Claude did not resolve the issue
  • Full computer restart did not resolve the issue
  • No Claude updates were available at time of report
  • Related issues: #30457, #35739

Environment

  • Platform: Windows 11 (x64)
  • Claude version: Latest available (no updates pending)
acostela · 3 months ago

I'm having exactly the same issue as previous comment the only difference is I'm using MacOS

ericbrooke · 3 months ago

Same issue

josecodes · 3 months ago

+1 — same issue on macOS, enterprise/Team license

Google Drive connector shows as connected in Claude Desktop settings, but when I try to use it in chat/Cowork it reports "not connected" and falls back to browser-based access. Multiple reconnect attempts haven't helped.

Enterprise context: We're on an enterprise license. Worth noting this may involve Google Workspace admin-level OAuth restrictions — if the connector requires specific API scopes to be approved by a Workspace admin, that could explain why it silently fails after the initial OAuth handshake succeeds.

Additional data points from our team:

  • One colleague got it connected but could only access Docs, not Sheets
  • Another had it working previously but it stopped working as of 2026-03-24
  • One person reports it works but is "occasionally flaky" and sometimes falls back to browser

Already tried @ben-edgar's full disconnect steps (removing from https://myaccount.google.com/connections, disconnecting all Google connectors in Cowork, restarting, reconnecting) — no luck.

krauseeriko-hub · 3 months ago

Same issue – Cowork + Google Drive, business use case
I'm experiencing the same bug. Google Drive shows as "connected" in Cowork, but it cannot actually access any files.
I've tried:

Disconnecting and reconnecting multiple times
Restarting Cowork
Reconnecting via Claude.ai Settings → Connectors

None of these worked.
My use case: I manage a large volume of business documents shared with headquarters via Google Drive. I need to selectively upload local files to Drive and occasionally sync files from Drive to local. This is a critical workflow for my daily work, and the broken connector is blocking me completely.
Please prioritize this fix. Thank you.

ulrikewo · 3 months ago

Same issue

Ortes · 3 months ago

This makes Claude useless for a lot of usecase this should be P0

godlevski · 3 months ago

plus one on above

twellspring · 3 months ago

I am getting something similar.

When I finish the auth flow and switch back to cowork there is a brief "Google Drive Connected' notification in the upper right corner, but the customize/connectors never shows Google Drive as connected. I have refreshed and closed/opened Claude after doing this and Google Drive still does not show as connected.

zbeekman · 3 months ago

same issue here

josepascual-eng · 3 months ago

same exact issue. Disconnecting and reconnecting does not fix. Gmail and Calendar are working

antonpogodin · 3 months ago

The same issue on Mac - Google Drive connector shows as connected in Claude Desktop settings, but when I try to use it in chat/Cowork it reports "not connected" and falls back to browser-based access. Multiple reconnect attempts haven't helped.

DamienCdindy · 3 months ago

I am not sure that it fixes your issue but I just discovered that the drive connector is disabled by defaut on cowork and that you need to proactively authorize it on the prompt interface. When you want to send a new prompt you have to go to the plus sign, connectors and enable the search-drive feature. Hope this helps.

josepascual-eng · 3 months ago

This was exactly the issue. Thanks Damien

Have a great day
Jose

On Tue, Apr 7, 2026 at 4:59 PM DamienCdindy @.***>
wrote:

DamienCdindy left a comment (anthropics/claude-code#30457) <https://github.com/anthropics/claude-code/issues/30457#issuecomment-4199967028> I am not sure that it fixes your issue but I just discovered that the drive connector is disabled by defaut on cowork and that you need to proactively authorize it on the prompt interface. When you want to send a new prompt you have to go to the plus sign, connectors and enable the search-drive feature. Hope this helps. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/30457#issuecomment-4199967028>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B6REXY3YESB5TXDRRMTDLIL4UUJV5AVCNFSM6AAAAACWFWJQ2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJZHE3DOMBSHA> . You are receiving this because you commented.Message ID: @.***>
mattbvb · 3 months ago

Anthropic, way to go welcoming a new subscriber! Lots of server outages. Broken Drive connector. Thimble-size session memory. Maybe I should go back to Gemini, as much as that makes me nauseous. Let me see if I understand the Anthropic model. Build a sexy but unsustainable system. Lure in unsuspecting users. Fall on your face. Watch, as your stock gets shorted into oblivion. You're running out of runway.

deesylove · 3 months ago

Same issue

rjoshi · 3 months ago

I thought Claude code is expected to look at issues, code a fix, test it and review it and merge it. But apparently that doesn't work for Anthropic 🦖

davehob · 3 months ago

same issue here on m1 pro mac

zbeekman · 3 months ago

toggling it in the chat fixed this for me. I don't know why every other integration defaults to on once you enable it except for this one... but that did resolve it for me.

davehob · 3 months ago

For whatever reason, I don't have a toggle button

[image: image.png]

On Thu, Apr 9, 2026 at 9:54 AM zbeekman @.***> wrote:

zbeekman left a comment (anthropics/claude-code#30457) <https://github.com/anthropics/claude-code/issues/30457#issuecomment-4215997732> toggling it in the chat fixed this for me. I don't know why every other integration defaults to on once you enable it except for this one... but that did resolve it for me. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/30457#issuecomment-4215997732>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS5N5GVSJ4C3DT6ZX6EP3L4U7IWBAVCNFSM6AAAAACWFWJQ2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMJVHE4TONZTGI> . You are receiving this because you commented.Message ID: @.***>
davehob · 3 months ago

for whatever reason I don't have a toggle button

[image: image.png]

On Thu, Apr 9, 2026 at 8:01 AM cbroster02 @.***> wrote:

cbroster02 left a comment (anthropics/claude-code#30457) <https://github.com/anthropics/claude-code/issues/30457#issuecomment-4215239422> make sure to toggle the connector within the chat itself, i had the same issue where drive was connected but needed toggling within the chat connectors image.png (view on web) <https://github.com/user-attachments/assets/0cb192a5-00dc-440d-b46a-e4c76d609e7c> — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/30457#issuecomment-4215239422>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS5N5EIVLZURYEQYA7FJGT4U63LPAVCNFSM6AAAAACWFWJQ2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMJVGIZTSNBSGI> . You are receiving this because you commented.Message ID: @.***>
jonwong514 · 3 months ago

same issue here as well. not sure how to toggle.

paxie001 · 3 months ago

same issue...

fugalh · 3 months ago

I'm hitting this too. I have the pro plan. Claude Desktop version 1.1617.0 (8d6345). Claude tells me it sees an empty tools list for the connector.

I attempted to disconnect from the gdrive connector (within Cowork UI) and got an error "Missing permissions: library:manage required".

Claude suggests:

What it might mean: library:manage doesn't match any standard Google Drive OAuth scope, which makes me think it's an internal Cowork/connector permission — something the connector backend needs to grant itself during setup, not something you can grant from your Google account. If that internal permission isn't being set correctly when the connector initializes, it could explain both the disconnection error you saw and the tools: [] state we are seeing.
JimmyJones33 · 3 months ago

I tried an incognito browser login. I was able to reconnect G-Drive. I then cleared my cache/cookies covering the time since I started encountering this problem. I logged into the desktop version and the G-Drive connection is still there and operational.

chadsten · 3 months ago

<img width="515" height="424" alt="Image" src="https://github.com/user-attachments/assets/50f969ca-8259-4ec5-8214-9ab84307a1fb" />

This fixed it, and Claude didn't catch it from the comments in this issue. Hopefully this helps!

wmccomis · 3 months ago

This did it for me

JorikSchellekens · 3 months ago

Same issue, missing the second tool to open files. Search works

godlevski · 2 months ago

WHAT WORKED FOR ME:

after connecting google drive, in the chat click "+" button > connectors > google drive and flip the switch to on ... 😅

cameron-bales-telus-health · 2 months ago

Confirming this is resolved as of today (May 12, 2026). A Cowork session on macOS now exposes 8 Drive tools under a dedicated MCP server (search_files, read_file_content, download_file_content, list_recent_files, create_file, copy_file, get_file_metadata, get_file_permissions). Called list_recent_files and got back real Drive metadata for my recent docs. Looks like the Drive→MCP migration shipped. Thanks!