{"version":"2.1.267","anchor":"new-insights-or-similar-command-gated-by-allow-insights-p","canonical_anchor":"new-insights-or-similar-command-gated-by-allow-insights-p","heading":"New \/insights (or similar) command gated by allow_insights policy","tier":"use","area":"Insights","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-insights-or-similar-command-gated-by-allow-insights-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New \/insights (or similar) command gated by allow_insights policy\n\nNew \/insights command, gated by an allow_insights policy, generates a report on your Claude Code usage\n\n**What**\n\nA new `\/insights` command generates an HTML report analyzing your recent Claude Code sessions on this machine: which projects you work in, how you use Claude Code, where things go wrong, and features to try. It's controlled by a policy called `allow_insights` and is not available in cloud sessions.\n\n**Why**\n\nThis gives users a way to review their own usage patterns and discover underused features, while administrators can control access to it via the `allow_insights` policy.\n\n- Area: Insights\n- Names: `\/insights`, `allow_insights`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}