{"version":"2.1.299","anchor":"settings-env-plugin-loading-and-project-listing-tweaks","canonical_anchor":"settings-env-plugin-loading-and-project-listing-tweaks","heading":"Project command listing no longer filters commands by where they came from","tier":"notice","area":"Slash Commands","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/settings-env-plugin-loading-and-project-listing-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Project command listing no longer filters commands by where they came from\n\nListing project commands no longer refuses a command because of where it was loaded from, and refusal messages now name the command\n\n**Unclear.** It is not clear which commands now appear in the project command list that were refused before.\n\n**What**\n\nWhen Claude Code lists a project's commands, it no longer turns a command away because of where that command was loaded from. If it does refuse a command, its log message now names the command rather than the place it came from.\n\nA plugin loaded from a path given inline can also now have that path replaced by an attestation value.\n\n**Why**\n\nThis is a small behaviour change to how project commands and inline plugins are loaded.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}