Plugins

Built-in vs community

• Built-in plugins are shipped as part of the host experience.
• Community plugins come from separate plugin bundles and need both installation and enablement.
• Higher versions already present globally should not be blindly overwritten by built-in templates.

Basic plugin checklist

When a plugin seems broken, verify in order:

1. The vault is trusted.
2. The plugin is installed.
3. The plugin is enabled.
4. The plugin setting page opens.
5. Its custom view or commands actually appear.

File-type-sensitive plugins

Some plugins heavily depend on host compatibility layers:

• Excalidraw
• Canvas-related integrations
• Agent-facing side-pane plugins

For these, host-side API compatibility matters as much as the plugin bundle itself.

Good operating practice

• Enable only the plugins you actively use.
• Test one problematic plugin at a time.
• After host updates, re-check custom views, settings pages, and context menus.

Related

• Agent Client
• Troubleshooting