{"version":"2.1.290","anchor":"pewter-owl-tool-responses-gated-by-tengu-witty-hearth","canonical_anchor":"pewter-owl-tool-responses-gated-by-tengu-witty-hearth","heading":"A remote switch now controls an opt-in tool behaviour","tier":"use","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/pewter-owl-tool-responses-gated-by-tengu-witty-hearth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A remote switch now controls an opt-in tool behaviour\n\nWith `CLAUDE_CODE_PEWTER_OWL_TOOL` set, three tools can now leave out a response ID depending on a remotely controlled switch\n\n**Unclear.** What this tool behaviour does, and what the other conditions test, are not known.\n\n**What**\n\nSetting the environment variable `CLAUDE_CODE_PEWTER_OWL_TOOL` to true opts into a behaviour affecting three tools. Before, those three tools always returned a response ID.\n\nThey now leave the response ID out when a check on the last response passes. That check needs certain other conditions not to apply, and it needs a remotely controlled switch, `tengu_witty_hearth`, to be on. When the server sends nothing for that switch, it falls back to on.\n\n**Why**\n\nThe switch gives a way to turn this opt-in behaviour off or on remotely, even for people who have set the environment variable.\n\n- Flag `tengu_witty_hearth`: Not enough to say (read for one account on one subscription tier against v2.1.290; 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: Tools\n- Names: `CLAUDE_CODE_PEWTER_OWL_TOOL`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}