Plugins
Plugins extend the platform with custom logic your team registers — validated, versioned, and enabled deliberately, like everything else that can touch production.
How plugins work
- A plugin is registered with a manifest describing what it provides; the platform validates it at submission.
- Plugins are versioned: publishing an update creates a new version, and whatever referenced the old version keeps working until it moves.
- A plugin version must be enabled before anything new can use it. Disabling stops new references without breaking existing ones.
One growing consumer: a plugin can back an agent tool, giving agents a governed way to call your custom logic — still subject to grants, side-effect levels, and the approval queue.
The statuses
| Status | Meaning |
|---|---|
| Submitted | Registered, awaiting validation — neutral, like a draft. |
| Valid / Enabled | Passed checks; usable by new references. |
| Invalid | Failed validation; the reason is shown, fix and resubmit. |
| Disabled | Deliberately switched off for new use. |
Working with plugins in the Studio
- Go to Plugins in the sidebar (System group).
- Register a plugin with its manifest; watch validation complete.
- Open a plugin's detail page for its versions, status, and the grants that reference it.
- Enable the version you want available; disable or supersede old ones at your own pace.
Next
- The main place plugins plug in: Agent tools & approvals.