Emit proposed plans for plan-capable clients#2
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
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.
Why
Upstream codex-acp#326 makes completed plans visible as ordinary final-answer messages. Anvil also needs the unstable ACP
plan_updateartifact so it can render a first-class Proposed Plan card and require an explicit implementation handoff.Review capability gating and live/history parity first.
Changes
plan_updatewhen the client advertises Plan support.Related Anvil PR: anvil-works/anvil#7168
Test evidence
npm test -- --run— 333 passed, 28 skipped.npm run typecheck— passed.npm run build— passed.git diff --check— passed.AI assisted with implementation, tests, and PR text.