Capabilities
Plugins extend the orchestration platform itself, not the agent: they add instructions before a task starts, add their own verification checks, or act when a task completes.
Plugins are not MCP servers
task.prepare, task.verify, task.completed — in a restricted Node.js process with only the permissions it declares. Plugins run only when a platform administrator enables plugin execution, an administrator approves the installation, and the worker's owner allows it. Every plugin here ships its full source and is tested.Self-hosted: you control the registry
Your installation keeps its own capability registry. Register entries from this directory, or your own private skills, MCP servers and plugins; set versions, permissions and install policies. Nothing is fetched from us, and nothing phones home.
Managed cloud: we run it for you
The same registry, operated by us. Your organization registers and installs capabilities the same way, with the same policies and approvals. Compare the two.
4 plugins
Agent Orchestration
Posts a JSON summary of every completed task — title, summary, changed files, verification and Git result — to an https URL, with an optional authentication header.
Agent Orchestration
Reads the project's own convention files — CONTRIBUTING.md, docs/CONVENTIONS.md, .editorconfig or any you list — and adds them to the agent's instructions before it starts.
Agent Orchestration
Fails verification when a task changes files it must never touch — secrets, keys, lock files or anything you list — and sends the agent back to revert them.
Agent Orchestration
Fails verification when changed JavaScript or TypeScript files contain debugger statements or console.log calls, listing file and line so the agent removes them.