A complete WebSocket-based remote bridge implementation for connecting Claude Code CLI sessions to Claude Desktop, replacing the older SSE-based transport.
- New WebSocket transport with JWT-based authentication (
worker_jwt) - Automatic JWT refresh on 401 errors with transparent transport rebuilding
- Connection status tracking: "Disconnected", "Reconnecting…" states shown in the UI
- Keep-alive heartbeat for session persistence
- Message batching and history flushing on reconnection
- Session creation via
/v1/code/sessionsendpoint - Session archival support
- Gated by
tengu_bridge_repl_v2feature flag
Remote bridge session manager (search for "[remote-bridge]") — 38+ log messages added; feature flag tengu_bridge_repl_v2
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_bridge_repl_v2 On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.77: no gate table built for this version
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.77. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.