fix: align agent websocket origin#307
Merged
Merged
Conversation
Derive debugger WebSocket Origin from the selected inspector URL. Default local agent connections to 127.0.0.1 so React Native origin checks accept agent sessions.
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.
What is this?
This PR fixes Rozenite for Agents session startup when React Native rejects debugger WebSocket connections because the
Originheader does not match the selected inspector URL. The CLI now defaults local agent traffic to127.0.0.1, which matches the loopback host Expo returns for local inspector targets.How does it work?
Agent sessions now derive the debugger WebSocket
Originfromtarget.webSocketDebuggerUrlinstead of hardcodinghttp://localhost:<port>. That keeps the WebSocket URL andOriginhost aligned whether Metro returns127.0.0.1,localhost, or a securewsstarget. The session tests cover the127.0.0.1origin case that previously failed.Why is this useful?
React Native is tightening debugger WebSocket origin checks, and Expo already terminates mismatched local origins. Aligning the origin with the selected inspector target lets Rozenite for Agents bootstrap reliably instead of failing with
CDP connection closed before bootstrap completed.