The Remote Control feature (/remote-control) has been substantially rebuilt with a full bridge architecture for controlling CLI sessions from claude.ai/code. The feature flag was changed from tengu_worktree_mode to tengu_ccr_bridge, and the implementation now includes:
- Full work-polling loop with session spawn/teardown lifecycle
- WebSocket-based session ingress for real-time communication
- QR code display (togglable with spacebar) for quick mobile connection
- Automatic OAuth token refresh with JWT expiry tracking
- Environment registration, deregistration, and re-registration on failure
- Reconnection with exponential backoff and error budget
- Session activity tracking (tool starts, text output, results)
remoteControlAtStartupsetting to auto-enable Remote Control for all sessionsallow_remote_sessionspolicy for organization-level control
Feature flag tengu_ccr_bridge, command definition name: "remote-control" with aliases ["rc"] (search for "tengu_ccr_bridge")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_worktree_mode 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.51: 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.
tengu_ccr_bridge 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: off · compiled default in v2.1.51: 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.51. 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.