Plugins overview

Start with Plugin Developer. The quickest way to build a plugin is to describe the work to Plugin Developer, a built-in plugin. Type / in a chat and choose it. It asks only what changes the result, writes the plugin and its files, checks them, and installs it on your computer for you to try. See Create a plugin in chat.

The rest of this section explains what it produces, for when you want to review, change or write a plugin by hand.

A SoduWork plugin is an installable package that tells agents how to do one kind of work. It can contain instructions, Skills, MCP connections, inputs, permission declarations and an optional workflow. An app is a plugin with its own window.

You don't need a workflow for everything. A single method, a knowledge Skill or a system connector can be used directly from a chat or a task. Add a workflow only when the work needs several agents, human checkpoints, quality checks, deployment, or resuming from a failed step.

Plugin types

Type (template)	Use it for
method	A way of working: instructions, Skills and inputs
connector	Access to an outside system through MCP, a platform account or a bundled CLI
workflow	Several steps with hand-offs, reviews and checkpoints
app	A plugin with its own window and an AI side panel (Apps)

Three objects

Object	Answers	Can it change?
PluginVersion	What the plugin contains, where it can be used, and how the workflow runs	No. Changing content needs a new SemVer version
PluginBinding	How it connects in this organization or project: MCP, secrets, harness (runtime), model, runner	Yes. Check compatibility before switching versions
WorkflowRun	How far this run got, who actually ran each step, and what evidence it left	Stored. A failed run resumes at the exact step

Keep company addresses, machines, personal models and secrets out of the plugin. The plugin defines a portable method; the binding connects it to a real environment; the run records what happened.

Lifecycle

1. Write in the client's Plugin Studio, by chatting with Plugin Developer, or in a Git repository.
2. Package as an immutable version.
3. Pre-check runs static checks when you import.
4. Quarantine holds a candidate uploaded to the organization. Nothing runs yet.
5. Review: an admin checks the capabilities, signature key and evaluations.
6. Bind the version to an organization or project.
7. Simulate each step against the real environment.
8. Run step by step on a runner.
9. Recover from the failed step and keep the evidence.

Personal plugins use only the first three steps on your own computer. You choose when to upload one to the organization.

Where to start

You want to	Read
Turn something you just did into a plugin	Create a plugin in chat
Write a workflow by hand	Write your first workflow
Look up a field	Package format · Workflow nodes
Share it with your team	Publish to your organization
Build a plugin with its own UI	Apps

The repository includes runnable examples in hub-backend/plugins/. In the admin console, Plugins and apps → Authoring and listing guide offers a starter package that tracks the current schema.

harness harnesses runtime runtimes 底座