Hey, thanks for the detailed report with the screenshot and the staleness breakdown, it really helps. Your intuition is right: Update/Reinstall reinstalls the same local snapshot instead of pulling the latest commit from GitHub.
This is a known bug and we can reproduce it on our side. A personal marketplace added via /add-plugin with a GitHub URL gets pinned to the commit that was current when it was first added, and re-adding it or using Update/Reinstall won’t move it forward. So it’s not your config.
The most reliable workaround right now is to install the plugin as a local development plugin: clone the repo locally and put it in ~/.cursor/plugins/local/<plugin-name> (or symlink that folder to your local checkout). That path indexes the plugin from disk as it is right now and bypasses the stuck marketplace cache. Clearing ~/.cursor/plugins/cache and ~/.cursor/plugins/marketplaces doesn’t reliably move the pin, so don’t count on that.
I can’t share an ETA for a fix yet, but I’ll attach your report to the issue. Once there’s an update, I’ll reply in the thread. The same problem is discussed here, you can subscribe: /add-plugin GitHub imports can get stuck on stale plugin versions