Installing Plugins
Plugins can be installed from the marketplace, from a local directory, or via the CLI. Once installed they appear in the Plugins panel where you can start, stop, reload, and configure them.
From the marketplace
- Desktop App
- CLI
- Open the Plugins panel — bottom bar → Plugins dropdown, or View → Plugins.
- Click Browse Marketplace at the top of the panel.
- Search or browse by category (LLM Providers, Chat Gateways, Execution, UI).
- Click a plugin card to see its description, required configuration, and reviews.
- Click Install. Codebolt downloads the plugin into
~/.codebolt/plugins/and starts it automatically if it has astartuptrigger.
# Search for plugins
codebolt plugin search <query>
# Install a plugin globally
codebolt plugin install <plugin-name>
# Install into the current project only
codebolt plugin install <plugin-name> --project
The plugin is downloaded from the registry and placed in the correct directory. On next server start (or immediately if the server is running) it will be discovered and loaded.
From a local directory
If you have a plugin as a local folder (downloaded manually, shared by a colleague, or one you're developing):
# Copy to global plugins directory
cp -r ./my-plugin ~/.codebolt/plugins/my-plugin
# Or copy to the current project only
cp -r ./my-plugin ./.codeboltPlugins/my-plugin
Then open the Plugins panel and click Reload to discover the new plugin.
Configuring a plugin after install
Most plugins require some configuration before they work — an API key, a bot token, a server URL. After installation:
- Find the plugin in the Plugins panel.
- Click the Configure (gear) icon.
- Fill in the required fields. These are stored securely in Codebolt's key-value store — not in plain files.
- Click Save, then Start if the plugin doesn't start automatically.
For chat gateway plugins, a configuration UI panel opens directly inside Codebolt where you enter your platform credentials.
Managing installed plugins
The Plugins panel shows all discovered plugins with their status:
| Status | Meaning |
|---|---|
running | Plugin process is active and connected |
stopped | Plugin is installed but not running |
error | Plugin crashed or failed to connect |
loading | Plugin process is starting up |
Actions available per plugin:
- Start / Stop — manually control the plugin process
- Reload — stop, rebuild detection, and restart (useful during development)
- Configure — open the settings form or UI panel
- Uninstall — remove the plugin files from the plugin directory
- View logs — open the Plugin Debug panel for this plugin's WebSocket traffic and errors
Scoping a plugin to one project
By default, installing a plugin puts it in ~/.codebolt/plugins/ where it's active globally. To scope it to a single project:
codebolt plugin install <plugin-name> --project
Or move the plugin folder manually:
mv ~/.codebolt/plugins/my-plugin ./.codeboltPlugins/my-plugin
Project-scoped plugins override global plugins of the same name.
Updating plugins
- Desktop App
- CLI
In the Plugins panel, plugins with available updates show an Update badge. Click it to update. Or update all at once: Plugins panel → ⋯ menu → Update all.
# Update a specific plugin
codebolt plugin update <plugin-name>
# Update all installed plugins
codebolt plugin update --all
Uninstalling
- Desktop App
- CLI
Plugins panel → plugin card → ⋯ menu → Uninstall. This stops the process and removes the plugin directory.
codebolt plugin uninstall <plugin-name>