Changelog

From CHANGELOG.md.

Unreleased

Fixed

  • The release workflow no longer reports the wrong npm credential path. actions/setup-node writes the literal _authToken=${NODE_AUTH_TOKEN} into the runner npmrc, and the check read that placeholder as a token, so a run publishing through Trusted Publishing was told it was taking the legacy token path.
  • The post-publish check waits five minutes for the registry instead of one. npm served 0.4.0 later than that, which failed the release workflow over a publish that had succeeded.

0.4.0 (2026-11-13)

Fixed

  • ppd release waits for npm to serve the new version before it creates the GitHub release, and says what to run if the publish never lands. A failed publish used to leave a release page, and a registry PR linking to it, for a version npm had never served.
  • The release workflow publishes through Trusted Publishing alone. An _authToken line left by actions/setup-node with an empty NODE_AUTH_TOKEN made npm refuse with ENEEDAUTH before OIDC was attempted, which is why 0.3.0 was tagged but never published. The workflow now reports which credential path it took, pins npm to the major that supports Trusted Publishing, publishes a prerelease under the next tag, and fails when the registry does not serve what it just published.
  • ppd release resumes a release whose tag reached origin but whose GitHub release did not, instead of refusing every version that is not higher than the one in package.json. An npm publish that never serves the version stops the run before the release; the rerun finishes it.
  • The agent-hook template appends its card again on Paseo 0.14 and later. Those releases emit agent.turn_ended with an empty timeline, so the template saw no tool calls and silently appended nothing; it now reads the turn back from the agent's timeline when the event carries none.
  • ppd check applies the app's theme schema to client.addTheme: a bad hex color, a missing or extra color, an extra key, a missing name, a name over 60 characters or an appearance other than light or dark makes the app throw and drop the whole client, and ppd check now reports each one instead of passing the plugin.

Changed

  • Verified on Paseo 0.15.4: daemon, compiler and web UI, with the full opt-in end-to-end suite green against the installed app. ppd daemon up and ppd doctor no longer print the version note on it.
  • client-eval says where its rules come from instead of claiming they are the host's: contributions: addWorkspacePanel (checked as Paseo 0.15.4, rules copied from 0.13.0 and confirmed through 0.15.4), and warns when the host is newer than the last release the rules were read against.
  • test/rules-drift.test.ts hashes the four upstream files the client rules are copied from against a Paseo checkout (PASEO_SOURCE), so a rule that drifts fails the weekly CI job instead of going stale unnoticed.

0.3.0 (2026-11-10)

  • Add PaseoWeb.openFiles, openFile, fileTab, chooseFilePanel, openWith, pinFile, closeFile and reload for native file-panel tests. Paths identify tabs by their full workspace-relative name. Tree traversal distinguishes repeated folder names and file basenames.
  • Add ppd web --open-file PATH --with PANEL for file-panel screenshots.
  • openFile scrolls long Files trees to find the row. A requested panel without a picker, an unknown panel or a missing file fail with a clear message.
  • Without a Paseo host and without requirements.paseo, ppd check now applies the Paseo 0.15.3 client contract instead of 0.12.0, including the 0.13.0 rules.
  • Verify the daemon, compiler and web UI on Paseo 0.15.3. Add an isolated nested-file regression covering panel selection, changes, deletion, restoration, reload and reopening.
  • Close the browser when initial app navigation fails.
  • A panel title that several plugins offer fails with the matching labels in openFile, chooseFilePanel and openWith; pass the full label ("Title \u2014 owner") to choose one. Panels with identical full labels fail as indistinguishable. Before, Playwright's strict-mode error surfaced.
  • Add FileOpenOptions.pickerTimeoutMs and ppd web --picker-timeout MS to change the 10 s panel picker wait.
  • openFile waits for the Files controls after reload instead of failing when the restored sidebar mounts late.

