CTRL K

Enable, Disable, and Understand Markdown Explorer Plugins

July 28, 2026•2 min read

Enable, Disable, and Understand Markdown Explorer Plugins

Markdown Explorer uses plugins to keep optional workflows separate from the core editor. Open Plugins & Themes from the sidebar to see installed functional plugins and theme plugins.

Find and filter a plugin

The manager includes:

a search field for plugin name and description;
All, Plugins, and Themes category filters;
version and author information;
Enabled and Disabled state controls.

Search for a workflow such as template, enable the matching plugin, and then open its sidebar view or command.

Built-in plugin examples

The current system includes or provides the foundation for:

Templates, with reusable Markdown files and dynamic variables;
GitHub Workspace, for repository-backed Markdown;
Google Drive Workspace, currently marked Close Beta;
AI chat and history integrations;
Theme plugins, including registered built-in themes;
MCP integration foundations for AI tools.

The exact list can change with the application version, so the manager is the source of truth for what is installed.

What disabling means

Disabling a plugin unloads its optional behavior and removes its registered commands or views. It should not delete your Markdown project. A plugin can, however, perform file operations after you explicitly use its workflow, so read its description before enabling and running it.

Themes have two related states: enabled as a plugin and applied as the active theme. Disabling an applied theme returns the interface to another available theme or the base appearance.

Example: use a template

Enable the Templates plugin.
Keep template Markdown files in the configured .mark-explorer/templates/ folder.
Press Option + T on macOS or Alt + T on Windows.
Choose a template.
Review substituted values such as date, time, or title before saving.

Current limits

Markdown Explorer does not yet have a community marketplace comparable to long-established editor ecosystems. The plugin architecture is growing, and built-in integrations are currently the safest, most predictable path.

For visual customization, continue with themes and VS Code theme import.