Skip to content

[upstream-adapt] Report Drive folder size, inventory, and tree layout #164

Closed

Description

@itsjeremyjohnson

Outcome

Users can inspect folder trees, inventory contents, and size rollups for planning cleanup and migrations.

Why

Upstream du/inventory/tree-style reporting fills an everyday gap.

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

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

Performance bounds and shared-drive behavior are triage details.

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

    Drive can list/search individual resources, but it does not calculate recursive folder rollups or render folder trees. No closed issue, merged pull request, or local rejected-request record covers this outcome.

    This request currently combines three potentially different products—tree display, inventory export, and recursive size accounting—and leaves shortcuts, Google-native files, multiple parents, shared drives, inaccessible descendants, pagination, and performance limits undecided. Those choices materially change both accuracy and output contracts.

    Recommendation: keep needs-triage and either select one bounded first workflow or define shared traversal and size semantics before delegation.

  3. itsjeremyjohnson commented on Aug 13, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive currently lists one folder page and returns provider file metadata, but it does not recursively traverse folder trees, render a hierarchy, produce a complete inventory, or calculate size rollups. The historical issue and PR records contain no duplicate, and no prior-rejection record exists.

    This candidate combines three separable workflows—tree display, inventory export, and recursive size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, multiple parents, inaccessible descendants, pagination, cycles or repeated resources, and performance or completeness limits.

    Recommendation: retain needs-triage and choose one bounded first workflow or define shared traversal and size semantics before delegation.

  4. itsjeremyjohnson commented on Aug 14, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder page and return provider file metadata, including byte size where Google supplies it. It does not recursively traverse folders, render hierarchy, emit a complete inventory, or calculate recursive size rollups.

    The source snapshot and historical issue and PR records contain no duplicate implementation, and no prior-rejection record exists.

    This candidate combines three separable workflows: tree display, inventory export, and size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits.

    Recommendation: retain needs-triage and choose one bounded initial workflow or define shared traversal and size semantics before delegation.

  5. itsjeremyjohnson commented on Aug 15, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder page and return provider metadata, including byte size when Google supplies it. It does not recursively traverse folders, render a hierarchy, emit a complete inventory, or calculate recursive size rollups. No equivalent implementation or prior-rejection record was found.

    This issue combines three separable workflows: tree display, inventory export, and size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits.

    Recommendation: retain needs-triage and either select one bounded initial workflow or define shared traversal and size semantics before delegation.

  6. itsjeremyjohnson commented on Aug 16, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder page and return provider metadata, including byte size when Google supplies it. It does not recursively traverse folders, render a hierarchy, emit a complete inventory, or calculate recursive size rollups. The source and historical snapshots contain no equivalent implementation, and there is no prior-rejection record.

    This issue combines three separable workflows: tree display, inventory export, and size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until a bounded initial workflow or shared traversal and size semantics are selected.

  7. itsjeremyjohnson commented on Aug 17, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder page and return provider metadata, including byte size when Google supplies it. It does not recursively traverse folders, render a hierarchy, emit a complete inventory, or calculate recursive size rollups. The supplied source and historical snapshots contain no equivalent implementation, and there is no prior-rejection record.

    This issue combines three separable workflows: tree display, inventory export, and size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until a bounded initial workflow or shared traversal and size semantics are selected.

  8. itsjeremyjohnson commented on Aug 20, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder page and return provider metadata, including byte size when Google supplies it. It does not recursively traverse folders, render hierarchy, emit a complete inventory, or calculate recursive size rollups. The current source and supplied historical snapshots contain no equivalent implementation, and there is no prior-rejection record.

    This issue combines three separable workflows: tree display, inventory export, and size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until a bounded initial workflow or shared traversal and size semantics are selected.

  9. itsjeremyjohnson commented on Aug 21, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list a folder page and return provider metadata, including byte size when Google supplies it. It does not recursively traverse folders, render hierarchy, emit a complete inventory, or calculate recursive size rollups. Searches across the Drive surface and supplied closed-issue and merged-PR histories found no equivalent workflow or duplicate; no prior-rejection record exists.

    This issue combines three separable workflows: tree display, inventory export, and size accounting. A durable contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until a bounded initial workflow or shared traversal and size semantics are selected.

  10. itsjeremyjohnson commented on Aug 23, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder page and return provider metadata, including byte size when supplied. It does not recursively render hierarchy, emit a complete inventory, or calculate recursive size rollups. Searches of the Drive surface and supplied histories found no equivalent workflow or duplicate, and there is no prior-rejection record.

    This candidate combines three separable workflows: tree display, inventory export, and size accounting. A durable first contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until a bounded initial workflow and its traversal and size semantics are selected.

  11. itsjeremyjohnson commented on Aug 23, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list folder contents and return provider metadata, including byte size when supplied. It does not recursively render hierarchy, emit a complete inventory, or calculate recursive size rollups. Searches of the Drive surface and supplied histories found no equivalent workflow or duplicate, and there is no prior-rejection record.

    This candidate combines three separable workflows: tree display, inventory export, and size accounting. A durable first contract needs decisions for shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until a bounded initial workflow and its traversal and size semantics are selected.

  12. itsjeremyjohnson commented on Aug 24, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder's contents and return provider metadata, including byte size when supplied. It does not recursively render hierarchy, emit a complete inventory, or calculate recursive size rollups. Searches of Drive listing, metadata, and shared-drive concepts and the supplied closed-issue and merged-PR histories found no equivalent workflow or duplicate; no prior-rejection record exists.

    This candidate combines three separable workflows: tree display, inventory export, and size accounting. A maintainer must choose a bounded first workflow and decide how it handles shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Keep this in needs-triage until that contract is selected.

  13. itsjeremyjohnson commented on Aug 25, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Triage Notes

    Drive can list one folder's contents and return provider metadata, including byte size when supplied. It does not recursively render hierarchy, emit a complete inventory, or calculate recursive size rollups. Concept searches of Drive listing, metadata, and shared-drive behavior and the supplied histories found no equivalent workflow or duplicate, and there is no prior-rejection record.

    This candidate combines three separable workflows: tree display, inventory export, and size accounting. A maintainer must choose a bounded first workflow and decide how it handles shortcuts, Google-native files without byte sizes, shared drives, repeated or multiply parented resources, inaccessible descendants, pagination, cycle protection, and performance or completeness limits. Retain needs-triage until that contract is selected.

  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 inspect folder trees, inventory contents, and size rollups for planning cleanup and migrations.

    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 inspect folder trees, inventory contents, and size rollups for planning cleanup and migrations.

    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

    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) (drive.files.list) 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-humanRequires human implementationupstream-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