|
|
|
|
@@ -108,6 +108,7 @@ my-plugin/
|
|
|
|
|
├── .lsp.json # LSP server configurations for code intelligence
|
|
|
|
|
├── bin/ # Executables added to Bash tool's PATH while plugin is enabled
|
|
|
|
|
├── settings.json # Default settings applied when plugin is enabled (currently only `agent` key supported)
|
|
|
|
|
├── themes/ # Optional: ship custom Claude Code themes (v2.1.118+)
|
|
|
|
|
├── templates/
|
|
|
|
|
│ └── issue-template.md
|
|
|
|
|
├── scripts/
|
|
|
|
|
@@ -478,9 +479,25 @@ Enterprise and advanced users can control marketplace behavior through settings:
|
|
|
|
|
| Setting | Description |
|
|
|
|
|
|---------|-------------|
|
|
|
|
|
| `extraKnownMarketplaces` | Add additional marketplace sources beyond the defaults |
|
|
|
|
|
| `strictKnownMarketplaces` | Control which marketplaces users are allowed to add |
|
|
|
|
|
| `strictKnownMarketplaces` | Control which marketplaces users are allowed to add (managed-only) |
|
|
|
|
|
| `blockedMarketplaces` | Admin-managed blocklist of marketplaces (supports `hostPattern` / `pathPattern` regex fields since v2.1.119) |
|
|
|
|
|
| `deniedPlugins` | Admin-managed blocklist to prevent specific plugins from being installed |
|
|
|
|
|
|
|
|
|
|
> **Enforcement** (v2.1.117+): `blockedMarketplaces` and `strictKnownMarketplaces` are enforced on every plugin lifecycle event — install, update, refresh, and autoupdate — not just at first add. `strictKnownMarketplaces` is managed-only.
|
|
|
|
|
|
|
|
|
|
Example `blockedMarketplaces` with host/path regex (v2.1.119):
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
{
|
|
|
|
|
"blockedMarketplaces": [
|
|
|
|
|
{
|
|
|
|
|
"hostPattern": "^evil\\.example\\.com$",
|
|
|
|
|
"pathPattern": "^/marketplaces/.*"
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
### Additional Marketplace Features
|
|
|
|
|
|
|
|
|
|
- **Default git timeout**: Increased from 30s to 120s for large plugin repositories
|
|
|
|
|
@@ -629,8 +646,11 @@ claude plugin list # List installed plugins
|
|
|
|
|
claude plugin enable <name> # Enable a disabled plugin
|
|
|
|
|
claude plugin disable <name> # Disable a plugin
|
|
|
|
|
claude plugin validate # Validate plugin structure
|
|
|
|
|
claude plugin tag <version> # Create a release git tag with version validation (v2.1.118+)
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Example: `claude plugin tag v0.3.0` validates the version format, creates the matching git tag, and is the recommended way to cut plugin releases for distribution.
|
|
|
|
|
|
|
|
|
|
## Installation Methods
|
|
|
|
|
|
|
|
|
|
### From Marketplace
|
|
|
|
|
@@ -722,7 +742,8 @@ Administrators can control plugin behavior across an organization using managed
|
|
|
|
|
| `enabledPlugins` | Allowlist of plugins that are enabled by default |
|
|
|
|
|
| `deniedPlugins` | Blocklist of plugins that cannot be installed |
|
|
|
|
|
| `extraKnownMarketplaces` | Add additional marketplace sources beyond the defaults |
|
|
|
|
|
| `strictKnownMarketplaces` | Restrict which marketplaces users are allowed to add |
|
|
|
|
|
| `strictKnownMarketplaces` | Restrict which marketplaces users are allowed to add (managed-only; enforced on every plugin lifecycle event since v2.1.117) |
|
|
|
|
|
| `blockedMarketplaces` | Blocklist of marketplaces; enforced on every plugin lifecycle event since v2.1.117; supports `hostPattern` / `pathPattern` regex fields since v2.1.119 |
|
|
|
|
|
| `allowedChannelPlugins` | Control which plugins are permitted per release channel |
|
|
|
|
|
|
|
|
|
|
These settings can be applied at the organization level via managed configuration files and take precedence over user-level settings.
|
|
|
|
|
@@ -745,10 +766,11 @@ This ensures that plugins cannot escalate privileges or modify the host environm
|
|
|
|
|
2. Write `.claude-plugin/plugin.json` manifest
|
|
|
|
|
3. Create `README.md` with documentation
|
|
|
|
|
4. Test locally with `claude --plugin-dir ./my-plugin`
|
|
|
|
|
5. Submit to plugin marketplace
|
|
|
|
|
6. Get reviewed and approved
|
|
|
|
|
7. Published on marketplace
|
|
|
|
|
8. Users can install with one command
|
|
|
|
|
5. Tag the release with `claude plugin tag v0.3.0` (v2.1.118+) — validates the version string and creates the matching git tag
|
|
|
|
|
6. Submit to plugin marketplace
|
|
|
|
|
7. Get reviewed and approved
|
|
|
|
|
8. Published on marketplace
|
|
|
|
|
9. Users can install with one command
|
|
|
|
|
|
|
|
|
|
**Example submission:**
|
|
|
|
|
|
|
|
|
|
@@ -968,10 +990,12 @@ The following Claude Code features work together with plugins:
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
**Last Updated**: April 16, 2026
|
|
|
|
|
**Claude Code Version**: 2.1.112
|
|
|
|
|
**Last Updated**: April 24, 2026
|
|
|
|
|
**Claude Code Version**: 2.1.119
|
|
|
|
|
**Sources**:
|
|
|
|
|
- https://docs.anthropic.com/en/docs/claude-code/plugins
|
|
|
|
|
- https://www.anthropic.com/news/claude-opus-4-7
|
|
|
|
|
- https://support.claude.com/en/articles/12138966-release-notes
|
|
|
|
|
- https://code.claude.com/docs/en/plugins
|
|
|
|
|
- https://code.claude.com/docs/en/plugin-marketplaces
|
|
|
|
|
- https://github.com/anthropics/claude-code/releases/tag/v2.1.117
|
|
|
|
|
- https://github.com/anthropics/claude-code/releases/tag/v2.1.118
|
|
|
|
|
- https://github.com/anthropics/claude-code/releases/tag/v2.1.119
|
|
|
|
|
**Compatible Models**: Claude Sonnet 4.6, Claude Opus 4.7, Claude Haiku 4.5
|
|
|
|
|
|
Luong NGUYEN