Published on

Claude Code Plugin Ecosystem Arrives β€” v2.1.129, Custom Themes, and Project Purge

Imagine assembling an AI coding tool like Lego bricks β€” snapping in exactly the pieces you need.

On May 6, 2026, Anthropic shipped Claude Code v2.1.129 and that vision moved considerably closer to reality. Install a new capability with a single plugin URL. Apply a custom color theme via /theme. Wipe a project's entire history with claude project purge. And do it all knowing Anthropic now runs an official, curated plugin directory behind the scenes.

This is not a routine patch. It is a statement: Claude Code is evolving from a personal tool into an extensible platform.

What Changed in v2.1.129

1. --plugin-url <url> β€” Install a Plugin from a Single URL

Claude Code plugin-url install placeholder

Previously, adding a plugin meant local file installation or manual configuration. From v2.1.129, one line does it:

claude --plugin-url https://example.com/my-plugin.zip

Claude Code fetches the .zip archive from the URL and loads it for the current session. Sharing plugins with teammates or pulling from an external marketplace is now frictionless.

Anthropic also launched the Official Claude Plugins Directory (claude-plugins-official) β€” a curated, Anthropic-reviewed collection of high-quality plugins. Think of it as an App Store that Anthropic itself vets.

Like a marketplace for Lego sets, Claude Code now lets you drop any verified block onto your workbench.

2. Custom Themes β€” Build Your Color Palette with /theme

Claude Code custom theme palette placeholder

The assumption that terminals must be black-and-green is officially optional. v2.1.129 lets you create, save, and share custom color themes.

Two ways to do it:

MethodDescription
/theme commandCreate and switch themes directly inside the terminal
Hand-edit JSONSave a palette JSON to ~/.claude/themes/

Plugin developers can ship themes alongside their plugin by including a themes/ directory in the package.

From an EdTech perspective, visual separation between contexts genuinely helps productivity. Keeping student code-review sessions in one color scheme and personal projects in another reduces the mental cost of switching.

3. claude project purge β€” Full Project State Reset

claude project purge command placeholder

Claude Code accumulates transcripts, task lists, file history, and config entries as you work. Sometimes those traces become a burden β€” stale state from an old project, or sensitive conversations that need removing.

claude project purge [path]

This deletes all Claude Code state for a specified project.

Key options:

FlagFunction
--dry-runPreview what would be deleted without deleting anything
-y / --yesSkip confirmation and delete immediately
-i / --interactiveChoose which items to delete one by one
--allPurge state for every project at once

Always run --dry-run first. Deletion is irreversible.

4. MCP Server Reliability β€” 3 Auto-Retries on Startup

When an MCP (Model Context Protocol) server hit a transient error on startup, it previously stayed disconnected. Now Claude Code automatically retries up to three times. Integrations with Notion, GitHub, and other MCP-connected services are significantly more resilient on unstable networks.

5. Gateway Model Auto-Discovery β€” /model Picker Upgrade

When ANTHROPIC_BASE_URL points to an Anthropic-compatible gateway, the /model picker now automatically fetches the available model list from that gateway's /v1/models endpoint. Teams running private AI gateways can now switch models inside Claude Code without any extra configuration.

6. Session Recaps and Fullscreen Scroll Fix

Two small improvements that matter every day:

  • Session recaps: When you step away and return, Claude Code shows you exactly what it did while you were gone.
  • Fullscreen scroll stays put: Previously, scrolling up in fullscreen mode caused the view to snap back to the bottom. Now the position holds where you left it.

What This Update Really Means

Three observations from an EdTech CEO who uses Claude Code daily.

First, Claude Code became a platform. The URL-based plugin installation and the official Anthropic directory signal an ecosystem strategy. Until now, Claude Code was a single Anthropic-built tool. Now it invites external developers to extend it.

Second, the move toward team collaboration is accelerating. Shareable custom themes, distributable plugin URLs, and more reliable MCP connections all point toward team use rather than solo use. EdTech teams can now maintain a shared, consistent Claude Code environment.

Third, the design is reaching beyond developers. /theme, --plugin-url, and the /model picker are all accessible without deep CLI knowledge. Claude Code appears to be lowering the barrier for non-developers deliberately.

Tips

1. Always dry-run before purging Run claude project purge --dry-run first to review what will be removed before committing.

2. Share theme JSON through a team repo Put your team's ~/.claude/themes/*.json files in a shared Git repository so everyone works in the same visual environment.

3. Use the official directory first Before installing any third-party plugin, check claude-plugins-official. Anthropic-reviewed plugins carry meaningful trust guarantees.

4. MCP reconnection is now mostly automatic The 3-retry behavior means you rarely need to manually restart an MCP server after a transient failure.

Claude Code is accelerating its platform ambitions. You do not have to adopt every new feature today β€” but watching how this ecosystem grows is itself an important form of AI literacy.

Related Posts

Sources

Discuss on Twitter β€’ View on GitHub
Claude Code Plugin Ecosystem Arrives β€” v2.1.129, Custom Themes, and Project Purge | MINSSAM.COM