{"version":"2.1.283","anchor":"api-metrics-opt-out-status-cache-is-now-per-principal","canonical_anchor":"api-metrics-opt-out-status-cache-is-now-per-principal","heading":"The metrics opt-out check is now remembered separately for each account","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/api-metrics-opt-out-status-cache-is-now-per-principal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### The metrics opt-out check is now remembered separately for each account\n\nClaude Code now caches whether metrics are enabled separately for each account and organisation, so switching accounts cannot reuse another's answer\n\n**What**\n\nClaude Code checks whether metrics collection is enabled and remembers the answer. That answer used to be stored once for everyone. It is now stored separately for each principal, meaning the signed-in account and organisation, or an API key identified by a hash.\n\n- At most 8 answers are kept.\n\n- Saving a new answer clears the old shared one.\n\n- The stored answers are cleared when your identity changes.\n\n- If the account changes while a check is still running, that result is thrown away, logged as an error, and metrics are treated as disabled for it.\n\n**Why**\n\nAfter you switch accounts or organisations, one account's metrics opt-out setting can no longer be applied to another.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}