Editors can now ask whether Remote Control could ever work in your deployment.
What's wrong with this entry?
The handshake an editor extension makes with Claude Code can now return remote_control_available, saying whether Remote Control is possible in this deployment at all: not turned off by managed settings, not running inside a remote environment, and on a first-party provider. Editors can use it to hide the Remote Control affordance where it can never work. Older CLIs omit the field, and it is treated as available.
- Deliberately separate from transient state such as whether you are signed in or in the rollout, so hiding the UI is a permanent decision rather than a flicker.
remote_control_available
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Stale editor bridge connections are dropped instead of read
Both mention integration
-
v2.1.234
Git remote URLs can no longer smuggle a different host
Both mention integration
-
v2.1.236
Change detection ignores custom diff drivers and submodules
Both mention integration