anthropics / anthropics/knowledge-work-plugins

gmail_read_message does not return CC/BCC headers

未关闭
#139 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
24k
派生
2.9k
平均合并
1 天 16 小时
30 天内合并 PR
149

描述

**Description**

The `gmail_read_message` tool only returns four headers: From, To, Subject, and Date. The Cc and Bcc fields are omitted from the response, even when present on the original message.

**Impact**

Without CC/BCC headers, it's impossible to:
- Know who else is on a conversation
- Construct a proper Reply All
- Avoid accidentally excluding participants from a thread

This affects any workflow where multiple recipients are involved — which is most professional email.

**Steps to reproduce**

1. Receive an email where the sender has CC'd one or more recipients
2. Use `gmail_read_message` to read the message
3. Observe that the returned headers object contains only From, To, Subject, and Date
4. The CC'd addresses are not available anywhere in the response

**Expected behavior**

The headers object should include Cc (and ideally Bcc where available) so that reply drafts can be composed with the correct recipient list.

**Additional context**

The Gmail API itself returns these headers — they appear to be filtered out by the connector before the response is returned. Related: https://github.com/anthropics/claude-code/issues/28575 (another Gmail connector gap around draft attachments and sending).

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。