Skip to content

Add continuation tokens to YouTube channel listing #215

Closed

Description

@itsjeremyjohnson

This issue was generated by AI for maintainer triage.

Idea

Add a page-token option to the YouTube channels command and forward it to the Channels list request for both mine and explicit-ID queries.

Evidence

The channels command accepts a maximum result count but no page token. It emits the API's next-page token in JSON and prints a continuation hint using --page, even though that flag is unavailable and the request never sets a page token.

Why it matters

Users cannot enumerate channel results beyond the first page, and following the CLI's own continuation guidance produces an argument error.

Initial acceptance checks

  • youtube channels --page TOKEN sends TOKEN on the API request and returns the expected subsequent page.
  • Existing maximum-result behavior and JSON continuation-token output remain compatible.

Scope boundaries

  • Do not expand playlist, subscription, or channel-management capabilities.

Activity

  1. itsjeremyjohnson commented on Aug 16, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: bug
    Summary: Make YouTube channel-list continuation tokens usable.

    Current behavior:
    The YouTube channels command accepts a maximum result count and exposes nextPageToken, but it has no continuation-token input and never sets a page token on the Channels list request. Its human hint recommends an unavailable --page option. The gap exists for both authenticated-user and explicit-ID queries and has no historical duplicate.

    Desired behavior:
    Channel listing should accept a continuation token and forward it for either query form. The emitted continuation hint must use the accepted option, while existing maximum-result and output contracts remain unchanged.

    Key interfaces:

    • YoutubeChannelsCmd — accept a continuation token.
    • The Channels list request — receive the token alongside mine or ID selection and the existing result limit.

    Acceptance criteria:

    • A supplied continuation token is sent for authenticated-user channel queries.
    • A supplied continuation token is sent for explicit-ID channel queries.
    • The human continuation hint is a valid next invocation.
    • Existing maximum-result behavior and JSON nextPageToken output remain compatible.
    • Tests cover both query forms and omission of the token on the first page.

    Out of scope:

    • Playlist, subscription, or channel-management capabilities.
    • Automatic aggregation of all pages.
  2. added
    ready-for-agentFully specified and ready for an agent
    and removed
    needs-triageMaintainer needs to evaluate this issue
    on Aug 16, 2026
  3. itsjeremyjohnson commented on Oct 12, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    Closing as obsolete (GitHub sweep 2026-10-12). This issue describes behavior of the gog CLI command layer. The CLI was removed from this repository in 91336b7 (#269, "refactor(mcp): retire CLI distribution and rewrite server docs"), which deleted cmd/gog and all of internal/cmd; main now builds only gog-mcp, and none of the symbols this issue names exist on main (checked at bf17220). There is no code path left to fix here. A fix to the installed v0.10.0 binary would mean restoring the CLI, which is a separate decision. If the same gap appears in a gog-mcp operation, please file it against the MCP surface.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions