Skip to content

Expose continuation for Calendar search results #222

Closed

Description

@itsjeremyjohnson

This issue was generated by AI for maintainer triage.

Idea

Add page-token support to Calendar event search and return the API continuation token in structured output with a usable human-mode hint.

Evidence

Calendar search issues one Events list request with a configurable maximum result count. It does not accept or send a page token, and its JSON result contains events and the query but not the API's next-page token. Text output likewise provides no continuation hint.

Why it matters

Broad searches can silently stop after the first API page, so users and scripts may interpret an incomplete result set as complete.

Initial acceptance checks

  • Search accepts --page, sends it to the Events list request, and exposes any returned next-page token.
  • Human output identifies when another page exists without adding diagnostics to JSON stdout.

Scope boundaries

  • Do not add automatic all-calendar search or change query/time-range semantics.

Activity

  1. itsjeremyjohnson commented on Aug 16, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: bug
    Summary: Expose usable continuation tokens for Calendar event search.

    Current behavior:
    Calendar search performs one Events list request with a configurable maximum but accepts and sends no page token. Its JSON result contains events and the query without nextPageToken, and text output provides no continuation hint. The source and historical snapshots contain no equivalent implementation.

    Desired behavior:
    Search should accept a continuation token, send it to the same Events list query, expose the returned token in structured output, and provide a usable human-mode hint on stderr. Search filters, time range, ordering, and existing event schemas must remain stable.

    Key interfaces:

    • CalendarSearchCmd — accept a continuation token.
    • The Calendar Events list request — receive that token alongside the existing query and time range.
    • The structured search envelope — add nextPageToken without changing the event projection.

    Acceptance criteria:

    • A supplied token is sent as the Events list page token.
    • JSON includes the provider’s returned nextPageToken while preserving events and query.
    • Human mode emits a copyable next-page hint on stderr when another page exists.
    • No continuation diagnostic is written to JSON stdout.
    • Tests cover first page, continued page, empty token, and returned-token output.

    Out of scope:

    • Automatic all-calendar search.
    • Query or time-range semantic changes.
  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