{"version":"2.0.12","anchor":"inline-plugin-commands","canonical_anchor":"inline-plugin-commands","heading":"Inline Plugin Commands","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.12\/e\/inline-plugin-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.12","markdown":"### Inline Plugin Commands\n\n**What:** Plugin developers can now define commands directly in their manifest with inline markdown content\n\n**How to use:** In your plugin's `marketplace-manifest.json`:\n\n`{ \"commands\": { \"hello\": { \"content\": \"---\\ndescription: Say hello\\n---\\n\\nGreet the user warmly!\", \"description\": \"Greet the user\", \"argumentHint\": \"[name]\" }, \"status\": { \"source\": \"commands\/status.md\" } } }` **Details:**\n\n- Commands can now use object notation with `content` (inline) or `source` (file path) fields\n- Cannot use both `content` and `source` - validation enforces one or the other\n- Supports metadata overrides: `description`, `argumentHint`, `model`, `allowedTools`\n- Reduces file clutter for simple commands\n- Old array-of-paths format still supported for backward compatibility\n- **Evidence**: Command schema with `content` field at lines 42750-42775 in schema definition, inline content processing in plugin loader at lines 48817-48850"}