Skip to content

[upstream-adapt] Access Google Photos library workflows #196

Open

Description

@itsjeremyjohnson

Outcome

Users can work with Google Photos library/picker style workflows from the CLI for backup and media automation.

Why

Upstream photos support; only if there is a real Robben workflow.

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: P3
  • Area: Photos

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

API/policy constraints may limit scope.

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.

    Triage Notes

    No Google Photos Library or Picker API service is present, and no historical issue or merged pull request implements Photos workflows. The request is novel but describes only "library/picker style workflows" and a conditional backup/media goal.

    Those APIs have materially different user-consent, selection-session, download-lifetime, upload, and policy constraints. "Backup" also implies completeness that a picker-style user selection may not provide. The local snapshot cannot establish the intended workflow or acceptable API limitations.

    Recommendation: retain needs-triage until the maintainer identifies the concrete media workflow, selected API, read/write boundary, and whether partial/user-selected access satisfies the product goal.

  3. itsjeremyjohnson commented on Aug 13, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The registered services contain no Google Photos Library or Picker API workflow. The only Drive “photos” occurrence is an ID-generation space, not Photos library access. Closed issues and merged pull requests contain no duplicate, and no prior rejection exists.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. The local snapshot cannot establish which workflow or limitation is acceptable.

    Recommendation: retain needs-triage until a maintainer identifies the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected media access.

  4. itsjeremyjohnson commented on Aug 14, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The registered commands, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive's support for generating IDs in a photos space is a Drive API operation, not Photos library access. Historical issue and merged-PR searches found no duplicate, and no prior-rejection record exists.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide.

    A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access before an implementation can be verified.

    Recommendation: retain needs-triage until those product and API-boundary choices are made.

  5. itsjeremyjohnson commented on Aug 15, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The registered commands, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive's support for generating IDs in a photos space is a Drive API operation, not Photos library access. Historical searches found no duplicate or prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access before implementation can be verified.

    Recommendation: retain needs-triage until those product and API-boundary choices are made.

  6. itsjeremyjohnson commented on Aug 16, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The registered commands, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive support for generating IDs in a photos space is a Drive API operation, not Photos library access. Historical searches found no duplicate or prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those product and API-boundary choices are made.

  7. itsjeremyjohnson commented on Aug 17, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The registered commands, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive support for generating IDs in a photos space is a Drive API operation, not Photos library access. The supplied historical snapshots contain no duplicate, and there is no prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those product and API-boundary choices are made.

  8. itsjeremyjohnson commented on Aug 18, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The registered commands, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive support for generating IDs in a photos space is a Drive API operation, not Photos library access. Historical searches found no duplicate, and there is no prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those product and API-boundary choices are made.

  9. itsjeremyjohnson commented on Aug 20, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The current command registry, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive support for generating IDs in a photos space is a Drive API operation, not Photos library access. The current source and supplied histories contain no duplicate, and there is no prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those product and API-boundary choices are made.

  10. itsjeremyjohnson commented on Aug 21, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The command registry, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive support for generating IDs in a photos space is a Drive API operation, not Photos library access. Searches of the supplied histories found no duplicate implementation; no prior-rejection record exists.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those product and API-boundary choices are made.

  11. itsjeremyjohnson commented on Aug 23, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The command registry, authentication catalog, and Google client layer contain no Google Photos Library or Picker workflow. Drive support for IDs in a photos space is a Drive API operation, not Photos library access. Searches of the supplied histories found no duplicate implementation, and there is no prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those choices are made.

  12. itsjeremyjohnson commented on Aug 24, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The default-branch command registry, authentication catalog, and Google API client layer contain no Google Photos Library or Picker workflow. Drive support for IDs in a photos space is a Drive API operation, not Photos library access. Searches of Photos concepts and the supplied closed-issue and merged-PR histories found no duplicate implementation; no prior-rejection record exists.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Keep this in needs-triage until those choices are made.

  13. itsjeremyjohnson commented on Aug 25, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    The default-branch command registry, authentication catalog, and Google API client layer contain no Google Photos Library or Picker workflow. Drive support for IDs in a photos space is a Drive API operation, not Photos library access. Concept searches of Photos behavior and the supplied histories found no duplicate implementation, and there is no prior-rejection record.

    Library and Picker workflows have different consent, selection-session, upload, download-lifetime, and API-policy constraints. The stated backup goal also implies coverage and durability guarantees that a user-selected picker session may not provide. A maintainer must identify the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected access. Retain needs-triage until those choices are made.

  14. added and removed
    needs-triageMaintainer needs to evaluate this issue
    on Sep 15, 2026
  15. itsjeremyjohnson commented on Sep 15, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: enhancement
    Summary: Users can work with Google Photos library/picker style workflows from the CLI for backup and media automation.

    Current behavior:
    Fork lacks this upstream-adapt capability (or only partial primitives exist). Prior triage notes on this issue document the current surface.

    Desired behavior:
    Users can work with Google Photos library/picker style workflows from the CLI for backup and media automation.

    Key interfaces:

    • Existing gog CLI command surface and auth/safety controls
    • Google API surface named in the issue outcome
    • Script-friendly machine-readable output consistent with sibling commands

    Acceptance criteria:

    • Outcome in the issue body is met under this fork’s architecture (adapt, do not cherry-pick upstream patches)
    • Behavior is covered by tests or documented manual verification
    • Safety/auth constraints match the rest of gog

    Out of scope:

    • Copying upstream implementation wholesale
    • Unrelated Google services

    Why not delegable

    Product priority and contract semantics are still open (what ships first, audit/lifecycle meaning, and whether this fork needs the capability at all). An agent should not invent those decisions. Once Jeremy ranks or rejects this upstream-adapt item, retarget to ready-for-agent or wontfix.

    Prior triage notes remain the technical baseline; this comment only advances state out of needs-triage.

  16. itsjeremyjohnson commented on Oct 12, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    Deferred by the GitHub sweep 2026-10-12: This asks for a Google service that gog-mcp's pinned catalog does not include yet (internal/googlecatalog/manifest.json has no Photos Library or Picker API). The original request targeted the retired CLI (91336b7, #269) and leaves the workflow undefined. Leaving open with sweep:deferred.

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-humanRequires human implementationsweep:deferredReal but large; deferred by the 2026-10-12 backlog sweepupstream-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