{"version":"2.1.233","anchor":"plugin-subcommand-help-now-comes-from-one-table-with-eval-co","canonical_anchor":"plugin-subcommand-help-now-comes-from-one-table-with-eval-co","heading":"Plugin subcommand help now comes from one table, with eval commands hidden","tier":"soon","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/plugin-subcommand-help-now-comes-from-one-table-with-eval-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Plugin subcommand help now comes from one table, with eval commands hidden\n\nPlugin subcommand help now comes from one table, with eval commands hidden by default.\n\n**What**\n\nEvery `claude plugin ...` subcommand takes its usage line, aliases and description from a single registry instead of inline strings. Entries marked as early access, currently `eval` and `eval init`, are filtered out of the listing unless early access is switched on, which it is not by default in this build.\n\n**Details**\n\n- Visibility of the eval commands is decided by a server-side flag with an off fallback, overridable locally with `CLAUDE_CODE_WALNUT_SPIRE`.\n\n**Evidence**\n\n`earlyAccess: \"pluginEval\"`\n\n- Area: Plugins\n- Names: `claude plugin`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}