{"version":"2.1.281","anchor":"remote-control-session-capacity-refusal-title-appears-unuse","canonical_anchor":"remote-control-session-capacity-refusal-title-appears-unuse","heading":"Remote-control session capacity refusal title (appears unused)","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-session-capacity-refusal-title-appears-unuse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote-control session capacity refusal title (appears unused)\n\nA helper that labels a Remote Control session as refused for lack of capacity was added but does not appear to be used yet\n\n**Unclear.** The finding does not say whether anything calls this helper or what the always-false check will eventually control.\n\n**What**\n\nRemote Control lets you drive a Claude Code session running on one machine from somewhere else. It relies on a connecting piece called the bridge. A new bridge helper can rename a session so its title starts with \"Couldn't start\" and says too many sessions are running. It also records the reason `capacity` in a field called `client_metadata.desktop_rc_refusal`. Next to it is a new placeholder check that always answers false.\n\n**Why**\n\nIn practice nothing changes yet. The pieces exist for showing why a session never started, but the finding describes them as apparently unused."}