Anthropic removed the gmail_read_message capability from Claude's Gmail connector, breaking workflows that depended on the model reading incoming emails.
Users who built automations around Claude's email access - summarizing messages, triaging newsletters, extracting action items from threads - report those tasks now fail silently. The Gmail connector still appears in Claude's integrations list, but the specific action that allows it to read message content is gone.
Anthropiv hasn't published an explanation for the removal. That's the main frustration: the capability was live long enough for people to build real workflows around it, and it disappeared without a changelog entry or migration path. Gmail access sits in a sensitive category - reading email content raises data handling questions that vary by privacy regulation and region - so a compliance or policy review is the most plausible cause.
The practical workaround is to route email content through a third-party automation platform like Make or Zapier, which gives you explicit control over what gets passed to Claude and when. It requires more setup than the native connector, but it also means you're not dependent on first-party integrations staying stable.
No timeline exists from Anthropic on whether gmail_read_message returns in some form - possibly with tighter consent flows or clearer data handling disclosures. Any workflow that relied on Claude reading Gmail directly needs to be rebuilt around an alternative approach now.