claude-code - 💡(How to fix) Fix anthropics/claude-code/issues [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51994Fetched 2026-04-23 07:39:24
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Timeline (top)
commented ×1labeled ×1

Error Message

Error Messages/Logs

Code Example

threadId / In-Reply-To to create_draft". Body: describe the use case (drafts visible in correct thread in own Drafts view) + cite the Gmail API field.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Feature request: Gmail connector create_draft currently accepts only to / cc / bcc / subject / body / htmlBody. Please add optional threadId, inReplyTo, and references parameters so drafted replies land inside the target thread in my own Drafts view, matching Gmail API behaviour.

What Should Happen?

Feature request: Gmail connector create_draft currently accepts only to / cc / bcc / subject / body / htmlBody. Please add optional threadId, inReplyTo, and references parameters so drafted replies land inside the target thread in my own Drafts view, matching Gmail API behaviour.

Error Messages/Logs

threadId / In-Reply-To to create_draft". Body: describe the use case (drafts visible in correct thread in own Drafts view) + cite the Gmail API field.

Steps to Reproduce

threadId / In-Reply-To to create_draft". Body: describe the use case (drafts visible in correct thread in own Drafts view) + cite the Gmail API field.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

latest

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Add optional threadId, inReplyTo, and references parameters to the Gmail connector create_draft method to enable drafted replies to land inside the target thread.

Guidance

  • Review the Gmail API documentation to understand the usage of threadId, inReplyTo, and references fields in creating drafts.
  • Update the create_draft method to accept these optional parameters and pass them to the Gmail API.
  • Test the updated method with different scenarios to ensure drafted replies are correctly threaded in the user's Drafts view.
  • Verify that the updated method behaves as expected when these parameters are not provided, to maintain backward compatibility.

Example

No code example can be provided without knowing the exact implementation details of the create_draft method.

Notes

The fix relies on the Gmail API's behavior and the implementation of the create_draft method, which is not provided in the issue.

Recommendation

Apply workaround: Update the create_draft method to include the optional parameters, as this is a feature request to align with the Gmail API behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix anthropics/claude-code/issues [1 comments, 2 participants]