Skip to content

[upstream-adapt] Export contacts as vCard #186

Closed

Description

@itsjeremyjohnson

Outcome

Users can export contacts (by resource, search, or all) to vCard for backup and migration.

Why

Standard interchange format; upstream contacts export.

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: Contacts

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

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: Export individual, searched, or all Google contacts as standards-compliant vCard

    Current behavior:
    Contacts can be listed, searched, fetched, created, updated, deleted, grouped, and batch-managed. Output is API JSON or gog's text/plain formats; no contact interchange artifact is available.

    Desired behavior:
    Export one resource, search results, or all paginated contacts as a UTF-8 vCard stream suitable for common address-book importers. Map every supported People field with a defined vCard equivalent, escape and fold lines correctly, preserve multiple values and type labels, and report fields that cannot be represented rather than silently losing them.

    Key interfaces:

    • Contact selection — resource, search, and all-contact modes with complete pagination
    • People person fields — request the field set needed for the vCard mapping
    • vCard serializer — produce deterministic cards with correct escaping, line folding, and multi-value handling

    Acceptance criteria:

    • Resource, search, and all modes emit one valid card per selected contact
    • Names, emails, phones, addresses, organizations/titles, URLs, birthdays, notes, and supported custom fields map when present
    • Multiple values and their type labels are retained
    • Unicode, commas, semicolons, backslashes, and newlines round-trip through a standards-compliant parser
    • All-contact export follows pagination without duplicates or truncation
    • Unsupported populated fields produce a documented warning/error contract rather than silent loss

    Out of scope:

    • Importing vCard
    • Downloading contact photos into separate files
    • Merging duplicate contacts
  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) (people.people.connections.list / people.people.get) 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