{"version":"2.1.321","anchor":"remote-control-response-dropped-when-its-card-is-open-under","canonical_anchor":"remote-control-response-dropped-when-its-card-is-open-under","heading":"Stale or duplicate approvals from a remote client are now ignored","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-response-dropped-when-its-card-is-open-under","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Stale or duplicate approvals from a remote client are now ignored\n\nIn remote sessions, an approval for a tool whose prompt is already open under a different request is now dropped instead of acted on\n\n**What**\n\nWhen Claude Code wants to use a tool that needs your permission, it shows an approval prompt, sometimes called a card. In a remote session, where you control Claude Code from another device or app, your answer arrives as a message tied to a request id.\n\nClaude Code now ignores an \"allow\" answer if the same tool use already has an approval prompt open under a different request id. Before, the only duplicate check caught answers for a tool use that had already been settled. Claude Code now also keeps track of which approval requests are open and which have been sent.\n\n**Why**\n\nThis closes a gap where two answers could approve the same tool use in a remote session, so an old or repeated approval can no longer slip through while a newer prompt is still waiting.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}