{"version":"2.1.163","anchor":"plugin-list-enabled-and-disabled-filters","canonical_anchor":"plugin-list-enabled-and-disabled-filters","heading":"\/plugin list --enabled and --disabled Filters","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.163\/e\/plugin-list-enabled-and-disabled-filters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.163","markdown":"### \/plugin list --enabled and --disabled Filters\n\n**What**\n\nThe `\/plugin list` command now accepts `--enabled` and `--disabled` flags to filter the output to only installed plugins matching the requested state.\n\n**Usage**\n\n`\/plugin list --enabled # show only enabled plugins \/plugin list --disabled # show only disabled plugins \/plugin list # show all installed plugins (unchanged)` **Details** - Enabled\/disabled status is shown as `\u2713 enabled` or `\u2717 disabled` per plugin entry. - If no plugins match the filter, a short message like \"No disabled plugins.\" is shown. - Plugin entries also show version and scope where available. - A pending-reload indicator `\u2014 run \/reload-plugins to apply` appears when the in-memory state differs from what would be loaded on next start. **Evidence** Filter flag in command rendering (search for `\"\/plugin list [--enabled|--disabled] - List installed plugins\"`)"}