{"version":"2.1.248","anchor":"new-reason-when-a-remote-approval-does-not-land-refused-afte","canonical_anchor":"new-reason-when-a-remote-approval-does-not-land-refused-afte","heading":"New reason when a remote approval does not land: refused after an automatic approval","tier":"notice","area":"Remote Approvals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/new-reason-when-a-remote-approval-does-not-land-refused-afte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### New reason when a remote approval does not land: refused after an automatic approval\n\nWhen an auto-approved remote call is refused, Claude is told to ask you to approve it directly.\n\n**What**\n\nIf this session's automatic check approved a tool call and an unverifiable sender then reported it refused, the model is now told exactly that instead of getting the generic dropped or unverified-refusal message. The follow-up advice is tailored per case, telling the model to re-send the call and ask you to approve it from the terminal or desktop prompt when only a person's approval counts for that tool.\n\n**Evidence**\n\n`This session's automatic check (not a person) had approved the call`\n\n- Area: Remote Approvals\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}