Skip to content
The Chat Archive
Qwenqwen3-235b-a22b· Alibaba (Qwen) LMArena Human Preference 140K

I'm a new user to obsidian.md, and am interested in a maximalist approach to the…

  1. User

    I'm a new user to obsidian.md, and am interested in a maximalist approach to the obsidian plugin ecosystem. I consider myself to be the textbook definition of "power user", and Im interested in improving my onboarding process with obsidian. currently, the issue is the limited nature of the community plugins browser. I do not need you to try to provide an exhaustive code solution, but I am interested in whether or not it is even possible to interact with the community plugin browser system when creating a plugin of my own.

  2. Assistant

    Yes, it is theoretically possible to interact with Obsidian's community plugin browser system through a custom plugin, but with significant limitations due to the current architecture and security constraints. Here's a breakdown of the possibilities and constraints:


    Key Considerations

    1. Community Plugin Browser Internals:

      • The browser is part of Obsidian's internal settings UI, not exposed via a public API.
      • Plugin metadata is sourced from the community-plugins.json manifest. This data can be fetched and parsed programmatically.
    2. No Official API:

      • Obsidian does not provide a documented API to:
        • Programmatically open the community plugin browser.
        • Trigger installs/searches.
        • Modify plugin states (enable/disable/install).
      • Workarounds would rely on undocumented DOM manipulation or reverse-engineering internal logic, which risks breaking with updates.
    3. User-Driven Installation:

      • Security restrictions require manual user approval for plugin installations. Automated installs are blocked by design.
    4. Forking Functionality:

      • You can replicate parts of the browser in your plugin by:
        • Fetching the community-plugins.json manifest.
        • Building a custom UI to display/search plugins.
        • Redirecting users to the official browser for installation (via deep links like obsidian://show-plugin?id=PLUGIN_ID).

    Potential Use Cases for Your Plugin

    • Enhanced Discovery: Build a searchable/filterable interface for plugins (e.g., by category, popularity, or tags).
    • Dependency Management: Suggest or validate required plugins for your workflow.
    • Version Control: Track updates or compatibility warnings using the manifest data.
    • Integration Hubs: Surface plugins that complement your plugin’s features.

    Technical Risks & Tradeoffs

    • Brittle Hacks: DOM manipulation or internal method calls may break with Obsidian updates.
    • Security Limits: No bypassing user consent for installs/updates.
    • Maintenance Burden: Replicating browser features requires ongoing sync with the manifest schema and Obsidian’s UI changes.

    Recommendations

    1. Leverage the Manifest: Use community-plugins.json as a foundation for custom discovery tools.
    2. Collaborate with the Community: Advocate for official APIs via Obsidian’s GitHub or forums.
    3. Build Bridges, Not Replacements: Focus on augmenting the existing browser (e.g., adding filters/tags) rather than replacing it.
    4. Explore Existing Plugins: Tools like Plugin Hub or Advanced Settings may already address some needs.

    Example Workflow

    // Fetch and parse community-plugins.json
    async function getCommunityPlugins() {
      const response = await requestUrl("https://raw.githubusercontent.com/obsidianmd/obsidian-releases/master/community-plugins.json");
      return JSON.parse(response.text);
    }
    
    // Display plugins in a custom UI
    class PluginBrowserModal extends Modal {
      constructor(app: App, private plugins: any[]) {
        super(app);
      }
    
      onOpen() {
        const { contentEl } = this;
        contentEl.createEl("h3", { text: "Community Plugins" });
        // Render searchable list here
      }
    }
    

    Final Thoughts

    While you can’t fully integrate with the browser itself, you can create a complementary tool that enhances discovery and management. For deeper integration, engage with Obsidian’s dev community to push for expanded APIs in future releases. For now, focus on empowering users with data-driven workflows that align with Obsidian’s extensible-yet-secure design philosophy. 🚀

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.