Skip to main content
Extensions

Plugins

Install and manage packages of related Qoder capabilities.

A Plugin bundles related capabilities for a workflow or role. Depending on the package, it can include Skills, connectors, Agents, commands, rules, or Hooks. Install a Plugin when you want these components to work together instead of adding them one at a time.

Find and review a Plugin

  1. Select Extensions in the left sidebar.
  2. Open the Plugins tab.
  3. Browse the available categories, change the sorting option, or select Search.
  4. Open a Plugin's details and review its publisher, purpose, included components, and external requirements.
  5. Select Install only after the package matches your intended workflow.

Browse recommendations and Partner badges

To discover featured plugins, browse New & noteworthy and select its heading for the full list. This section appears only when the marketplace is accessible and recommendations are available. Otherwise, use categories, sorting, or search. A Partner badge identifies an offering from a partner. Before installing, open its details and review the publisher, purpose, required permissions, and external dependencies for your task. Visible content also depends on account or organization restrictions. The market can vary by account and extension source. Use Installed to see packages already available on this device, and Refresh market when the list appears out of date.

Use an installed Plugin

Start a task and describe the result you need. Qoder can use matching capabilities supplied by the Plugin. Type / to select a Plugin, Skill, Command, or connector; use @ to select an Agent. Select the suggested item, describe your request, and send it. For example, Better Harness requires installing the Plugin before selecting its better-harness Skill for a review. Review any authentication, permission, or confirmation step shown during use. A Plugin may combine local file access with external services, so start with a small read-only task when evaluating an unfamiliar package.

Connect WeCom

To use Qoder in WeCom, install and configure the corresponding plugin. Review its supported scope, dependencies, and authorization requirements, then follow the plugin instructions to install it and configure the WeCom connection. Once connected, send tasks in WeCom and receive Qoder replies in the chat. If your account or organization restricts access, confirm that you are allowed to use the integration first. If you cannot use the plugin, check its account, platform, and organization requirements and confirm access with your administrator.

Check IM plugin connections and pairing

Qoder can display connection states supplied by enabled IM plugins and bring plugin notifications and pairing requests together. After installation, open the configuration entry offered by the plugin, complete the service's setup, and check that the connection succeeded. When asked to pair or switch the device handling the connection, check the plugin, account, and target device before accepting. Closing or canceling the prompt does not authorize it. Enterprise policies, plugin enablement, or account changes may make an earlier connection unavailable. Check its current state rather than treating a previous account's connection as current authorization.

Create or upload a Plugin

In Extensions → Plugins, choose Add Plugins. Use Create with Qoder to build a plugin, or Upload Plugin if you already have a package. Created or uploaded content stays on the current device.

Use Plugin Creator

When creating a plugin with Qoder in a local task, use the built-in Plugin Creator to describe its purpose, inputs, and expected output. Combine the Skills, commands, Agents, Hooks, or MCP capabilities you need. Review the generated files and configuration, package the plugin, and install and verify it locally. Creation or packaging does not publish the plugin publicly.

Build and keep a UI plugin open

You can build plugins with custom interfaces and keep them open in the client for ongoing use. The plugin supplies its page and business logic; Qoder supplies the interface container and the interactions supported in the current environment.
  1. Open Extensions → Plugins → Add Plugins → Create with Qoder. Describe the plugin’s purpose, interface, and workflow. State that you want to keep it open for ongoing use. You can also add an interface to an existing plugin while preserving its capabilities.
  2. Use Plugin Creator to develop the interface and configure the plugin. A plugin intended for ongoing use needs a standalone app entry point. Review generated files, dependencies, and permissions, then package, install, and enable it through the existing workflow.
  3. Complete any required configuration or authorization and open the interface from its available app entry. Keep it open in Qoder for continued use and return to the associated conversation when needed.
Develop against the MCP Apps protocol and host capabilities supported by the current Qoder client; available interactions vary by execution environment. After installation, verify opening the page, its main actions, and required authorization. Creating or installing a plugin does not publish it publicly.

Install from a file and review access

At the plugin upload entry, select, drag, or paste one plugin ZIP file. Do not submit a directory or multiple packages at once. Before installing, review the skills, commands, Agents, Hooks, connector addresses, and external dependencies in the package. If a plugin requests Qoder SDK access, read the permission summary during installation and make the authorization decision yourself. Review permission changes during updates as well. The Agent cannot authorize this access for you. After installation, check plugin status and required configuration.

Check for plugin updates

In Qoder extension management, check eligible installed marketplace plugins for updates and use the offered update action. Enterprise extensions must match the current organization. Built-in, managed, local, or project sources may not offer an individual update action. Update plugin-provided Skills or connectors through their parent plugin. Valid enterprise-provisioned plugins reuse the existing installation; follow the management source shown in the interface.

Manage and troubleshoot

Open Installed to review installed packages. When a Plugin is no longer needed, use the management actions available on its details page rather than trying to manage one packaged component independently. If a capability is unavailable, confirm that the parent Plugin is installed and that any required connector is authenticated. If the marketplace is empty, clear any search or category filters, switch the extension source if applicable, and select Refresh market.