Plugin development
Turn a useful workflow into an installable plugin. Combine interfaces, file handling, Agent tools, Skills and themes, or provide just one focused capability.
Choose a starting point
- Create through conversation: start with Using and creating plugins. Describe the behavior and ask your companion to produce source and an installation package.
- Write your own plugin: follow Your first plugin to build a counter panel with a command and instance state.
- Maintain an existing plugin: use the API reference and Build and distribute to check types and compatibility.
Choose a capability
| Goal | Guide |
|---|---|
| Pages, panels, menus and input commands | Views and interaction |
| File previews, editing, saving and recovery | Files and documents |
| Send selected material to a task and reveal its source | References |
| Agent tools, task actions and packaged Skills | Agent capabilities |
| Settings, private data and state restoration | Settings and state |
| Colors, icons, styles and decorations | Themes and appearance |
| Libraries, Workers and WASM | Dependencies and computation |
Understand the boundary
Plugin backgrounds and views run in isolated browser environments. File, network and model access go through permissioned host APIs. Read Core concepts and Permissions and compatibility before adding capabilities.
Incremental APIs require the corresponding host version and available capability. Sharing an API major version does not guarantee the same set of methods.