Repository navigation
feat: The grouped list_tasks answer adds open boards, unlisted boards, personal tasks and a summary EXO-94360 - #739
Merged
bmestrallet merged 2 commits intoNov 16, 2026
Conversation
Contributor
Author
Self-review close-out — 8472babDelivery checks before each round; reviewer round 1, then a closing round with a fresh reviewer, whose findings were fixed and confirmed clean by the same reviewer; one test gap found by the mutation run, fixed and confirmed.
Verified conform.
Classification (computed on |
bmestrallet
force-pushed
the
feat/EXO-94360-grouped-list-tasks-summary
branch
from
November 15, 2026 18:13
8472bab to
8c104a9
Compare
Contributor
Author
…EXO-94377 The tool paged through every task of the project and returned each one with its change log and comments of the period, so one answer for a large project reached about a megabyte. It now returns at most 20 tasks in all: the ones updated in the period, the most recently active first, then as many older uncompleted ones as there is room for. has_more says that the project holds more such tasks; uncompleted_count gives its uncompleted tasks. Only the tasks returned are read in full. The period still starts at midnight of the user's day, in the user's zone. The description changes, so the upgrades file lists the tool's one earlier definition, the only one any ref ever shipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, personal tasks and a summary EXO-94360 - group_by_project also returns open_project_count (the boards holding open tasks the user can access), projects_not_listed (the boards past the list's cap), personal_count (the selected tasks on no board) and summary, one sentence naming the filters the call applied, such as « 260 overdue open tasks in 29 of 86 boards ». It says « open », and counts the boards « of » the open boards, only when the listing selects open tasks only: overdue_only, or hide_completed_tasks without completed_since. - The open tasks are counted once on every board the user can access: that count gives open_project_count, and the listed boards read their open_count from it, instead of a second count on the listed boards. - has_more: a grouped call with limit 1, made for the counts, returns at most one task, with has_more false and no next_offset. A grouped call reading a real page keeps has_more and next_offset, since list_tasks also serves agents and MCP clients that read the page and the counts in one call. A grouped shape without a has_more key would break those callers' paging. - The list_tasks description names the new fields, says to answer from them about the call's own filters, and states the limit-1 rule for grouped calls. Its shipped definition joins the upgrades list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bmestrallet
force-pushed
the
feat/EXO-94360-grouped-list-tasks-summary
branch
from
November 16, 2026 06:27
8c104a9 to
739444d
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Why. In evaluation runs, asked how many tasks are late across their boards, the assistant called the grouped
list_tasksonce, then kept paging or calling it board by board: the grouped answer saidhas_moretrue whenever more tasks matched than the page held, and gave no ready figure to answer with, so the assistant either looped or wrote its own totals.How.
group_by_project) also returns:open_project_count: the boards the user can access that hold open tasks;projects_not_listed: the boards past the 100-board cap ofprojects;personal_count: the selected tasks on no board;summary: one sentence built from those counts and naming the filters the call applied, such as « 260 overdue open tasks in 29 of 86 boards ».overdue_only, orhide_completed_taskswithoutcompleted_since.open_project_countand each listed board'sopen_count, so a grouped call still runs two grouped counts.limit1, made for the counts, returnshas_morefalse and nonext_offset. A grouped call reading a real page keeps both, sincelist_tasksalso serves other agents and MCP clients that read the page and the counts in one call.list_tasksdescription names the new fields and tells the model to answer from them about the call's own filters, never reusing a summary for another question. Its earlier definition joinsai-tool-definition-upgrades.json, pinned in the upgrades test.Stacked on #738. Part of EXO-94360 with a Meeds-io/ai change whose Tasks agent reads
projects_not_listed: this PR lands before it or with it, never after.Knowledge: pending — EXO-94360
Classification: N2: a changed definition of an existing read-only MCP tool on a list endpoint (description and parameter text; no
require_approvalor annotations change), output fields added; no REST, DAO, schema or ACL change. Its approver must be an Architect or Developer who knows it is N2.🤖 Generated with Claude Code