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] Access Google Photos library workflows #196
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Activity
itsjeremyjohnson commentedon Aug 12, 2026
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-triageuntil the maintainer identifies the concrete media workflow, selected API, read/write boundary, and whether partial/user-selected access satisfies the product goal.itsjeremyjohnson commentedon Aug 13, 2026
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-triageuntil a maintainer identifies the concrete media workflow, selected API, read/write boundary, required completeness, and acceptable handling of expiring or user-selected media access.itsjeremyjohnson commentedon Aug 14, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 15, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 16, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 17, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 18, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 20, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 21, 2026
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
photosspace 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-triageuntil those product and API-boundary choices are made.itsjeremyjohnson commentedon Aug 23, 2026
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
photosspace 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-triageuntil those choices are made.itsjeremyjohnson commentedon Aug 24, 2026
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
photosspace 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-triageuntil those choices are made.itsjeremyjohnson commentedon Aug 25, 2026
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
photosspace 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-triageuntil those choices are made.itsjeremyjohnson commentedon Sep 15, 2026
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:
Acceptance criteria:
Out of scope:
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-agentorwontfix.Prior triage notes remain the technical baseline; this comment only advances state out of
needs-triage.itsjeremyjohnson commentedon Oct 12, 2026
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.jsonhas no Photos Library or Picker API). The original request targeted the retired CLI (91336b7, #269) and leaves the workflow undefined. Leaving open withsweep:deferred.