Recipes

Each recipe is a whole plugin, verified on a dev daemon with the commands on its page. The code shown is the code that is checked: pages read it from the repository at build time.

  • Timeline renderer: a card under every agent turn that used tools, and a screen listing all turns. Uses server.on("agent.turn_ended"), timeline.append, addTimelineRenderer, addScreen and an RPC.
  • Settings screen: a settings screen whose values the server reads when a turn ends. Uses defineSettings, registerSettings, useSettings, addSettingsScreen and addCommandCenterItem.
  • Server hooks: an MCP server injected into every new agent, and a log line for every finished turn. Uses server.before("agent.create") and server.on("agent.turn_ended").

The timeline renderer is the agent-hook template of ppd create, which the devkit's own tests create, check and run. The other two live in docs-site/recipes, and CI runs ppd check on them.

Try one

The settings and server hooks recipes are in the repository, not in the npm package (the timeline renderer is ppd create --template agent-hook). Clone the repository, then run from any plugin repo with paseo-plugin-devkit installed and a dev daemon running:

npx ppd check path/to/recipes/settings
npx ppd install path/to/recipes/settings

A recipe's devDependencies are there for types and tests only: Paseo provides @getpaseo/plugin, react, react-native and zod at runtime, so a recipe installs without npm install.