fix: cross-host messaging script #58
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
The second resolve_agent call (for sender's alias) was overwriting RESOLVED_HOST_URL, causing cross-host messages to fail. Now we save TO_HOST_URL immediately after resolving the destination. Co-Authored-By: Claude Opus 4.5 <[email protected]>
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
Fix cross-host message sending by saving
RESOLVED_HOST_URLbefore it gets overwritten.Bug
When sending a message to a remote host, the
resolve_agentcall for the sender's alias was overwritingRESOLVED_HOST_URL, causing the script to use the wrong (or empty) URL.Fix
Save
TO_HOST_URLimmediately after resolving the destination agent.🤖 Generated with Claude Code