Fix Failed to Install Anthropic Marketplace Will Retry on Next Startup

Resolve the 'failed to install Anthropic marketplace will retry on next startup' error in Claude Code with manual syncs, cache resets, and env flags.

VerifyArr

November 4, 20266 min read

Software developer workspace with dark command line terminal open on a dual monitor display.

The warning message failed to install anthropic marketplace will retry on next startup appears when the Claude Code CLI fails to download or sync the official plugin repository during session boot. The failure usually stems from read-only directory permissions, strict corporate proxies, corrupted local cache files, or an ongoing background retry loop. You can clear the alert by manually re-registering the catalog, purging cached metadata, or disabling automated startup checks entirely.

Why Claude Code Fails to Register the Plugin Catalog

Understanding what causes the error prevents repeated boot delays. When you launch the CLI, Claude Code's background process attempts to automatically download and register the default official plugin catalog.

If that background fetch encounters an interruption, the process records a failure state instead of continuing silently. Official Claude Code documentation notes that the CLI attempts to auto-register the default marketplace on startup but defers or skips the step if an organizational policy blocks the source or if an earlier attempt failed and is waiting to retry. When that happens, the tool displays the persistent retry banner on every subsequent launch.

Several distinct factors disrupt this automatic registration routine:

Write Permission Conflicts: Operating systems occasionally mark local configuration folders as read-only. For example, file permissions issues, such as Windows marketplace cache folders defaulting to read-only mode, can block successful installation of the marketplace manifest.
Network and SSL Blocks: Strict corporate firewalls, VPNs, or man-in-the-middle proxy certificates often reject the remote HTTPS call to the plugin repository.
Corrupted Local Manifests: A sudden shell termination during an update can leave half-written JSON files in your Claude configuration folder.
Phantom Alerts on Global Packages: In some environments, the failure notification triggers spuriously on global npm installations (`@anthropic-ai/claude-code`) even when plugins load with zero errors.

Comparing Fixes for the Startup Installation Error

Depending on whether your issue stems from network blocks, file lockups, or a broken manifest, you have several ways to address the startup loop. Use this summary table to choose the right fix for your developer environment:

Fix Method	Primary Cause Addressed	CLI Command or Action	Best Suited For
Manual Re-addition	Transient network drop	`/plugin marketplace add anthropics/claude-plugins-official`	Interactive sessions
Cache Purge	Corrupted local manifest	Remove cache files, then run `/plugin marketplace remove`	Broken plugin trees
Environment Variable	Blocked corporate network	Set `CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL=1`	Air-gapped or CI/CD systems
Permission Reset	OS read-only folder locks	Run `chmod -R 755 ~/.claude` or uncheck Read-only in Windows	Local permission errors

Selecting the right path saves time and gets your terminal environment operational immediately.

Step 1: Manually Register the Official Marketplace

The built-in retry routine rarely recovers on its own. As systemprompt.io reports, the automatic retry loop rarely succeeds on its own because the root cause is persistent.

To bypass the automatic startup loop, force a clean manual registration directly. You can manually add the official catalog inside a session by executing the command `/plugin marketplace add anthropics/claude-plugins-official` or by running `claude plugin marketplace add anthropics/claude-plugins-official` directly in the shell.

If the terminal returns an error stating that the catalog already exists, remove the broken pointer first. Run `/plugin marketplace remove anthropics/claude-plugins-official`, quit your session, launch Claude Code again, and re-run the add command.

Step 2: Clear Corrupted Manifests and Fix Directory Permissions

When a manual registration fails, cached local data or strict file permissions are almost always the cause. Claude Code stores marketplace definitions in your local profile directory under `.claude/plugins` or similar internal application folders.

Resetting Storage Permissions

On macOS and Linux, adjust folder privileges to ensure your user profile owns the entire Claude tree:

`chmod -R 755 ~/.claude`

On Windows, navigate to `%USERPROFILE%\.claude`, open folder properties, and verify that the Read-only checkbox is cleared across all subfolders and JSON files.

Purging Cache State

If files are writable but errors continue, delete the cached marketplace manifests completely. Close all active terminal sessions running Claude Code. Open your `.claude` directory, remove the `marketplace` and `cache` subfolders, and relaunch the tool. This forces Claude Code to re-initialize clean configurations instead of reading damaged partial downloads.

Step 3: Disable Autoinstall via Environment Variables

If your workstation operates behind a strict enterprise proxy or you develop without external internet access, automatic registry syncs will continue to fail. You can permanently suppress the startup attempt without losing existing local plugin functionality.

Official Claude Code documentation notes that the environment variable `CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL` can be set to stop the tool from attempting to auto-install the official marketplace on session startup.

To apply this across your shell sessions, add the variable to your profile file (such as `~~/.bashrc` or `~~/.zshrc`):

`export CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL=1`

On Windows systems, execute this command in PowerShell:

`[System.Environment]::SetEnvironmentVariable('CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL', '1', 'User')`

Restart your shell. Claude Code will boot cleanly into the prompt without triggering the startup network check.

Security Verification and Marketplace Integrity

When troubleshooting plugin repositories and IDE integrations, always verify the source of your CLI tools and extensions. Malicious packages frequently imitate popular developer tooling.

On October 29, 2026, Cursor disclosed a supply-chain incident affecting up to 5,000 developers where compromised third-party builds of the `Anthropic.claude-code` extension (versions 2.1.312 and 2.1.313) appeared in the Cursor Extension Marketplace. Following that disclosure, Microsoft Threat Intelligence confirmed that the tampered marketplace extension attempted to plant an attacker SSH key and establish reverse tunnels, but noted that official distributions via npm and the Microsoft Visual Studio Marketplace remained uncompromised.

Always ensure that you install Claude Code directly through official channels such as npm (`npm install -g @anthropic-ai/claude-code`) and verify that any third-party extensions in your editor come from authentic, verified publishers. Sound engineering practices and strict provenance matter just as much when building an indie SaaS or managing codebases as they do when conducting due diligence to evaluate and buy a SaaS business.

Frequently asked questions

Can I use Claude Code plugins if the official marketplace fails to auto-install?

Yes. The failure only prevents the CLI from syncing the default repository index automatically. You can install individual plugins directly from local paths, private repositories, or third-party git URLs without needing the official marketplace auto-installer.

Does setting CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL disable installed plugins?

No. Disabling the auto-install routine only stops the startup network check and suppressive retry warnings. All previously installed plugins and custom configurations continue to run normally.

Why does the error persist after running the manual marketplace add command?

If the manual add command fails, your local configuration directory is likely locked as read-only or contains a corrupt manifest. Remove the marketplace entry manually, delete the local cache folder, and verify write permissions before re-adding.

How do I confirm whether the official plugin catalog is registered?

Inside an active Claude Code session, enter `/plugin marketplace list`. If the official repository is active, it will appear in the output list alongside its sync status and available plugins.