{"version":"2.1.318","anchor":"bash-permission-second-pass-check-under-tengu-quiet-sextant","canonical_anchor":"bash-permission-second-pass-check-under-tengu-quiet-sextant","heading":"Some shell commands get a second permission check that can overturn an allow","tier":"internal","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bash-permission-second-pass-check-under-tengu-quiet-sextant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Some shell commands get a second permission check that can overturn an allow\n\nCertain shell commands are checked twice for permission when a remote switch is on, and a deny from the second check wins\n\n**Unclear.** Which commands match the pattern, and what the second check does differently, is not clear.\n\n**What**\n\nBefore Claude Code runs a shell command, it checks whether the command is allowed. A new step now wraps that check. If the command matches a particular pattern and the remote switch `tengu_quiet_sextant` is on, Claude Code runs the permission check a second time in a different way. If that second check denies the command, the command is denied, and the reason shown combines both results.\n\n**Why**\n\nA command that the normal check would allow can now end up denied, so a command you expect to run may be blocked.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}