Repository navigation
feat(coding-agent): persist plan criteria in task context - #249
Merged
Merged
Conversation
- Keeps step IDs and success criteria across updates, resume, and compaction - Appends current plan state to every model request after tool execution
- Describes step IDs, criteria, single-step updates, and per-request plan context
- Makes session cache reuse visible alongside context usage - Fits the rate within narrow footer widths
- Prevents saved tool output from being remeasured on every keystroke - Keeps typing responsive as session history grows
- Keep plan snapshots in persisted tool results and compaction summaries - Let ordinary requests reuse prior model message prefixes
Updated guidelines to include optional success criteria for subtasks.
- Make the destination plan explicit when abandoned branches are summarized - Persist the snapshot so restored sessions retain unambiguous plan context
- Keep the prompt assertion consistent with optional success criteria
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
Persist
update_plansteps with stable IDs and optional success criteria while keeping the latest plan available in durable conversation history.Return the complete resolved plan in successful tool results instead of appending a plan message to every model request, so ordinary requests can reuse the previous prompt prefix.
Reasoning
Appending an unsaved current-task message to each request moved that message when the next turn added conversation history, breaking prompt cache reuse.
Persisted tool results carry plan changes in the normal conversation.
Successful compaction summaries include the latest plan snapshot so the plan remains available after older tool results are compacted away.
The latest plan does not need to be the final message of every request.
Changes
update_plan.details.planunchanged; clearing still returnsPlan cleared.Testing
session.prompt()with the faux provider before the fix.npm run check