[Feature]: list_tasks

[davidarule]

Problem to solve

As progress occurs with the epics and tasks, comments add up. When the list_tasks call is returned, the response is large. My last call returned 222,689 characters which exceeds maximum allowed tokens for Claude. May need to split up what details are returned on the list_tasks call and return comments on a task specific API instead?

Proposed solution

list_Tasks returns extremely large set of characters after developing for while.

Alternatives considered

No response

Scope and impact

No response

[jeeshofone]

We've put together a fix for this — added a get_task MCP tool that returns a single task by ID with full details (including comments and blocked status). This lets agents fetch task detail on demand instead of getting everything via list_tasks.

Branch with the change: https://github.com/CompactSaaS-Org/flux/tree/feature/get-task-mcp

Will open a PR shortly.

[sirsjg]

Still a valid problem — list_tasks returns every comment on every task, so on a long-running project the response balloons past what an agent can take in. The earlier PR for this (#70) got stranded when the MCP server was rewritten, but the plan stands: slim down list_tasks (drop or truncate comments) and add a get_task tool that returns one task in full, so agents fetch detail on demand. Will look into it — the rewrite actually made this easier to do.