fix(acp): update AgentKit lifecycle handling - #43
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.
Summary
Update Kit to AgentKit's merged ACP v2 lifecycle and background-continuation revisions. Autonomous background drives now remain in the existing idle state instead of emitting synthetic
Running/Idlecycles, while foreground prompt state pairing is unchanged.Motivation
No-work autonomous drives could render phantom zero-duration turns after a background completion had already been consumed. The updated lifecycle behavior keeps ACP state transitions tied to real user-visible turns.
Technical details
AgentKit revision
Pins all AgentKit patches to
1204e2b31d77ca820c9302fab2769e0b5c0c1c10, which merges the released lifecycle changes from AgentKit main into the session-injection branch used by Kit. Direct package versions andCargo.lockare aligned with that revision.Autonomous error handling
Background continuation failures still emit a diagnostic agent message, but do not emit an
Idletransition because autonomous work begins while the ACP session is already idle.Version
Bumps Kit from
0.1.103to0.1.104for the behavior fix.