{"version":"2.1.227","anchor":"clamped-agents-are-blocked-on-every-execution-surface","canonical_anchor":"clamped-agents-are-blocked-on-every-execution-surface","heading":"Clamped agents are blocked on every execution surface","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/clamped-agents-are-blocked-on-every-execution-surface","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Clamped agents are blocked on every execution surface\n\nCommand-restricted agents are now blocked on PowerShell and the Monitor tool too, and fail closed.\n\n**What**\n\nAn agent restricted to a specific set of allowed shell commands is now denied when it tries to run through PowerShell or the Monitor tool's websocket mode, not just Bash. A crash inside the permission check now denies for those agents rather than letting the command through.\n\n**Details**\n\n- Denials carry a dedicated reason, e.g. \"bashCommandClamp: no clamp rule matches this command\".\n- Bash denials emit a `tengu_bash_command_clamp_denied` event.\n- The permission check now fails closed for clamped agents; previously an error in the check could result in execution proceeding.\n\n**Evidence**\n\n`bashCommandClamp: no clamp rule matches this command`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}