Repository navigation
fix(cli): report all matching tasks in task_list total, not just the limited page - #4324
Merged
Merged
Conversation
Merged
meefs
pushed a commit
to meefs/claude-code-flow
that referenced
this pull request
Oct 20, 2026
Minor release (new backward-compatible flags: Grok Build CLI host surface ruvnet#3512, memory list/search tag filter ruvnet#3526) bundled with a round of correctness fixes merged since 3.58.1: memory delete-sync (ruvnet#4138), real AgentDB HNSWIndex replacing the dead getController('hnsw') path with safe exact-search fallback (ruvnet#4249/ruvnet#4322), harness live-process reporting (ruvnet#3521), RaBitQ on-demand index build (ruvnet#4318/ruvnet#4319), metaharness ADR-152 cost-dimension and verdict-band fix (ruvnet#3520), swarm idle-agent heartbeat false-positive (ruvnet#4320), ephemeral-agent termination idempotency (ruvnet#4323), status/task_list field-mapping and total-count fixes (ruvnet#4321/ruvnet#4324). Also fixes the actual cause of broken images/links on npmjs.com/package/ruflo: `ruflo/package.json`'s `repository.directory: "ruflo"` field added an extra path layer on top of the README content (the root README.md, copied in verbatim by `prepublishOnly` at publish time, which is already written with repo-root-relative paths) — every relative image/link resolved to e.g. `raw/main/ruflo/ruflo/assets/...` instead of `raw/main/ruflo/assets/...`. Removed the `directory` field to match claude-flow's own (directory-less) repository entry. A prior PR (ruvnet#4325) fixed `ruflo/README.md`'s own relative paths for anyone browsing that file directly on GitHub, but that file is overwritten by the root README at publish time and was never the actual npm-rendered content. Published to npm: @claude-flow/[email protected], [email protected], [email protected], and standalone @claude-flow/[email protected] (the ruvnet#4249 fix — not part of the 3-package train, published separately per its own leaf's npm presence). All three umbrella packages' latest/alpha/v3alpha dist-tags verified pointing at 3.59.0. Co-Authored-By: RuFlo <[email protected]>
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.
Summary
task_listsetstotalafter applyinglimit, sototalalways equals the number of returned tasks.ruflo task listthen printsShowing 20 of 20 taskseven when 50 tasks match, and MCP callers can't tell that the list was truncated.Change
mcp-tools/task-tools.ts: count the filtered tasks beforeslice(0, limit)and return that astotal. The returnedtasksarray and the filters are unchanged.Tests
New
__tests__/task-list-total.test.ts(tempCLAUDE_FLOW_CWD, 4 tasks):limit: 2returns 2 tasks withtotal: 4type: 'feature', limit: 1returns 1 task withtotal: 3(filters still apply to the count)totalequals the number of returned tasksBefore the fix, the first two fail (
totalis 2 and 1); after it, all pass.__tests__/mcp-tools-deep.test.tsstill passes.This is separate from #4321 (
status taskswithstatus: 'all') and doesn't depend on it.This change was prepared with AI assistance; I reviewed the diff and verified it by running the tests above.