Skip to main content

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 by category, change the sort order, or search for a plugin by name. Where the public marketplace is available, you can also describe the job in the search box or in chat, for example, “Find a plugin that reviews code changes.” Both use the same relevance rules to find matching plugins.
  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. When you install or try a plugin from the marketplace, Qoder can open its app or add the plugin to a chat draft with a suggested prompt, if one is available. A supported extension link can also add content to a local task draft. Check the selected plugin and edit the request before sending it. 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

Open Extensions → Plugins → Add Plugins. Choose Create plugin to build a plugin, or Import plugin to import an existing ZIP file on this device. If Publish to public marketplace is available, select it to open the publishing site, sign in to the publishing center, and submit the plugin for review. Publishing guide

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 plugin. Describe the plugin’s purpose, interface, and workflow. If you want to keep it open for ongoing use, include that in the request. 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. Find the tool card that returned an app result in the current conversation or its history. If the card offers an option to open the app, use it to view the result beside that conversation. Recent pages stay available when you switch away and return. After a plugin update, select Refresh plugin in place. If the app offers Edit plugin, you can change its display name or icon. For a global app that offers Pin to sidebar, select it to find the app under More in the sidebar. In a local global app with file access, you can add files you select to a chat draft. Review the attachments before sending. An app that supports creating tasks asks for permission. Review the proposed foreground or background task before deciding whether to allow it. If the app requests a series of tasks, you can stop the remaining requests.

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. Where public marketplace sharing is available, sign in to Qoder and open the details of a marketplace plugin that supports sharing, or select an eligible user-installed local plugin under Installed. Choose Share or Share plugin, then Copy link. To use a link you received, open it in Qoder. Review the plugin name, who shared it, and its capabilities before choosing to install. If installation would replace a local plugin with the same name, Qoder asks you to confirm. Cancel to keep your version, or choose Replace and install to use the shared version. Complete any account or connector setup the plugin requires.

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. Enabling or disabling a plugin also enables or disables the Skills and MCP servers bundled with it. After installing a plugin with a connector, follow the setup prompt for that service. For OAuth, complete the service’s authorization flow. If the service requires an API key, follow the guidance to obtain it and enter it in the authorization dialog. If you cancel an authorization, a capability fails to load after an update, or one resource reports an error, you can keep using the other available capabilities. Return to the affected item to authorize it or retry. 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.