0.2.0 (2026-10-30)

  • Verified on Paseo 0.12.0: ppd daemon up and ppd doctor no longer print the version note on it.
  • ppd check applies the client registration rules of the Paseo version it checks against: the app's or source checkout's version, or without a host the oldest release requirements.paseo admits. From 0.13.0 that includes file panels (client.addFilePanel, getpaseo/paseo#7411), agent panels (client.addAgentPanel), workspace panels without context, translated labels, { svg } and component icons, and the notification timeline item. Before, every plugin that used them failed client-eval.
  • On an app version without a method, client.<method> is undefined like in the app: a guarded call passes, an unguarded one fails client-eval.
  • client-eval warns when the host accepts the client but the oldest release requirements.paseo admits would reject it. ppd install and ppd dev print the same warning as a note.
  • A source checkout's version is raised to the release of the newer client methods its evaluator defines, since its package version lags main until a release is cut.
  • When requirements.paseo excludes the installed app (a prerelease counts by its stable core, like in Paseo), client-eval checks against the range's lower bound and warns that the app would not load the plugin.
  • From 0.13.0 a label is a non-empty string or a message from the SDK's message(); anything else gets the SDK's error text. "addFilePanel" in client works as a guard.
  • Docs: React Native, React and SDK versions come from the Paseo app at runtime; how to review their upgrades and keep Dependabot within a React Native series.

0.1.0 (2026-10-18)

First public release. Verified on macOS with Paseo 0.11.4.

Dev daemon:

  • ppd daemon up|down|status: a detached Paseo daemon in a fresh home under $TMPDIR on a free port (7800-7899), with plugins and the web UI on and relay, MCP and speech off. Port 6767 and ~/.paseo are refused, only homes carrying the .ppd-home marker are deleted, only pids whose command line carries the dev home are signalled, and inherited PASEO_* variables never reach the daemon or CLI calls. --workspace, --fake-agent, --caffeinate, --port, --name.
  • ppd install [dir]: installs a plugin, reloads it (same directory) or replaces an installed id, and checks the client against the app's registration rules: a client the app would drop is reported as client-rejected (exit 1). --git installs committed HEAD through the manifest build, also from a repo subfolder.
  • ppd dev [dir]: install, then reload on every change, re-check the client and stream plugin logs. Pauses when something keeps writing into the plugin folder.
  • ppd paseo -- <args>: any Paseo CLI call against the dev daemon.
  • ppd web and the PaseoWeb page object (paseo-plugin-devkit/web): screenshots at any viewport, Command Center items and clicks by accessible name; reports console errors and plugin clients the app failed to evaluate (exit 1).
  • ppd android up|down|status: adb reverse to the dev daemon, with read-only device checks.
  • ppd doctor: toolchain report.

Host contract:

  • ppd check, paseo-plugin-devkit/testing and paseo-plugin-devkit/vitest: compile and evaluate with the installed Paseo app's own compiler and evaluator (or a PASEO_SOURCE checkout), else an esbuild replica labeled APPROXIMATION (--approx forces it). Plugin code runs in child processes with a time limit, so a hang or process.exit fails; the returned cleanup is called and handles left open are warnings. Also: the app's client registration rules, manifest rules from Paseo's schema, Lucide icon names from the app, Hermes class syntax, parse and VM smoke run, bundle sizes, import boundaries, dependency placement and an RPC budget helper.

Agent-facing plugins:

  • ppd daemon up --fake-agent installs a credential-free provider plugin that runs a scripted turn per prompt. Steps: say, think, write, edit, bash, mcp (calls tools on the MCP servers plugins inject), sleep, fail. bash with run: true executes only in a daemon ppd daemon up started.
  • Library: runFakeAgentTurn, sendFakeAgentTurn, agentTimeline (plugin rows included), pluginRows, fakeAgentPrompt, installFakeAgent.

Start and ship:

  • ppd create <dir> [--template panel|agent-hook]: wraps paseo plugin init (built-in base without it) and adds tsconfig node types, an @types/node ~22 pin, .gitignore, vitest with a host-contract suite, npm run check|test|dev and a README. The result passes ppd check and installs as is.
  • ppd registry precheck|update|submit and ppd release (checks the remote before committing and tagging; a rerun after a failed push resumes).
  • examples/hello-plugin, examples/ci.yml and the Claude Code skill paseo-plugin-dev.

Compatibility and licensing:

  • When the installed Paseo does not look like 0.11.4 (app bundle layout, daemon start, web UI labels), errors name what was expected, the verified and found versions, and the workaround. ppd doctor and ppd daemon up note a different Paseo version. ppd --version.
  • Files adapted from Paseo (Apache-2.0) carry per-file notices, and THIRD_PARTY_NOTICES ships in the package. The package license is MIT AND Apache-2.0.