{"version":"2.1.290","anchor":"fewer-permission-prompts-skill-now-forbids-allowlisting-pyri","canonical_anchor":"fewer-permission-prompts-skill-now-forbids-allowlisting-pyri","heading":"Permission suggestions no longer propose allowing pyright","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/fewer-permission-prompts-skill-now-forbids-allowlisting-pyri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Permission suggestions no longer propose allowing pyright\n\nThe skill that suggests permission rules to cut down prompts is now told never to allow pyright, since it starts Python in your folder\n\n**Unclear.** Whether Claude Code's own command checker still lets some pyright commands through automatically is not settled.\n\n**What**\n\nA skill is a packaged set of instructions that Claude Code can follow. The built-in skill that suggests permission rules, so that you are asked for permission less often, now carries a rule never to propose allowing tools that start an interpreter (a program that runs code) in the working folder. `pyright` in any form is the named case.\n\n`pyright` was previously listed as allowed automatically when used with safe options. It is no longer on that list.\n\n**Why**\n\n`pyright` starts Python in the current folder, and Python looks for code to load in that folder first. A rule allowing it could let code sitting in the project run without you being asked.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}