{"version":"2.1.285","anchor":"a-model-restriction-helper-is-stubbed-to-always-return-false","canonical_anchor":"a-model-restriction-helper-is-stubbed-to-always-return-false","heading":"Usage data labels model restrictions as coming from an allowlist more often","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/a-model-restriction-helper-is-stubbed-to-always-return-false","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Usage data labels model restrictions as coming from an allowlist more often\n\nA check in how Claude Code reports where a model restriction came from now always gives the same answer\n\n**Unclear.** Whether this check is newly disabled in this release is not established.\n\n**What**\n\nWhen a model restriction is set, Claude Code records where it came from. One check that used to tell the cases apart now always gives the same answer, so the restriction is labelled as coming from an allowlist in more cases.\n\n**Why**\n\nThis affects only the usage data Claude Code reports, not which models you can use.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}