{"version":"2.1.139","anchor":"remote-control-diagnostics-are-more-specific","canonical_anchor":"remote-control-diagnostics-are-more-specific","heading":"Remote Control Diagnostics Are More Specific","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.139\/e\/remote-control-diagnostics-are-more-specific","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.139","markdown":"### Remote Control Diagnostics Are More Specific\n\nRemote Control now tells users why it is unavailable in more cases, especially when the session is using API-key auth or a non-first-party backend.\n\n**Details**\n\n- Distinguishes `ANTHROPIC_API_KEY`, `ANTHROPIC_AUTH_TOKEN`, `apiKeyHelper`, and `ANTHROPIC_UNIX_SOCKET` cases.\n- Explains that Remote Control requires claude.ai subscription auth.\n- Adds a specific message when the active backend is not `api.anthropic.com`.\n\n**Evidence**\n\nRemote Control auth diagnostics (search for `\"Remote Control requires claude.ai subscription auth\"`, `\"ANTHROPIC_API_KEY is set\"`, `\"Remote Control is only available when using Claude via api.anthropic.com\"`)"}