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
Add usable pagination to Business Profile accounts #214
This issue was generated by AI for maintainer triage.
Idea
Let business-profile accounts list accept page size and page token options, forward them to the API, and expose a usable continuation token consistently.
Evidence
The accounts list command has no pagination fields and performs an unparameterized list request. It includes nextPageToken in JSON and prints the shared next-page hint in human mode, but the suggested --page option is not accepted. There is also no way to control the API page size.
Why it matters
Operators managing many Business Profile accounts can retrieve only the first response page and are given an unusable recovery instruction.
Initial acceptance checks
The command accepts bounded --max and --page values and forwards them to the account-management API.
The emitted token or hint successfully retrieves the following page without changing existing row schemas.
Scope boundaries
Do not add location pagination or automatic aggregation to this issue.
Category: bug Summary: Add usable page-size and continuation controls to Business Profile account listing.
Current behavior: business-profile accounts list performs one unparameterized account-management list request. JSON exposes nextPageToken and human output recommends --page, but the command accepts neither a page token nor a page-size control. The source and historical snapshots contain no implementation or duplicate.
Desired behavior:
Account listing should accept bounded page-size and continuation-token inputs, forward them to the provider request, and preserve the existing account row and JSON payload shapes while making the emitted token usable.
Key interfaces:
BusinessProfileAccountsListCmd — expose page-size and continuation inputs consistent with other list commands.
The Business Profile account list request — receive the validated pagination values.
The shared next-page hint contract — emit an accepted continuation option.
Acceptance criteria:
A supplied page size is validated and forwarded to the account-management API.
A supplied continuation token is forwarded and retrieves the following response page.
A returned continuation hint can be copied into a valid next invocation.
Existing JSON account data, nextPageToken, plain rows, and human rows remain compatible.
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.
Activity
itsjeremyjohnson commentedon Aug 16, 2026
Agent Brief
Category: bug
Summary: Add usable page-size and continuation controls to Business Profile account listing.
Current behavior:
business-profile accounts listperforms one unparameterized account-management list request. JSON exposesnextPageTokenand human output recommends--page, but the command accepts neither a page token nor a page-size control. The source and historical snapshots contain no implementation or duplicate.Desired behavior:
Account listing should accept bounded page-size and continuation-token inputs, forward them to the provider request, and preserve the existing account row and JSON payload shapes while making the emitted token usable.
Key interfaces:
BusinessProfileAccountsListCmd— expose page-size and continuation inputs consistent with other list commands.Acceptance criteria:
nextPageToken, plain rows, and human rows remain compatible.Out of scope:
itsjeremyjohnson commentedon Oct 12, 2026
Closing as obsolete (GitHub sweep 2026-10-12). This issue describes behavior of the
gogCLI command layer. The CLI was removed from this repository in 91336b7 (#269, "refactor(mcp): retire CLI distribution and rewrite server docs"), which deletedcmd/gogand all ofinternal/cmd;mainnow builds onlygog-mcp, and none of the symbols this issue names exist onmain(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 agog-mcpoperation, please file it against the MCP surface.