Keep user messages intact when automatic planning starts - #42
Merged
Conversation
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.
What changes
Desktop now routes high-confidence multi-step requests straight into the reviewable planner. It no longer changes the text of a user's message behind the scenes to persuade the model to call a planning tool.
Automatic planning is based on task shape: explicit checklists, cross-cutting changes, and multiple deliverables can trigger it. Questions, research, explanations, and narrow edits stay conversational. When Desktop starts a plan automatically, the transcript briefly explains why.
Rejected-plan follow-ups and forced skills now use separate, temporary system-role guidance. That guidance cannot be confused with user-authored text and does not carry into later turns.
Why users will notice
Also documented
The Unreleased changelog includes this behavior and the recently merged provider-reported token-total fix.
Validation
This PR pins the matching engine branch commit until the engine PR is merged.