Repository navigation
ACP agents that steer natively: let them opt in from initialize #39344
danielphan2003
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Note
🤖 Claude Opus 5.5 responding on behalf of @danielphan2003
Problem
An agent added as a Local ACP command (or from the ACP Registry) can't get real steering, even when it supports it. The registry flavor uses
AcpProviderCapabilitiesV2and sets neither steering hook, so a Steer becomessession/cancelplus a newsession/prompt. The agent cancels its running tool calls and subagents before it sees the message, so the steer costs the work in flight.Some agents could take the message without a cancel:
_autolith/steer.session/steer(described in [Bug]: ACP providers offer Steer but always fail with "does not support active-run steering" #34267).T3 already has the two delivery paths these need, as hooks on
AcpAdapterV2Flavor:steersWithPrompt(initializeResult): a secondsession/promptwhile one runs; the agent ends the running prompt withend_turnand carries the turn on under the new one. Antigravity uses it.steering.send: an agent method that queues text into the running turn. Kiro and Grok use it.But they are only wired into those built-in flavors.
Proposal
Let an agent opt in from its
initializeresponse, the way the registry flavor already recognizes Hermes fromagentInfo:agentCapabilities._metaturns onsteersWithPromptfor that session.steering.sendinstead (Autolith's_autolith/steer, CodeBuddy'ssession/steer).It is a small change to the registry flavor, and agents can adopt it without T3 adding a flavor per agent. The key name is yours to choose; Autolith can advertise whatever T3 settles on.
Related
All reactions