Skip to content

gtd.tasks silently clamps results to 200 rows — callers cannot distinguish a full result from a capped one #744

Description

@oceanwaves630

Verified live: gtd.tasks(limit=500) returns exactly 200 rows with no indication the requested limit was clamped. The cap itself is reasonable; the silence is the defect — callers building counts or boards from the returned array undercount without knowing it.

Ask (either, prefer the second):

  1. Document the cap in the verb's help/ParamDef description.
  2. Return a truncated: true and/or total_matching field when the server-side cap (or any internal scan limit) cuts the result, so a full result is distinguishable from a capped one.

Same audit lens applies to sibling list-shaped verbs (gtd.next, note list) — if they share the clamp, they share the fix.

Low priority; surfaced from downstream consumers computing task counts.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions