{"version":"2.1.178","anchor":"remote-control-diagnostics-improvements","canonical_anchor":"remote-control-diagnostics-improvements","heading":"Remote Control Diagnostics Improvements","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178\/e\/remote-control-diagnostics-improvements","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178","markdown":"### Remote Control Diagnostics Improvements\n\n**What**\n\nThe Remote Control eligibility check (shown in `claude doctor` and related diagnostics) now shows more granular, correctly-labeled status for each check.\n\n**Details**\n\n- Each check now shows a positive or negative label depending on its state, e.g. \"Connected to the Anthropic API (api.anthropic.com)\" vs. \"Not connected to the Anthropic API (api.anthropic.com)\"\n- A new explicit org policy check: \"Org policy allows Remote Control (allow_remote_control)\" \/ \"Org policy does not allow Remote Control\" \/ \"Org policy could not be verified\"\n- The rollout gate check now distinguishes between \"rollout not enabled for this account\" and \"could not be verified for this account\" (no server response)\n- Remote Control is now blocked with a clearer message when the organization's compliance policy disallows it\n\n**Evidence**\n\nUpdated diagnostics function (search for `\"Connected to the Anthropic API (api.anthropic.com)\"`, `\"Org policy allows Remote Control (allow_remote_control)\"`, `\"Remote Control rollout enabled for this account\"`)"}