{"version":"2.1.304","anchor":"late-permission-answers-are-bounded-and-may-be-refused","canonical_anchor":"late-permission-answers-are-bounded-and-may-be-refused","heading":"Late permission answers with oversized input are now refused","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/late-permission-answers-are-bounded-and-may-be-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Late permission answers with oversized input are now refused\n\nA permission answer that arrives late is refused if the input it supplies is too large or too deeply nested\n\n**What**\n\nBefore Claude runs some actions, it asks for permission, and the answer can come from somewhere other than the terminal, such as a program built on Claude Code. An answer can also change the input the action runs with.\n\nWhen such an answer arrives late, Claude Code now checks that changed input. If it is too large or too deeply nested, the action is not run and Claude sees this message:\n\n\"The call was not run. The permission answer gave it an input past what this session takes from an answer\"\n\n**Why**\n\nThis is a new safety limit on permission answers that come from remote or programmatic sources, so an outsized answer cannot slip an oversized input into an action.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}