Skip to content

connector: connecting includes opening the inbox watch, as a local bridge does - #4900

Merged
trissim merged 1 commit into
mainfrom
connector-connect-opens-watch
Nov 18, 2026
Merged

trissim merged 1 commit into
mainfrom
connector-connect-opens-watch

Conversation

@trissim

@trissim trissim commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

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

…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
@trissim
trissim merged commit 3ae4ae2 into main Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant