{"version":"2.1.290","anchor":"shell-nesting-depth-refusal-message-reworded","canonical_anchor":"shell-nesting-depth-refusal-message-reworded","heading":"Clearer wording when a command nests shells too deeply","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-nesting-depth-refusal-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer wording when a command nests shells too deeply\n\nThe refusal reason for a command that passes shell code through too many nested shells now reads more simply\n\n**What**\n\nA shell is the program that runs your terminal commands. Before Claude Code runs a command, it checks whether the command is safe to approve. Some commands hand shell code to another shell, which can hand it to yet another one. When a command does this too many times, Claude Code gives a reason for not approving it. That reason now reads \"it hands shell code to a shell too many layers deep\". It used to say \"it hands shell code to a shell more times over than this reading follows\".\n\n**Why**\n\nYou see this text when Claude Code asks for your permission, so the shorter wording is easier to understand. Only the words changed. The check works the same way.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}