Accept prerelease Paseo versions in plugin requirements and prepare plugin docs for the 0.8 beta (#4452)

Accept plugin requirements against the runtime version or its stable core while preserving the legacy version boundary. Validate all example manifests, correct the ACP example metadata, and prepare plugin author documentation for the beta.
This commit is contained in:
Mohamed Boudra
2026-09-08 08:30:52 +02:00
committed by GitHub
parent 1f5b6143d6
commit 229f3cd5a8
13 changed files with 88 additions and 65 deletions
@@ -17,6 +17,10 @@ paseo plugin install /absolute/path/to/plugin-examples/lifecycle-logger
paseo plugin logs lifecycle-logger
```
Outside the Paseo repository, `server/inspect.ts` needs `@getpaseo/protocol` installed for its
type imports. Add it to your plugin development dependencies at the same version as
`@getpaseo/plugin` before installing this example.
Copy the callbacks you need into your own plugin. The follow-up example sends a new message; it does
not replay attachments or undo previous tool effects. If the provider keeps returning the matching
phrase, it keeps sending follow-ups. Add limits or delay in your plugin when your workflow needs them.
+7 -12
View File
@@ -9,21 +9,16 @@ Set a personal API key in the daemon environment:
export LINEAR_API_KEY="lin_api_..."
```
Register the extension in `$PASEO_HOME/config.json`:
Start your daemon with that environment variable set. Then turn on **Enable plugins** in
**Settings → Plugins** and install the example:
```json
{
"pluginsEnabled": true,
"plugins": {
"linear": {
"source": "directory",
"path": "/absolute/path/to/paseo/plugin-examples/linear"
}
}
}
```bash
paseo plugin add /absolute/path/to/paseo/plugin-examples/linear
paseo plugin ls linear
```
Restart the development daemon after changing its environment or plugin configuration.
Use `paseo plugin reload linear` after source edits. Changing the API key requires restarting the
daemon with the new environment; installing or reloading plugin source does not.
The split entry point demonstrates the complete attachment-source pattern:
@@ -1,8 +1,5 @@
{
"id": "provider-acp-transformer-example",
"name": "ACP provider transformer example",
"version": "1.0.0",
"description": "Wraps an ACP command and normalizes one vendor file-edit shape.",
"requirements": {
"paseo": ">=0.8.0"
}