{"version":"2.1.312","anchor":"compiled-in-default-for-tengu-snoopy-creek-flipped-true","canonical_anchor":"compiled-in-default-for-tengu-snoopy-creek-flipped-true","heading":"Permission-decision usage reports now default to off when the server is silent","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/compiled-in-default-for-tengu-snoopy-creek-flipped-true","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Permission-decision usage reports now default to off when the server is silent\n\nThe setting behind usage reports on permission decisions now falls back to off instead of on when the server sends nothing\n\n**What**\n\nThe built-in fallback for `tengu_snoopy_creek` has changed from on to off. This is the remotely controlled setting tied to the usage reports Claude Code sends about each permission decision, meaning each time it decides whether a tool Claude wants to use is allowed. The fallback is only what Claude Code uses when the server sends no answer. The server decides per account whether the setting is actually on.\n\nThe last time this site checked, under an earlier release, the server answered off both for this site's own account and for a check made without any account. No check has been made under this release yet.\n\n- Flag `tengu_snoopy_creek`: Off in both readings (read for one account on one subscription tier against v2.1.312; this account: off, anonymous baseline: off, compiled default: off) 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: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}