{"version":"2.1.282","anchor":"claude-remote-control-accepts-debug-d-and-debug-in","canonical_anchor":"claude-remote-control-accepts-debug-d-and-debug-in","heading":"claude remote-control accepts --debug and -d instead of failing","tier":"use","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/claude-remote-control-accepts-debug-d-and-debug-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### `claude remote-control` accepts `--debug` and `-d` instead of failing\n\n`claude remote-control` no longer stops with an unknown-argument error when given `--debug`, `-d` or `--debug=\u2026`\n\n**Unclear.** Whether the flag actually turns on debug output for remote control or is only tolerated is not known.\n\n**What**\n\n`claude remote-control` used to reject `--debug`, `-d` and `--debug=\u2026` as unknown arguments, stop, and point you to `claude remote-control --help`. It now accepts them. This command's own argument handling does nothing further with the flag.\n\n**Why**\n\nRunning `claude remote-control --debug` used to fail at startup and now runs.\n\n- Area: Remote Control\n- Names: `claude remote-control`, `--debug`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}