Feed
771views

Claude Pro: personal marketplace “already added” but invisible in UI — plugin stuck on an old version

Hi everyone,

I’m developing SkillPilot, a curriculum-guided learning coach, and its Claude plugin combining MCP, an interactive UI, and Skills. I’m trying to establish a straightforward installation and update workflow for beta testers using their own Claude accounts.

I’m currently stuck with a personal GitHub marketplace on my Claude Pro account. This concerns Claude’s plugin-management UI, not the Claude Code CLI or Team/Enterprise administration.

Marketplace: https://github.com/enpasos/skillpilot-claude-marketplace

Plugin: SkillPilot Coach v1 (skillpilot-coach-v1) Version currently in the repository: 1.1.1 Version Claude still shows after reinstalling: 1.0.4

What happened

I added the marketplace and successfully installed version 1.0.4.

I then published version 1.1.1 to the repository, but Claude continued to show the installed plugin as 1.0.4. I uninstalled the plugin to try a fresh installation.

When I tried adding the marketplace again, Claude rejected it with the German message “Dieser Marketplace wurde bereits hinzugefügt” — “This marketplace has already been added.” Clicking “Synchronisieren” (“Sync”) made no observable difference.

I could find the plugin again under “Entdecken” (“Discover”) and reinstall it, but Claude still showed version 1.0.4.

The part I cannot resolve

The marketplace itself has never appeared as a manageable source in my UI — including before I uninstalled the plugin.

Claude therefore seems to recognize the existing registration, but I cannot find an entry through which I can inspect, refresh, or remove it. Re-adding the same repository is blocked.

The official help article Use plugins in Claude, under Add or remove plugin marketplaces, describes removing a marketplace through its menu in the Plugins section. I cannot find the marketplace entry needed to follow that procedure. ([Claude Hilfecenter][1])

Repository details

The repository is public. On main, the file

plugins/skillpilot-coach-v1/.claude-plugin/plugin.json

declares "version": "1.1.1".

The catalog at .claude-plugin/marketplace.json points to "source": "./plugins/skillpilot-coach-v1". The version is declared in the plugin manifest rather than duplicated in the marketplace entry.

This looks consistent with stale marketplace or plugin metadata, but I have not established the underlying cause.

Questions

  • Where should a personally added GitHub marketplace appear for a Pro user, and how can I remove or reset its registration when that entry is missing?
  • Is there a supported way to force Claude to fetch the current repository state rather than reinstalling the version it already knows about?
  • Has anyone encountered this combination of “already added,” no visible marketplace entry, and an outdated plugin version? Is there a refresh step or repository requirement I am missing?

I’d appreciate a concrete workflow that has worked on a personal Pro or Max account, or pointers to an existing bug report.

pluginsmarketplaceclaude-proplugin-updatestroubleshooting
Comment1

Discussion

1

Update: marketplace controls found; auto-sync questions remain*

On my personal Claude Pro account I found: Plugins → Add → Manage marketplaces → ⋮

The menu offers Check for updates, Automatically sync, and Remove. Removing a marketplace also uninstalls its plugins. The missing-controls question is resolved for me.

Before finding this, re-adding https://github.com/enpasos/skillpilot-claude-marketplace?v=2 made 1.1.1 appear as current. The Contents tab now shows both 1.0.4 and 1.1.1. I haven't established whether the workaround created another marketplace registration.

Auto-sync and GitHub permissions

Claude says auto-sync requires the Claude GitHub App to have repository access. The authorization screen allows selecting specific repositories, but requests read/write access to code, workflows, Actions, checks, issues, discussions, pull requests and repository hooks.

Could someone from Anthropic clarify:

  1. Sync triggers: For personal marketplaces, does a push to the default branch trigger sync, or is a merged PR and/or plugin version bump required? When do installed plugins adopt the synced update?

  2. Publisher vs. users: Is installing the GitHub App on the publisher's repository sufficient for users on separate Pro accounts to receive automatic updates, without connecting GitHub themselves?

  3. Least privilege: Why are code/workflow write permissions requested for marketplace synchronization? Is a narrower permission set available?

This concerns Claude Web on personal Pro accounts, not the Claude Code CLI or organization-managed marketplaces. I'm trying to establish a reliable update workflow for our beta testers with minimal GitHub access.