{"version":"2.1.277","anchor":"prompt-shell-command-handoff-now-carries-full-tool-options","canonical_anchor":"prompt-shell-command-handoff-now-carries-full-tool-options","heading":"Prompt-shell command handoff now carries full tool options","tier":"internal","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/prompt-shell-command-handoff-now-carries-full-tool-options","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Prompt-shell command handoff now carries full tool options\n\nPermission checks for handed-off skill shell commands now always see the tool in the tool list\n\n**Unclear.** It is unclear what user-visible difference this makes, since the gate controlling this handoff path has no known configuration read.\n\n**What**\n\nSkills 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.\n\n**Why**\n\nThis 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.\n\n- Flag `tengu_iterative_falcon`: Not enough to say (read for one account on one subscription tier against v2.1.277; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}