Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One change · claude-code

Plugins reference changed

plugins-reference

Nearest release: v2.1.280, published 13 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+10added
Lines−3removed
From line 65 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits36to this page, all time

The whole hunk

from line 65, old and new numbered
/
lines
from line 65
6565 
6666For security reasons, plugin-shipped agents don't support `hooks`, `mcpServers`, or `permissionMode`.
6767 
68You can put plugin agent files in subfolders of `agents/`. Claude Code [loads them recursively](/docs/en/sub-agents#choose-the-subagent-scope) and joins the plugin name, each subfolder name, and the file name with colons to form the agent's scoped name. For example, `agents/review/security.md` in a plugin named `my-plugin` loads as `my-plugin:review:security`. Two settings change that name:
69 
70* Frontmatter `name`: it replaces only the file name, so `name: audit` in `agents/review/security.md` loads as `my-plugin:review:audit`
71* Manifest [`agents`](#component-path-fields) field: a file you list there loads without subfolder names, so `"agents": "./custom/review/security.md"` loads as `my-plugin:security`
72 
6873Claude Code loads a plugin agent even when its frontmatter has no `name` or doesn't parse:
6974 
7075* No `name`: Claude Code names the agent after the file, so `agents/reviewer.md` in a plugin named `my-plugin` loads as `my-plugin:reviewer`
from line 686
681686* All paths must be relative to the plugin root and start with `./`, except that the `skills` field also accepts `"."`
682687 * Both `"."` and `"./"` denote the plugin root itself
683688 * Before v2.1.221, `"."` failed manifest validation and the plugin didn't load, so use `"./"` to support earlier versions
684* Components from custom paths use the same naming and namespacing rules
689* Components from custom paths use the same naming and namespacing rules, except agent files. See [Agents](#agents) for how agent names work
685690* Multiple paths can be specified as arrays
686691* A skill path can point to a directory that contains a `SKILL.md` directly, for example `"skills": ["."]` for the plugin root
687692 * Claude Code takes the skill's invocation name from the frontmatter `name` field in `SKILL.md`, so the name stays stable whatever the install directory is named
from line 909
904909├── agents/ # Subagent definitions
905910│ ├── security-reviewer.md
906911│ ├── performance-tester.md
907└── compliance-checker.md
912├── compliance-checker.md
913│ └── review/ # Agents here load as enterprise-plugin:review:<name>
914│ └── accessibility.md
908915├── workflows/ # Workflow scripts
909916│ └── release-audit.js
910917├── output-styles/ # Output style definitions
from line 949
942949| **Manifest** | `.claude-plugin/plugin.json` | Plugin metadata and configuration (optional) |
943950| **Skills** | `skills/` | Skills with `<name>/SKILL.md` structure |
944951| **Commands** | `commands/` | Skills as flat Markdown files. Use `skills/` for new plugins |
945| **Agents** | `agents/` | Subagent Markdown files |
952| **Agents** | `agents/` | Subagent Markdown files. Subfolders are part of the [agent name](#agents) |
946953| **Workflows** | `workflows/` | [Workflow](/docs/en/workflows) script files |
947954| **Output styles** | `output-styles/` | Output style definitions |
948955| **Themes** | `themes/` | Color theme definitions |
Feedback