Skip to content

[upstream-adapt] Create draft-only Gmail reply, reply-all, and forward without sending #170

Closed

Description

@itsjeremyjohnson

Outcome

Users and agents can prepare reply, reply-all, and forward drafts with correct threading and recipients, without sending mail.

Why

Critical agent workflow: draft first, human or later step sends. Upstream draft-only compose is the target outcome.

Context

  • Source: upstream feature review of openclaw/gogcli (2026-08-11)
  • Intake rule: adapt the outcome in our architecture — do not cherry-pick or copy upstream implementation
  • Suggested triage priority: P1
  • Area: Gmail

Non-goals for this issue

  • No prescribed flags, package layout, or upstream file ports
  • No requirement to match upstream UX naming
  • Implementation design happens during triage / agent brief

Notes for triage

Must honor no-send / policy constraints.

Acceptance (triage will refine)

  • Desired user/agent-visible outcome is clear and still wanted
  • Not already fully covered by current main
  • Scope is bounded enough for an agent brief (or split)
  • Priority confirmed or re-bucketed

Activity

  1. added
    enhancementNew feature or request
    needs-triageMaintainer needs to evaluate this issue
    upstream-adaptFeature adapted from upstream openclaw/gogcli (rebuild our way)
    on Aug 11, 2026
  2. itsjeremyjohnson commented on Aug 12, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    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:

    • Existing-message reply metadata — derive thread, references, subject, and recipient sets
    • Draft composition — create a Gmail draft using the shared MIME composition behavior
    • Send-as identities and command policy — honor explicit sender choice and any no-send policy independently of draft creation

    Acceptance criteria:

    • Reply creates a draft addressed to the correct reply target in the original thread
    • Reply-all includes original To/Cc participants without duplicating the user's own recognized addresses
    • Forward creates an unthreaded forward draft with source context and caller-supplied recipients
    • Draft-only operations never call the Gmail send endpoint
    • Attachments and plain/HTML bodies follow existing composition behavior
    • JSON and plain output return stable draft, message, and thread identities
    • Tests cover Reply-To, reply-all deduplication, forward, aliases, and the no-send guarantee

    Out of scope:

    • Automatically sending the created draft
    • Scheduling delivery
    • Changing existing explicit-recipient draft creation
  3. added
    ready-for-agentFully specified and ready for an agent
    and removed
    needs-triageMaintainer needs to evaluate this issue
    on Aug 12, 2026
  4. itsjeremyjohnson commented on Oct 12, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an agentupstream-adaptFeature adapted from upstream openclaw/gogcli (rebuild our way)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions