K0324-j192 downloadsEdit community plugin enablement across multiple config profiles.
Profile Manager is a desktop plugin for comparing and editing enabled community plugins across multiple configuration profiles.
It is designed for vaults that use separate configuration folders for different devices or workflows.

community-plugins.json.Profile Manager reads plugin manifests from registered profile folders and writes to each profile's community-plugins.json when you save changes.
It can also copy or remove plugin folders inside registered profile folders when you explicitly use install or uninstall actions.
Automatic backup restore is planned for a future release.
Before saving changes, the plugin creates backups under:
.obsidian/plugins/plugin-profile-manager/backups/community-plugins/
.obsidian/plugins/plugin-profile-manager/backups/plugin-uninstall/
If a profile's community-plugins.json is invalid, saving is blocked for safety.
Changes to the currently running profile are applied immediately after saving when possible. Other profiles may require restarting Obsidian on that device.
Privacy mode replaces plugin names, plugin identifiers, profile names, and profile folder labels with generic labels.
While privacy mode is on, actions that would edit, install, uninstall, or save plugin profile changes do nothing. This makes it safer to take screenshots, record demos, or attach issue reports without exposing your real plugin list.
Privacy mode is not a security boundary. It is a screenshot and demo helper.
Profile Manager: Open manager.Backup and save to write changes.Profile Manager is marked as desktop-only because it manages local configuration folders and plugin directories from a desktop vault.
Mobile Obsidian is not supported.
Bug reports and feature requests are welcome through GitHub Issues. Support is best effort.
Pull requests are welcome, but please open an issue first for larger changes.
When sharing screenshots, enable privacy mode first.
npm install
npm run lint
npm run build
GitHub releases should attach:
main.jsmanifest.jsonstyles.cssThe release workflow builds these files automatically when a version tag such as 1.0.0 is pushed.