Unclear Nothing has been read about the tengu_fizzy_bonbon gate, so what the alternate permission-resolution logic actually changes is unclear.
What
- A new gate,
tengu_fizzy_bonbon, defaulting to off, was added to the tool-permission resolution flow. - In the fast-mode permission path, it switches between alternate ways of resolving tool permission.
- 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.
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.
Names in the bundletengu_fizzy_bonbon
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Nothing has been read about the `tengu_fizzy_bonbon` gate, so what the alternate permission-resolution logic actually changes is unclear.
The name it cites is new in this build
New in this build: tengu_fizzy_bonbon