Plugin structure
Each plugin consists of:- Definition — Name, description, and metadata
- Skills — Optional structured instructions in
SKILL.mdfiles - Credentials — Optional credential type definitions the plugin needs (e.g. API tokens)
- Apps — Optional interactive UIs that render inside the sidebar
Viewing plugins
The plugins settings page shows all installed plugins with:- Plugin name and description
- List of skills the plugin provides
- Required credentials and their configuration status
Plugin credentials
Some plugins require credentials (like API keys or access tokens). When a plugin declares a credential type, you can configure the credential in the plugin settings. Credential fields can be:- Secret — Encrypted and stored securely, never exposed in plaintext
- Non-secret — Stored as plain text (e.g. project IDs, usernames)
Plugin apps
Plugins can ship interactive mini-apps that render in an iframe within the chat sidebar. The agent can open these apps and exchange messages with them viapostMessage.
This enables plugins to provide rich UI experiences — for example, a Figma plugin could show a node preview panel, or a database plugin could display query results.
Built-in plugins
stagewise ships with bundled plugins in thebundled/plugins directory. These are always available and cannot be removed. Additional plugins can be installed from the community or created by the user.