Permission checks for handed-off skill shell commands now always see the tool in the tool list
Skills can include inline shell commands that Claude Code sometimes hands to the model to run explicitly instead of executing automatically. When that handoff happens, the permission check that decides whether the command is allowed now always runs with the tool included in the available tool options, adding it if it wasn't already present, rather than only sometimes including it.
This makes the permission decision for handed-off shell commands more consistent, so the check isn't skipped or handled differently depending on whether the tool happened to already be in the list.
tengu_iterative_falcon Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.277: on
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.
Read once, for one account on one subscription tier, against v2.1.277. It isn't a statement about your account. What a flag value here can and cannot tell you
It is unclear what user-visible difference this makes, since the gate controlling this handoff path has no known configuration read.