Fix ACP backend routing for configured agents - #1
Open
Justin0087 wants to merge 1 commit into
Open
Conversation
Justin0087
force-pushed
the
acp-host-routing-source-copilot
branch
from
June 23, 2026 06:30
b8e17b8 to
2c73482
Compare
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: add agent-aware ACP backend resolution, route ACP spawn/manager paths by configured agent backend, reuse the live Gateway NodeRegistry in local/detached contexts, and add regression tests. Testing: git diff --check passed; local OpenClaw Vitest was blocked by missing rolldown optional native binding and pnpm install network timeout. Spark/staging should run the targeted P0 tests and real quantum/copilot smoke.