{"version":"2.1.267","anchor":"stats-dialog-now-requires-an-allowed-permission-check","canonical_anchor":"stats-dialog-now-requires-an-allowed-permission-check","heading":"Stats dialog now requires an \"allowed\" permission check","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/stats-dialog-now-requires-an-allowed-permission-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Stats dialog now requires an \"allowed\" permission check\n\nThe stats dialog now checks a permission flag before loading usage stats\n\n**Unclear.** The finding does not say under what conditions `allowed` would be false or what reasons might be shown.\n\n**What**\n\nThe dialog that shows usage statistics (similar to the `\/stats` command) now first checks whether it is allowed to load, using an `allowed`\/`reason` pair from a store. If it isn't allowed, it shows the given reason text instead of fetching and displaying all-time and active-time usage figures.\n\n**Why**\n\nThis lets Claude Code hold back the stats dialog for certain accounts or situations and show an explanation instead, rather than always loading usage data.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}