Update All Plugins

One-shot command that upgrades every installed plugin from all configured marketplaces and syncs memory palace knowledge. This command reads the installed plugins configuration, updates each plugin individually, and processes any queued research into palaces.

When To Use

• After receiving marketplace-wide security fixes or compatibility updates
• Before running regression suites that depend on latest plugins
• To avoid manually updating each plugin individually
• When you want to validate all plugins are at their latest versions
• To process accumulated research from sessions into memory palaces

When NOT To Use

• Project doesn't use the leyline infrastructure patterns
• Simple scripts without service architecture needs

Workflow

The command executes the Python script at scripts/update_all_plugins.py which:

1. Read installed plugins

• Parses ~/.claude/plugins/installed_plugins_v2.json
• Extracts plugin names and their marketplaces
• Groups plugins by marketplace for efficient processing

1. Update plugins by marketplace

• For each plugin, runs: claude plugin update {plugin}@{marketplace}
• Handles update responses and tracks success/failure
• Continues updating even if some plugins fail

1. Sync memory palace knowledge (if memory-palace is installed)

• Processes data/intake_queue.jsonl into palaces
• Matches queued research to existing palaces by domain/tags
• Creates new entries in appropriate palace districts
• Reports items processed and palaces updated

1. Garden tending with palace check (if memory-palace is installed)

• Runs garden tend --palaces to check both garden plots and palace entries
• Identifies stale/overgrown garden plots needing attention
• Checks palace entries for staleness, low quality, duplicates
• Prompts for user approval before any cleanup operations
• Use --apply only after reviewing recommendations

1. Report results

• Counts total plugins checked, updated, and already latest
• Lists specific plugins that were updated with version changes
• Reports any failures with error messages
• Shows palace sync results (items processed, palaces updated)
• Shows prune recommendations (if any)
• Notes if restart is required for changes to take effect

Implementation Notes

• The script reads the actual installed plugins configuration file
• Each plugin is updated with its full marketplace identifier: {plugin}@{marketplace}
• No --all flag exists for the native update command, so we iterate through each plugin
• The script handles both versioned plugins (e.g., "1.2.1") and commit-based plugins (e.g., "ddbd034ca35c")
• Output is formatted without emojis for better compatibility with different terminals

Options

This command currently has no options. It updates all plugins from all marketplaces.

Notes

• Requires network access to check for updates
• Use /reload-plugins (2.1.69+) to activate pending plugin changes without restarting Claude Code. For older versions, a full restart is still required.
• The command will continue updating even if some plugins fail
• Updates are applied at the user scope by default
• If updates fail with git timeout errors, set CLAUDE_CODE_PLUGIN_GIT_TIMEOUT_MS (default: 120s, increased from 30s in 2.1.51)

For a full log of Claude Code plugin system changes, see plugins/abstract/docs/compatibility/.

• Fixed: LSP servers not registering when the LSP Manager initialized before marketplace reconciliation completed (2.1.76+)
• --plugin-dir now accepts only one path per flag invocation (2.1.76+). Use repeated --plugin-dir for multiple directories. Previously accepted colon-separated paths.
• Fixed: git-subdir plugins at different subdirectories of the same monorepo commit no longer collide in the plugin cache (2.1.77+)
• claude plugin validate now checks skill, agent, and command frontmatter plus hooks/hooks.json, catching YAML parse errors and schema violations (2.1.77+). Previously only checked plugin.json structure.
• Headless mode plugin installation now composes correctly with CLAUDE_CODE_PLUGIN_SEED_DIR for containerized environments (2.1.77+)