{"version":"2.1.296","anchor":"tengu-polished-tulip-check-gains-a-second-argument","canonical_anchor":"tengu-polished-tulip-check-gains-a-second-argument","heading":"Remotely controlled shell instructions can now name the tool they are for","tier":"internal","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/tengu-polished-tulip-check-gains-a-second-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Remotely controlled shell instructions can now name the tool they are for\n\nThe remotely switched instruction text used for shell commands now records which tool it is for, so the same text could serve other tools\n\n**What**\n\nThe remote setting behind the extra instruction text Claude receives when running shell commands now also records which tool the text is for. Shell commands pass \"bash\". The setting still falls back to on when the server sends nothing. Readings taken before this release found it on for this site's account and for a signed-out baseline.\n\n**Why**\n\nThe instructions for shell commands should stay the same. The change looks like groundwork for using the same remotely controlled text with other tools.\n\n- Flag `tengu_polished_tulip`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.296; this account: on, anonymous baseline: on, 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: Bash\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}