Files
paseo/plugin-examples/provider-direct
Mohamed Boudra a5d2b7d863 Declare and enforce plugin Paseo version requirements (#4430)
* feat(plugins): enforce declared Paseo version requirements

Treat manifests without a Paseo requirement as pre-0.8 plugins so the first breaking plugin release offers an explicit migration path. Check the daemon and app independently before plugin execution, and preserve installed Git revisions when updates are incompatible.

* fix(nix): refresh dependency hash for plugin requirements

* refactor(plugins): validate test manifest inputs and name compatibility input
2026-09-07 17:20:19 +02:00
..

Direct provider example

This plugin implements ProviderRegistration directly. It demonstrates connection negotiation, catalog and session listing, session creation, prompt and command disposition, settings, persistence and replay, archive actions, and an ordinary child session.

The provider emits versioned provider-result timeline items for its root and child sessions. index.client.tsx registers the Zod schema and React Native renderer for those items. The server and client share only the item kind and schema under shared/.

The provider receives Paseo host tools through config.mcpServers; it does not receive a second callback tool API.