You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[upstream-adapt] Create draft-only Gmail reply, reply-all, and forward without sending #170
Category: enhancement Summary: Create reply, reply-all, and forward Gmail drafts without sending
Current behavior:
Draft creation can manually set recipients, subject, body, attachments, From, and a reply-to message ID for threading. The caller must derive reply/reply-all recipients and forward content itself, and the high-level send workflow is separate from draft creation.
Desired behavior:
Provide draft-only reply, reply-all, and forward workflows based on an existing Gmail message. Reply modes should derive recipients and thread headers using the same mail semantics as sending, excluding the account's own addresses as appropriate. Forward should preserve useful source context and allow the caller to add body text and attachments. These workflows must create a draft and never invoke message send.
Closing as obsolete (GitHub sweep 2026-10-12). This [upstream-adapt] request asked to port an upstream steipete/gogcli CLI feature into our gog CLI. That CLI was retired in 91336b7 (#269); main builds only gog-mcp, so the command surface this request targets no longer exists. gog-mcp's pinned API catalog (internal/googlecatalog/manifest.json) already exposes the underlying Google method(s) (gmail.users.drafts.create) through --discovery=compact --api-catalog, subject to grants. New needs on the MCP side are filed as MCP-scoped issues (see #271, #273, #274, #278).
Activity
itsjeremyjohnson commentedon Aug 12, 2026
Agent Brief
Category: enhancement
Summary: Create reply, reply-all, and forward Gmail drafts without sending
Current behavior:
Draft creation can manually set recipients, subject, body, attachments, From, and a reply-to message ID for threading. The caller must derive reply/reply-all recipients and forward content itself, and the high-level send workflow is separate from draft creation.
Desired behavior:
Provide draft-only reply, reply-all, and forward workflows based on an existing Gmail message. Reply modes should derive recipients and thread headers using the same mail semantics as sending, excluding the account's own addresses as appropriate. Forward should preserve useful source context and allow the caller to add body text and attachments. These workflows must create a draft and never invoke message send.
Key interfaces:
Acceptance criteria:
Out of scope:
itsjeremyjohnson commentedon Oct 12, 2026
Closing as obsolete (GitHub sweep 2026-10-12). This [upstream-adapt] request asked to port an upstream steipete/gogcli CLI feature into our
gogCLI. That CLI was retired in 91336b7 (#269);mainbuilds onlygog-mcp, so the command surface this request targets no longer exists.gog-mcp's pinned API catalog (internal/googlecatalog/manifest.json) already exposes the underlying Google method(s) (gmail.users.drafts.create) through--discovery=compact --api-catalog, subject to grants. New needs on the MCP side are filed as MCP-scoped issues (see #271, #273, #274, #278).