{"version":"2.1.284","anchor":"refused-remote-control-answers-are-replaced-by-an-error-stan","canonical_anchor":"refused-remote-control-answers-are-replaced-by-an-error-stan","heading":"Remote Control sends an error in place of a refused tool answer","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/refused-remote-control-answers-are-replaced-by-an-error-stan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Remote Control sends an error in place of a refused tool answer\n\nWhen the service refuses a tool's answer in a Remote Control session, Claude Code now sends an error result instead of dropping it\n\n**Unclear.** When exactly this replacement is triggered is not settled.\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. When Claude uses a tool, meaning it runs one of its actions such as reading a file, the result is sent back to the session service.\n\n- If the service refuses that answer, Claude Code now sends a replacement result marked as an error. Before, it logged that the answer was 'not re-sending' and gave it up.\n\n- This applies to refusals with HTTP error statuses. Sign-in errors 401 and 403 are excluded. One finding also lists 408 and 429 as excluded.\n\n- An answer that was refused because it was over the service's size limit gets its own warning message.\n\n- The debug log says the answer was refused and that an error is being sent in its place.\n\n**Why**\n\nBefore, a remote session could wait indefinitely for a tool result that was never going to arrive, for example one that was too large. Now it receives an error it can see and act on.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}