{"version":"2.1.290","anchor":"remote-control-permission-responses-tracked-by-tool-name-p","canonical_anchor":"remote-control-permission-responses-tracked-by-tool-name-p","heading":"Remote control keeps a permission prompt open when the answer is for another tool","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-control-permission-responses-tracked-by-tool-name-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote control keeps a permission prompt open when the answer is for another tool\n\nWhen a session is controlled remotely, a permission answer naming the wrong tool no longer dismisses the prompt that is waiting\n\n**Unclear.** Whether the device identity setting is in use is not clear.\n\n**What**\n\nWhen Claude Code is driven remotely, permission questions (\"may Claude run this tool?\") are answered over the connection. Claude Code now notes which tool each successful answer is about. If an answer names a different tool from the question that is waiting, the question stays open instead of being cleared. Answers that come back as errors to questions shown to you are now handled according to a device identity setting.\n\nThe description of the `prompt.fill` event, which fills in the text box, now says that over a remote session connection it is sent only when the session's owner is the only account writing to it.\n\n**Why**\n\nA stray answer, or one meant for something else, is less likely to dismiss a permission question you have not answered.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}