Group of 2 Nothing to try yet
No documentation found
A new tengu_fizzy_bonbon gate, off by default, branches how tool permission is resolved in fast-mode and auto-mode paths
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
What behavioral difference exists between the two permission-context paths, and whether tengu_fizzy_bonbon is active anywhere, is not known.
The name it cites is new in this build
New in this build: tengu_fizzy_bonbon