{"version":"2.1.304","anchor":"remote-control-response-cannot-answer-a-specific-dialog-kind","canonical_anchor":"remote-control-response-cannot-answer-a-specific-dialog-kind","heading":"Remote control can no longer answer one kind of SDK dialog","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-control-response-cannot-answer-a-specific-dialog-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote control can no longer answer one kind of SDK dialog\n\nA response sent through remote control is now refused when the waiting dialog is a kind only the SDK host may answer\n\n**Unclear.** Which kind of dialog is reserved for the SDK host is not stated.\n\n**What**\n\nThe SDK is the kit developers use to run Claude Code from their own programs. Claude Code can now take a response sent in through remote control and pass it on as the answer to a waiting request. It refuses to do this when the waiting request is a `request_user_dialog` of one particular kind. That kind of dialog is now answered only when the program running Claude Code is the SDK host.\n\n**Why**\n\nRemote clients cannot answer dialogs meant only for the SDK host.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}