When creating Gmail drafts with attachments whose filenames contain
non-ASCII characters (e.g. umlauts like ü, ö, ä), Gmail displays
"noname" instead of the actual filename.
The root cause is that Content-Disposition was built via string
formatting (f'attachment; filename="{safe_filename}"'), which embeds
raw non-ASCII bytes in the header. Gmail cannot parse these and falls
back to "noname".
Fix: pass the filename as a keyword argument to add_header(), which
makes Python's email library automatically apply RFC 2231 encoding
(filename*=utf-8''...) for non-ASCII names while keeping ASCII
filenames unchanged.
Fixes#500
Fixes#494 - Windows attachment corruption for PNG/PDF files.
On Windows, os.open() defaults to text mode, which translates LF (0x0a)
bytes to CRLF (0x0d 0x0a) during os.write(). This corrupts any binary
attachment containing 0x0a bytes (PNG headers, PDFs, etc.).
The fix adds os.O_BINARY to the os.open() flags using the standard
getattr(os, 'O_BINARY', 0) idiom, which returns the flag on Windows
and 0 (no-op) on platforms where it doesn't exist.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Address CodeRabbit review feedback:
- Extract doc ID from full Google Docs URLs (e.g. /d/<id>/)
- Validate comment_mode against allowed values
- Escape pipe characters in table cell text
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds a new `get_doc_as_markdown` tool that converts Google Docs to clean
Markdown preserving formatting (headings, bold/italic/strikethrough, links,
code spans, ordered/unordered lists with nesting, and tables).
Optionally overlays comments with their anchor text (quotedFileContent) —
the specific text each comment is attached to — in two modes:
- inline: footnote-style references placed at the anchor text location
- appendix: all comments grouped at the bottom with blockquoted anchors
This gives AI agents full document context in a single tool call, unlike
get_doc_content which strips all formatting to plain text.
New files:
- gdocs/docs_markdown.py: Converter + comment formatting logic
- tests/gdocs/test_docs_markdown.py: 18 tests
Tool tier: extended (alongside search_docs, export_doc_to_pdf, etc.)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When reading comments via read_document_comments / read_spreadsheet_comments /
read_presentation_comments, the Drive API's quotedFileContent.value field is
now requested and displayed as "Quoted text:" in the output. This shows which
specific text in the document each comment is anchored to.
Comments without anchor text (document-level comments) omit the line.
Relates to #210
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Previously, get_messages and search_messages completely ignored the
attachment field on Chat API messages. This adds:
- Attachment metadata (filename, type) displayed inline in get_messages
and search_messages output
- New download_chat_attachment tool that downloads attachments via the
Chat API media endpoint and saves to local disk
The download uses httpx with a Bearer token against the
chat.googleapis.com/v1/media endpoint (with alt=media), which works
correctly in both OAuth 2.0 and OAuth 2.1 modes. The attachment's
downloadUri field is intentionally ignored as it points to
chat.google.com which requires browser session cookies.
Key details:
- Uses attachmentDataRef.resourceName for the media endpoint URL
- No new OAuth scopes required (existing chat_read is sufficient)
- Tool registered in the extended tier
- 10 unit tests covering metadata display, download, and edge cases
The list_spaces tool was using chat.messages.readonly which is overly
broad for simply enumerating available spaces. This adds the
chat.spaces.readonly scope and uses it for list_spaces, following the
principle of least privilege.
Closes#479
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Resolves several gaps in the Google Chat tools:
**Sender resolution via People API:**
- Chat API doesn't return displayName for service account access
- New `_resolve_sender()` uses People API to look up user IDs
- In-memory cache avoids repeated lookups
- get_messages and search_messages now use `require_multiple_services`
to inject both chat and people services
**Rich link (smart chip) extraction:**
- When users paste Workspace URLs that render as smart chips, the URL
is stripped from the `text` field and only available in annotations
- New `_extract_rich_links()` extracts RICH_LINK annotation URIs
- Surfaced as `[linked: <url>]` in get_messages and search_messages
**Thread support:**
- get_messages shows `[thread: ...]` for threaded replies
- send_message gains `thread_name` param for replying in existing threads
using `messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD`
- Fixes existing `thread_key` param which was missing messageReplyOption
**Emoji reactions:**
- get_messages shows `[reactions: 👍x3, 🎉x1]` from emojiReactionSummaries
- New `create_reaction` tool to add emoji reactions to messages
