Repository navigation
fix(acp): report compose executions as tool calls, not plans - #337
Merged
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.
Summary
Stop projecting runtime tool-execution tasks into ACP plans in both v1 and v2. Compose executions continue to use their existing tool-call cards and completion updates.
Motivation
ACP plans represent an agent's to-do list or execution strategy. Mapping foreground and background compose calls into plan entries caused clients to show repeated “Added compose” task lists instead of only tool activity.
Technical details
Remove the task-plan reducer and its actor and settlement observers. Background scheduling, cancellation, and completion handling remain unchanged.