{"version":"2.1.321","anchor":"remote-control-inbound-handling-tweaks","canonical_anchor":"remote-control-inbound-handling-tweaks","heading":"Remote Control can no longer answer hook callbacks","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-inbound-handling-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote Control can no longer answer hook callbacks\n\nOver Remote Control, answers to hook callbacks are now refused, as answers to user dialogs already were\n\n**What**\n\nRemote Control lets you drive a Claude Code session from somewhere else. A hook is a command you configure to run automatically, and some hooks wait for an answer, called a callback. Claude Code now refuses callback answers that come in over Remote Control. Before, only answers to user dialogs were refused.\n\nWhen the host has confirmed a dialog itself, Claude Code now records that the dialog was answered over Remote Control. Creating a session also accepts a new kind of environment and a repository for its results.\n\n**Why**\n\nA remote client can no longer answer a hook's question on your behalf.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}