Repository navigation
fix(run): replay plan-file edits when capturing the presented plan - #328
Merged
Merged
Conversation
The plan-file signal took the last write under the plan root and read its `content_field`. Claude Code agents often revise the plan in place with `Edit` or `MultiEdit`, which carry no `content`, so capture silently fell back to the round's final message while still recording `signal: plan_file`. A plan-review pass produces exactly that trailing edit, which biased captured artifacts against the arm that reviewed. Rebuild the last-touched plan file by replaying every write to that path in order: a write carrying `content_field` replaces the content, and an edit applies with the harness's matching rules (one occurrence unless `replace_all`). An edit the tool rejected (`<tool_use_error>`) changed nothing and is skipped. When the replay cannot reproduce the file, the final message stands in and `plan.signal` records `final_message`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
The plan-file signal took the last write under the plan root and read its
content_field. Claude Code agents often revise the plan in place withEditorMultiEdit, which carry nocontent, so capture silently fell back to the round's final message while still recordingsignal: plan_file. A plan-review pass produces exactly that trailing edit, which biased captured artifacts against the arm that reviewed.Rebuild the last-touched plan file by replaying every write to that path in order: a write carrying
content_fieldreplaces the content, and an edit applies with the harness's matching rules (one occurrence unlessreplace_all). An edit the tool rejected (<tool_use_error>) changed nothing and is skipped. When the replay cannot reproduce the file, the final message stands in andplan.signalrecordsfinal_message.