Repository navigation
connector: connecting includes opening the inbox watch, as a local bridge does - #4900
Merged
Merged
Conversation
…as a local session's bridge does A cloud session reaches the bus only through the connector's request/response tools; it is reachable (bound as its thread's reader, shown bridged) only while its inbox watch socket is open, the same registry binding a local bridge holds. The handshake instructions never said so, so cloud sessions connected, worked, and showed 'no bridge' whenever idle. Every connector client now reads that connecting is done once the watch is open, and to reopen it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RnH6dT7wdh7i4tjJZQdFu3
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.
Cloud sessions are bound as their thread's reader (shown bridged) only while their inbox watch socket is open, the same external_process binding a local bridge holds; the handshake instructions never said connecting includes it, so they showed 'no bridge' whenever idle. InitializeResult.announcing now adds that rule for every connector client. Tests: 69 passed (connector/MCP).
🤖 Generated with Claude Code
https://claude.ai/code/session_01RnH6dT7wdh7i4tjJZQdFu3