{"version":"2.1.281","anchor":"command-frontmatter-overrides-helper","canonical_anchor":"command-frontmatter-overrides-helper","heading":"Command frontmatter overrides helper","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/command-frontmatter-overrides-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Command frontmatter overrides helper\n\nCommand overrides can now replace a command's description, argument hint, model and allowed tools, and plugin commands are merged into the list\n\n**Unclear.** The finding does not say where overrides come from or how a merged plugin command is combined with an existing one.\n\n**What**\n\nA command's frontmatter is the short block of settings at the top of its file. A new helper takes an override and copies four of its values into that frontmatter:\n\n- `description`\n\n- `argumentHint`, written as `argument-hint`\n\n- `model`\n\n- `allowedTools`, written as `allowed-tools`\n\nSeparately, commands that come from plugins are now merged into the command list instead of being added to the end of it.\n\n**Why**\n\nAn override can change how a command is described, which model it uses and which tools it may use, without editing the command file itself. Because plugin commands are now merged into the list rather than tacked on, a plugin command no longer simply sits alongside an existing command of the same kind."}