{"version":"2.1.227","anchor":"agent-refuses-spawns-where-the-bash-command-clamp-would-not-","canonical_anchor":"agent-refuses-spawns-where-the-bash-command-clamp-would-not-","heading":"agent() refuses spawns where the Bash command clamp would not bite","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/agent-refuses-spawns-where-the-bash-command-clamp-would-not-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### agent() refuses spawns where the Bash command clamp would not bite\n\nSub-agent spawns are refused when the Bash command restriction couldn't be enforced.\n\n**What**\n\nTwo new checks on sub-agent spawns. If the host has remapped Bash or the related exec tools to different names, the clamp cannot be guaranteed on that path and the spawn is refused. If the spawned agent's tool set contains no Bash at all, the spawn is refused rather than running an agent whose clamp does nothing.\n\n**Details**\n\n- a third guard refuses schema-mode spawns whose combined disallow list denies the StructuredOutput tool, which that mode needs\n\n**Evidence**\n\n`agent() bashCommandClamp under a shell toolAlias`\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}