Unclear Whether this behavior is active depends on gates (tengu_iterative_falcon, tengu_prompt_shell_permission) that have not been read, and tengu_glowing_orbit, which this site's account currently reads as on but has not yet been read under this release.
Skills are packaged instructions written in markdown, and some embed inline shell commands (written as !command or in fenced ! blocks) that run automatically. When the permission decision for one of these commands is 'ask' (meaning Claude Code would normally prompt before running it), or a deny that's tied to an async-agent reason, a new code path can replace the command with a placeholder and instead tell the model to run it explicitly, exactly as written, and use its output. This turns what used to be an invisible side effect into a visible, explicit step in the conversation.
This gives more visibility and control over shell commands embedded in skills, so a command that needs permission or was previously denied doesn't just silently fail or run without the user noticing.
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.271: 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.
tengu_glowing_orbit On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.271: 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.271. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Whether this behavior is active depends on gates (`tengu_iterative_falcon`, `tengu_prompt_shell_permission`) that have not been read, and…
New in this build: tengu_glowing_orbit