Plugin Hub

Plugin Hub is where you discover, install, and run small tools. A plugin is a snippet with a window, stored with your other snippets. You can also open it from the search window Marketplace tab.

What Can Plugins Do?

Plugins are mini-applications that run inside CodeExpander. They can:

• Add custom tools — timestamp converters, JSON formatters, color pickers, calculators
• Process files — drag a file into the search window, a plugin parses and transforms it
• Integrate with workflows — generate QR codes, encode/decode Base64, format SQL
• Provide AI-powered features — code review, auto-commenting, test generation

Installing Plugins

From npm (Recommended)

The fastest way to install plugins:

1. Open Plugin Hub from the main window or search window
2. In the Install section, type the npm package name (e.g. @codeexpander/plugin-timestamp)
3. Click Install

Official plugins use the @codeexpander/plugin-* prefix and are curated by the team.

Requirements: Node.js and npm must be installed on your system.

From Local Directory

If you have a plugin folder on your machine:

1. Click Import from directory
2. Select the folder containing plugin.json and the entry file
3. The plugin appears in your list immediately

From AI (MCP)

Let AI create plugins for you:

1. Enable MCP server in Settings → MCP
2. Connect your AI assistant (Cursor, Claude Desktop, etc.)
3. Describe what you need — e.g. “Create a plugin that converts CSV to Markdown table”
4. The AI generates the plugin and installs it automatically

Managing Plugins

Browse and Search

The Plugin Hub shows all installed plugins as cards. Use the search box to filter by:

• Name — e.g. “timestamp”
• Category — e.g. “Developer tools”, “Converters”
• Description — keyword search

Run a Plugin

• From Plugin Hub — Click any plugin card to open its UI
• From Search Window — Type the plugin name or its defined command triggers
• With files — Drag files into the search window; file-aware plugins activate automatically

Pin and Organize

• Pin frequently used plugins so they appear in the search window’s empty state
• Hide plugins you rarely use to reduce clutter
• Uninstall to remove completely

Plugin Anatomy

A plugin is essentially a special snippet with:

• plugin.json — Metadata (name, description, icon, category, entry file)
• Entry file — The plugin’s UI (HTML/JS)
• Commands — Optional keyword triggers for the search window

Example: A “Timestamp Converter” plugin might define:

• Command: ts — type ts 1714392000 in search to convert instantly
• UI: A visual calendar picker when opened from Plugin Hub

Creating Your Own Plugin

Option 1: Manual (For Developers)

Create a folder with:

my-plugin/
  plugin.json    ← manifest
  index.html     ← UI

plugin.json example:

{
  "main": "index.html",
  "title": "My Plugin",
  "description": "Does something useful",
  "category": "Tools",
  "features": [
    {
      "code": "myCmd",
      "explain": "Run my command",
      "cmds": ["my", "mp"]
    }
  ]
}

Import via Plugin Hub → Import from directory.

Option 2: AI-Assisted (For Everyone)

Describe your idea to an AI assistant connected via MCP. The AI handles:

• Writing the HTML/JS
• Creating the manifest
• Installing it automatically

Example prompt: “Create a plugin that counts words in selected text. Add a wc command for the search window.”

Security

Plugins run in a small window with fewer permissions than the main app:

• They cannot browse your snippet library directly
• Clipboard and toasts wait for you to allow them
• The plugin list can declare which window abilities it needs; the app enforces that

Typical Workflows

Developer Toolkit

Install: @codeexpander/plugin-timestamp, @codeexpander/plugin-json, @codeexpander/plugin-color

Daily use:

1. Search window → ts + paste timestamp → instant conversion
2. Search window → json + paste JSON → format and validate
3. Search window → color + paste HEX → see RGB/HSL conversions

Content Creator

Install: @codeexpander/plugin-qr, @codeexpander/plugin-base64

1. Search window → qr + paste URL → generate QR code image
2. Search window → b64 + paste text → encode/decode Base64

Team Custom Plugins

Your team builds internal plugins for:

• Company API signature generation
• Internal document templates
• Deployment command runners

Share via npm private registry or local directory sync.

Plugin backend

Some plugins finish in one click. Others need to stay running for a bit. Open Settings → Extensions → Plugin backend to cap timeouts and how many can run at once. This stays on this computer. Plugin windows can touch fewer files than the main window on purpose. While developing, pick allowed local folders in Settings.

Plugin development

You want a tiny “pick a date, then insert” tool. You do not install a second product. A plugin is a snippet with plugin mode on, and it can open its own small window.

The written spec is on the Settings → MCP card.

See also: MCP