Claude Code Plugins Now Auto-Load from .claude/skills
Claude Code v2.1.157 removes the marketplace gate for local plugins: any plugin placed in a .claude/skills directory is now automatically loaded at session start, with no marketplace registration or install command. A new claude plugin init
Sources & Mentions
5 external resources covering this update
Local Plugins Go Marketplace-Free
Claude Code v2.1.157, released on May 29, 2026, delivers a significant quality-of-life improvement for developers who build or maintain custom Claude Code extensions. Plugins stored in a .claude/skills directory are now automatically discovered and loaded when a session starts, with no marketplace registration, no claude plugin install step, and no configuration required.
Previously, distributing a custom plugin to a team or using a locally developed extension required either publishing to a marketplace or manually adding it through plugin management commands. The new auto-load behavior treats .claude/skills as a first-class local plugin directory, bringing the experience closer to how most developers expect local tooling to work: drop it in the right place, and it works.
Scaffold New Plugins with claude plugin init
Alongside auto-loading, Anthropic introduced claude plugin init <name>, a command that scaffolds a complete plugin structure inside .claude/skills/<name>/. The command generates the standard plugin directory layout including a plugin.json manifest, and placeholder directories for skills, agents, hooks, and MCP server definitions.
The scaffolding command lowers the barrier to authoring plugins considerably. Instead of manually creating the directory structure and consulting documentation on required file formats, developers can run a single command and begin customizing immediately. The combination of claude plugin init for creation and automatic loading for consumption creates a tight local development loop.
Autocomplete for /plugin Arguments
Version 2.1.157 also adds tab-completion for /plugin command arguments, including subcommands, names of installed plugins, and plugins available from known marketplaces. This makes navigating and managing the growing plugin ecosystem faster without requiring users to remember exact plugin identifiers.
Worktree Flexibility: Switch Between Claude-Managed Worktrees Mid-Session
A second meaningful improvement in this release is that EnterWorktree can now switch between Claude-managed worktrees within the same session. Previously, entering a worktree was a one-way move for the duration of a session. With this change, Claude can navigate between multiple isolated worktrees as a task evolves, without requiring the user to start a new session or manually manage worktree state.
Key Takeaways
- Plugins in
.claude/skillsnow load automatically, eliminating the need to register or install local plugins through a marketplace, making team-level and personal extensions far easier to use. claude plugin init <name>scaffolds a complete plugin in seconds, generating the full directory structure and manifest so developers can start building immediately.- The local authoring loop is now fully self-contained: create with
plugin init, iterate with/reload-skills, and the plugin is available to every session in that project automatically. - Tab-completion for
/pluginarguments reduces friction when managing a growing library of plugins. EnterWorktreecan now switch between Claude-managed worktrees mid-session, enabling more fluid multi-branch workflows without restarting a session.