Open Settings → Community plugins → Browse.
Search for “Harper”.
No results appear.
Also no results searching for Harper on the Obsidian plugin page Open Harper’s existing plugin page and click “Add to Obsidian”.
Obsidian cannot find/install the plugin.
I read the troubleshooting guide
Expected result
I expected to be able to install Harper
Actual result
Have not been able to install Harper
Environment
SYSTEM INFO:
Obsidian version: 1.13.7
Installer version: 1.13.7
Operating system: Darwin Kernel Version 25.6.0: Fri Jul 31 19:18:29 PDT 2026; root:xnu-12377.161.14~5/RELEASE_ARM64_T8122 25.6.0
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0
RECOMMENDATIONS:
none
Additional information
I checked the Obsidian releases repository, Harper is not present in community-plugins.json, Harper is also not present in community-plugins-removed.json
Two threads from this week look like the same bug, but they are actually two different issues, and the difference decides who you should ask for a fix.
QuickAdd really is a manifest problem. It is listed in community-plugins.json, but the manifest.json file on its default branch pointed to version 2.26.0, while the newest actual release was 2.25.0. Obsidian reads the version from the manifest and looks for a matching release tag. If it cannot find it, it will not install. This has already been diagnosed by the developer.
Harper is a completely different story. I checked the plugin registry today and here is the situation:
It is missing from community-plugins.json (which currently has 7882 entries).
It is also not in community-plugins-removed.json, which matches your findings.
The registry’s git history shows it was added in August 2024 and updated in April 2025. So it was in there, and now it is not.
This explains the symptom perfectly. The Browse window only shows what is in community-plugins.json. If a plugin is absent from that file, no amount of fixes on the plugin’s side will make it show up, because Obsidian is not even looking at its repository.
Besides, Harper’s manifest is actually fine right now. The default branch says 2.11.0, and there is a proper release tagged 2.11.0 published today with main.js and manifest.json attached. If the manifest was the issue, this would have fixed it.
So the thing to chase is the registry entry, not the plugin. That lives in the obsidianmd/obsidian-releases repository, not in Harper’s repo.
One caveat just to be completely honest: I can see that it disappeared from the list without going through the “removed” file, but I do not know why. It might have been pulled deliberately and the list simply wasn’t updated. If that is the case, it might not be coming back. It is worth asking rather than assuming, but you need to ask in the right repository.