feat(acp): dispatch dynamic tools through websocket#619
Closed
gaofeng21cn wants to merge 1 commit into
Closed
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
Protocol
This is the AionCore host half of agentclientprotocol/codex-acp#301.
WebSocket events:
agent.dynamicToolsRegisteragent.dynamicToolsRegisteredagent.dynamicToolCallagent.dynamicToolResultACP session metadata uses
codex/dynamic_tools; the extension request iscodex/dynamic_tool_call. Ambiguous ownership is sticky fail-closed: disconnecting one claimant does not resurrect another claimant; a new explicit registration is required.Validation
Validated on
e1e022c9e327870bebefa26e417dc5f482349e10:cargo build --workspacecargo test --workspacejust pushgit diff --check HEAD^ HEADCross-repo evidence
24589322f1f6a2e7a9fba6ebb42067e47e4dfffd103b078af91454e9938f417fda0fde5ad52554b7This PR is ready for upstream review. The fork branch remains a contribution checkpoint, not a canonical product carrier. Product completion still requires both upstream canonical mains to merge and the Shell to consume released canonical refs.