This page lists every Apus plugin with its package, install route, and description. Operators use it to find a plugin and to see whether that plugin needs a separate install. Maintainers use it to check bundled plugin metadata and release automation.

Definitions

Source checkouts are different from npm installs: after pnpm install, bundled plugins load from their canonical extensions/<id> or core-plugin/<id> source directory so local edits and package-local workspace dependencies are available.

Install a plugin

Use the install route in each entry to decide whether install is needed. Plugins that say included in Apus are already present in the core package. Official external packages need one install. Installation applies to the running local Gateway without restarting it; start the Gateway if it was stopped.

For example, Discord is an official external package:

apus plugins install @openclaw/discord
apus plugins inspect discord --runtime --json

Ordinary bare package specs install from npm. Use clawhub:@openclaw/discord or npm:@openclaw/discord when you need an explicit source. After install, follow the plugin's setup doc, such as Discord, to add credentials and channel config. See Manage plugins for update, uninstall, and publishing commands.

Each entry lists the package, distribution route, and description.

Core npm package

69 plugins

Official external packages

96 plugins

Source checkout only

3 plugins

How this page is built

Apus generates this page from the top-level extensions/*/apus.plugin.json and core-plugin/*/apus.plugin.json manifests and the root npm package files exclusions. Optional package.json metadata enriches package and distribution details. Regenerate the page with:

pnpm plugins:inventory:gen