Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.0.12 Home All releases olderv2.0.11 v2.0.13newer
Claude Code v2.0.12

Inline Plugin Commands

What: Plugin developers can now define commands directly in their manifest with inline markdown content

How to use: In your plugin's marketplace-manifest.json:

{
  "commands": {
    "hello": {
      "content": "---\ndescription: Say hello\n---\n\nGreet the user warmly!",
      "description": "Greet the user",
      "argumentHint": "[name]"
    },
    "status": {
      "source": "commands/status.md"
    }
  }
}

Details:

  • Commands can now use object notation with content (inline) or source (file path) fields
  • Cannot use both content and source - validation enforces one or the other
  • Supports metadata overrides: description, argumentHint, model, allowedTools
  • Reduces file clutter for simple commands
  • Old array-of-paths format still supported for backward compatibility
  • Evidence: Command schema with content field at lines 42750-42775 in schema definition, inline content processing in plugin loader at lines 48817-48850

See this entry in the whole of v2.0.12 →