{"version":"2.1.300","anchor":"tengu-jaunty-umbrella-gate-for-a-tool-arbiter-path-fallback","canonical_anchor":"tengu-jaunty-umbrella-gate-for-a-tool-arbiter-path-fallback","heading":"A new switched-off check for one tool in the arbiter permission mode","tier":"soon","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/tengu-jaunty-umbrella-gate-for-a-tool-arbiter-path-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### A new switched-off check for one tool in the arbiter permission mode\n\nA new check covers one specific tool in a permission mode named arbiter and stays off unless the server turns it on\n\n**Unclear.** What this check turns on or changes when it applies is not clear.\n\n**What**\n\nA new check looks at the tool name and whether the session's permission mode is the one named \"arbiter\". A second check matches it against one specific tool. Both sit behind the `tengu_jaunty_umbrella` server-side switch, which falls back to off when the server sends nothing.\n\nThe flag server returned off for this site's account and for the anonymous baseline. No reading has been taken under this release yet.\n\n**Why**\n\nIn practice this is a feature that is off by default, in the part of Claude Code that decides whether a tool may run.\n\n- Flag `tengu_jaunty_umbrella`: Off in both readings (read for one account on one subscription tier against v2.1.300; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}