Plugins
Plugins
A plugin adds to Escouade what it does not do on its own: a theme, a harness, notifications, rules for your agents’ permissions. This page says what a plugin can do, the forms it comes in, where it comes from and where to start.
What a plugin brings
A plugin describes itself in one file, its manifest, and declares there what it adds:
- themes: the window’s colors, dark and light, and a palette for projects (themes);
- reactions to events: a webhook or a command when a ticket moves to “To review”, when an agent waits, when a turn ends (events);
- permission decisions: allowing or denying what an agent asks for, before the question reaches you (permission rules);
- harnesses: an agent that speaks ACP, like Goose, described without code (a described ACP harness);
- a workflow reader, for a workflow Escouade does not read on its own;
- its settings and its secrets, which you fill in on its page.
Some of Escouade’s integrations are plugins themselves, shipped with the app: GitHub, GitLab, Bitbucket, Gitea and Forgejo, Trello, the ACP harnesses, isola and the online voice services (see the plugins shipped with Escouade).
Three forms
| Form | What it is | What the install window says |
|---|---|---|
| Declarative | The manifest alone: a theme, webhooks, a described harness. Nothing runs. | Its permissions, with no program |
| Program in WASM | A bundle in JS or TypeScript (run.js), or a module in Rust (run.wasm), that Escouade runs inside the app, with no Node or Rust on your machine. It reaches the network, files and programs only through Escouade, and only what it declares. |
“Runs inside Escouade, isolated” |
| Native program | An executable (run.command) started in a process, with your rights. The store publishes none: it only comes from a folder or a git repository. |
“Runs a program on your computer, with your rights” |
A program talks to Escouade through the protocol; the SDK writes it for you in TypeScript, the kit in Rust.
What a plugin cannot do
- Read another one’s secrets: a plugin has only its own, never those of an account, a harness or another plugin.
- Act in a private project without your consent: a plugin you install is off there from the start (only the plugins shipped with Escouade are on there, like the rest of the app).
- Install itself: a project can propose a plugin in its
.escouade.yml, never install it; anescouade://link opens its page, never the install. - Receive what it did not ask for: a fact outside
permissions.eventsis never sent to it, a secret outsidepermissions.secretsis refused (see permissions). - Change the interface beyond what its manifest declares: no view of its own.
Where it comes from
- Shipped with Escouade: signed and updated with the app; it is switched off, never uninstalled.
- The store, store.escouade.dev: each version passes eleven checks there; those Escouade reviewed carry the “Verified by Escouade” seal, the others are “Unverified”.
- A folder or a git repository: allowed, always “Unverified”: nobody reviewed it.
- A folder in development: loaded in place, read again when it changes, to write it.
Where to start
- Using one: installing a plugin, then permissions.
- Writing one: a first plugin in ten minutes, in TypeScript or in Rust, then the manifest, the host’s capabilities, the calls and the example plugins.
- Publishing it: testing a plugin, publishing on the store, plugin security and versions.
- A question: the FAQ.