{"version":"2.1.314","anchor":"permission-denied-message-for-headless-sessions-is-now-compo","canonical_anchor":"permission-denied-message-for-headless-sessions-is-now-compo","heading":"The headless permission-denied message now says the action was not performed","tier":"notice","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/permission-denied-message-for-headless-sessions-is-now-compo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### The headless permission-denied message now says the action was not performed\n\nWhen a tool needs approval nobody can give, Claude is now told the action was NOT performed, and the message opens differently\n\n**Unclear.** The new opening wording of the message is not known.\n\n**What**\n\nIn a headless session, Claude Code runs with nobody at the screen to answer permission prompts. When Claude tries an action that needs your approval there, Claude Code refuses it and sends Claude a message explaining why.\n\nThat message now ends with \"and permission prompts are not available in this session. The action was NOT performed.\" The closing sentence saying the action was not performed is new. The opening part of the message now comes from wording shared with other messages, so it may also read differently.\n\n**Why**\n\nThis changes the exact wording Claude sees when an action is refused, which matters if you rely on that text.\n\n- Area: Headless Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}