fix(cli): keep todo updates incremental - #13249
Merged
Merged
Conversation
johnnyeric
approved these changes
Aug 19, 2026
This was referenced Aug 24, 2026
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
2 participants
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.
Multi-step todo lists can stop visibly advancing after the first or second item even though the todo persistence path can store later replacements. This makes longer tasks appear stalled and hides the current execution state from clients.
The regression follows the upstream tool-prompt reduction that shortened
todowriteguidance, which Kilo carried into the v1.17.6 through v1.17.9 compatibility merge in #12460. The reduced description still said to update status in real time, but it did not make the required call boundary explicit between completed items.This change keeps the policy at the tool boundary rather than adding todo-specific text to the general system prompt. The
todowritedescription now requires an update before the first item and after every completed item, and prevents continuing through multiple steps without an intervening update. It also adds a description contract test and a real CLI end-to-end test covering five sequential updates through the second-item boundary to a fully completed list.