{"version":"2.1.224","anchor":"remote-control-errors-are-typed-as-auth-or-terminal","canonical_anchor":"remote-control-errors-are-typed-as-auth-or-terminal","heading":"Remote Control errors are typed as auth or terminal","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-control-errors-are-typed-as-auth-or-terminal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote Control errors are typed as auth or terminal\n\nRemote Control failures are labelled auth or terminal, and auth ones point you at \/login.\n\n**What**\n\nBridge failures now record whether they were an auth problem or a terminal one, and auth failures show the `\/login` hint. The token-refresh failure message changed from \"re-authenticate, then re-enable Remote Control\" to text ending \"run \/login to re-authenticate\".\n\n**Details**\n\n- App state gains an error-kind field alongside the existing error, set to `\"auth\"` or the default `\"terminal\"`, and cleared wherever the error is cleared.\n\n**Evidence**\n\n`run \/login to re-authenticate`\n\n- Area: Remote Control\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}