{"version":"2.1.281","anchor":"remote-control-non-interactive-registration-failures-wait-b","canonical_anchor":"remote-control-non-interactive-registration-failures-wait-b","heading":"Remote Control: non-interactive registration failures wait before exiting","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-non-interactive-registration-failures-wait-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control: non-interactive registration failures wait before exiting\n\nWhen `claude remote-control` fails to register without a terminal attached, it now waits a limited time before exiting\n\n**What**\n\nIf `claude remote-control` fails to register and it is not running in a terminal (for example when started by a script), and the error carries an HTTP status, the process now waits before exiting. The wait is based on the server's Retry-After value, a hint about how long to wait before trying again, and has an upper limit. It prints a notice such as \"Exiting in about 30 seconds.\"\n\n**Why**\n\nA script or service that runs Remote Control will see a pause and a notice before the process exits, instead of an immediate exit.\n\n- Area: Remote Control\n- Names: `claude remote-control`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}