{"version":"2.1.321","anchor":"rebranded-migration-name-and-remote-control-check","canonical_anchor":"rebranded-migration-name-and-remote-control-check","heading":"Remote Control counts more settings errors in its settings check","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/rebranded-migration-name-and-remote-control-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote Control counts more settings errors in its settings check\n\nRemote Control's settings check now counts every non-warning settings issue, including those that were only shown as status notes\n\n**Unclear.** It is not stated what Remote Control does when this check finds a problem, such as refusing to start.\n\n**What**\n\nBefore Remote Control starts, Claude Code checks your settings for problems. Some settings issues are marked to be shown only as status notes. Before, those were ignored entirely. Now the check works like this:\n\n- Any issue that is more serious than a warning counts as a problem, including status-note issues.\n\n- A warning counts only if it is not a status note and it concerns `disableRemoteControl`.\n\nA one-time settings upgrade step for the Fable model alias was also renamed.\n\n**Why**\n\nA serious settings error that is only shown as a status note can now affect Remote Control, where before it was skipped.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}