Compatibility
ppd 0.1.0 is verified on macOS with Paseo 0.11.4, desktop app and CLI. It relies on parts of Paseo that are not a public API, and says so when one of them moves instead of blaming your plugin.
What it needs
| Tool | For | Without it |
|---|---|---|
| Node >=22.18 | everything | |
| Paseo desktop app | the real compiler, evaluator and Lucide list in ppd check, the web UI, agentTimeline | ppd check runs as a labeled approximation; ppd web needs a web UI build (--web-dist) |
| Paseo CLI | ppd daemon, install, dev, paseo, the fake agent | no dev daemon |
| Google Chrome, or Playwright's Chromium | ppd web, PaseoWeb | no screenshots |
react-native devDependency, or HERMESC and HERMES | the Hermes compile and VM checks | those two checks skip |
| adb | ppd android | no phone |
macOS and Linux. On Linux (CI), there is no Paseo app: daemon tests skip and ppd check is an approximation.
Windows is not supported.
What ppd relies on
| Relies on | Used by | When it changes |
|---|---|---|
compiler.js, bundle-evaluator.js and manifest.js from @getpaseo/server inside the app's app.asar (dist/server/server/plugins) | ppd check (real compile and server evaluation) | paseo-compile fails with "could not load Paseo's plugin compiler", the expected path, and the verified and found versions. ppd check --approx or PASEO_SOURCE works around it. |
The Lucide exports in the app's web bundle (app-dist/_expo/static/js/web/index-*.js) | icon checks | lucide-icons warns and falls back to the plugin's own lucide-react-native. |
@getpaseo/client and ws inside app.asar | agentTimeline | the call fails naming the modules it looked for. |
paseo daemon run --home, PASEO_HOME, PASEO_LISTEN and the config.json keys | ppd daemon up | a start failure prints the daemon output and how it was started. |
| Accessible names in the web UI ("New workspace", "Open menu", "Workspace actions", "Search commands") | ppd web, PaseoWeb | a timeout names the label it waited for. |
| Rules vendored from Paseo (client registration, manifest schema, build options) | every ppd check (manifest, client-eval), the client check in ppd install and ppd dev, and the approximation's compile | drift shows up in the weekly CI job against Paseo main. |
ppd daemon up prints a note when the installed Paseo is not 0.11.4, and ppd doctor shows the same text
as a warning on its paseo CLI line:
note: ppd was verified on Paseo <verified>; this is <found>Tracking Paseo main
The devkit's CI runs its test suite every week against a fresh build of Paseo main (PASEO_SOURCE), and examples/ci.yml does the same for your
plugin. When something breaks, an issue with the message helps: nkwib/paseo-plugin-devkit/issues.