claude-code - 💡(How to fix) Fix Investigate: should TodoWrite allow marking multiple todos complete in one call? [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#60598Fetched 2026-05-20 03:54:24
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

Today, when several adjacent steps finish together (e.g. during a setup phase, or when a task wraps up multiple sub-steps at once), the assistant has to issue separate TodoWrite calls to flip each todo from in_progress → completed. The work was conceptually one transition but is split across many tool invocations.

Root Cause

Today, when several adjacent steps finish together (e.g. during a setup phase, or when a task wraps up multiple sub-steps at once), the assistant has to issue separate TodoWrite calls to flip each todo from in_progress → completed. The work was conceptually one transition but is split across many tool invocations.

RAW_BUFFERClick to expand / collapse

Question to investigate

Should TodoWrite support marking multiple todos as complete in a single tool call, rather than requiring one call per status update?

Context

Today, when several adjacent steps finish together (e.g. during a setup phase, or when a task wraps up multiple sub-steps at once), the assistant has to issue separate TodoWrite calls to flip each todo from in_progress → completed. The work was conceptually one transition but is split across many tool invocations.

What to investigate

  • How often do real sessions have batches of "complete several at once" transitions vs. one-at-a-time? (Telemetry would tell.)
  • Trade-offs of batching: simpler/shorter tool traces, fewer round trips — vs. the discipline of "mark each one done as soon as it's done" that the current single-update pattern enforces (which the system prompt explicitly encourages).
  • Whether allowing batches would lead the model to defer completion updates and lose the granularity that makes the todo list useful as a progress signal.
  • Whether the right answer is API-level support, or just better prompting around the current one-at-a-time pattern.

This is an investigation, not a feature request — the right outcome might be "leave it as is."

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Investigate: should TodoWrite allow marking multiple todos complete in one call? [1 participants]