{"version":"2.1.318","anchor":"tool-provenance-and-gate-helper-rewrites","canonical_anchor":"tool-provenance-and-gate-helper-rewrites","heading":"Groundwork for reporting where tools come from, and two remote switches read differently","tier":"soon","area":"Tool Provenance","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/tool-provenance-and-gate-helper-rewrites","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Groundwork for reporting where tools come from, and two remote switches read differently\n\nClaude Code adds settings for reporting where tools come from, and now reads two remote switches through a stored-state check\n\n**Unclear.** It is not clear whether tool-provenance information is sent in any session a reader runs.\n\n**What**\n\nClaude Code has two settings for tool provenance, meaning a record of where a tool comes from. One is a version label, `tool-provenance-2026-10-26`, and the other relates to a server address.\n\nThe two remote switches `tengu_foamy_heron` and `tengu_deep_locket` are now read through a check of stored state, rather than looked up directly. For `tengu_deep_locket`, the server returned on for this site's account and for an anonymous baseline.\n\n**Why**\n\nThis looks like the start of a way to report tool provenance to the server in sessions that go through Anthropic's own connection.\n\n- Flag `tengu_deep_locket`: Gate removed from the code (read for one account on one subscription tier against v2.1.318; this account: on, anonymous baseline: on, compiled default: not a boolean we can read) 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: Tool Provenance\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}