{"version":"2.1.267","anchor":"new-gate-tengu-fizzy-bonbon-in-fast-mode-permission-path","canonical_anchor":"new-gate-tengu-fizzy-bonbon-in-fast-mode-permission-path","heading":"New tengu_fizzy_bonbon gate affects tool-permission resolution","tier":"soon","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-gate-tengu-fizzy-bonbon-in-fast-mode-permission-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New tengu_fizzy_bonbon gate affects tool-permission resolution\n\nA new tengu_fizzy_bonbon gate, off by default, branches how tool permission is resolved in fast-mode and auto-mode paths\n\n**Unclear.** Nothing has been read about the `tengu_fizzy_bonbon` gate, so what the alternate permission-resolution logic actually changes is unclear.\n\n**What**\n\n- A new gate, `tengu_fizzy_bonbon`, defaulting to off, was added to the tool-permission resolution flow.\n\n- In the fast-mode permission path, it switches between alternate ways of resolving tool permission.\n\n- In the auto-mode streaming path, it picks between two ways of establishing tool permission context\/consent: a more direct path, or the existing `getToolPermissionContext()` await path.\n\n**Why** This is an internal gated change to how Claude Code resolves whether a tool call is permitted; while off, behavior is unchanged, but it lays groundwork for a different permission-resolution approach.\n\n- Area: Models\n- Names: `tengu_fizzy_bonbon`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}