* feat(app): browse, install and manage plugins from a built-in gallery Settings → Host → Plugins becomes a gallery with two tabs. Installed lists the host's plugins with on/off switches and pending updates. Browse lists the plugin directory with featured cards, categories, sorting and search. Each plugin has its own page with its screenshots, overview, details, install or on/off controls, and its own settings screens inline. Every install asks first, in a sheet naming the source and version, because installing runs the plugin's code on the host. Uninstalling also asks first; its confirm says what is deleted. The daemon fetches the directory from its configured registry (plugin.registry.list/get, gated by server_info.features.pluginRegistry). The app never fetches from the registry itself, so a host with a private registry shows that registry. README overviews render with the registry's overview contract (the same one the website uses): only https links and images work, and nothing is read as a workspace file. Before this, a word like "Node.js" became a broken relative link. * fix(app): refresh plugin failures and leave Settings cleanly from a plugin page The Installed row read the app-side evaluation error without subscribing to the registry, so a plugin fixed by Reload kept its "failed" badge. Rows and the plugin page now subscribe through usePluginEvaluationError. Leaving Settings with no remembered workspace replaced only the top stack entry; with a plugin page pushed on top, the Plugins list stayed mounted underneath and reopening Settings stacked a second copy. Dismiss the Settings entries first. * fix(app): keep Browse working as the registry grows, and test it end to end Registry listings now reach apps through an open wire schema (plugin.registry.list/get carry PluginListing*), and the daemon drops a listing it cannot read instead of failing the whole index. A registry that adds an artifact kind or bumps schemaVersion no longer breaks Browse on older apps. The gallery picks its opening tab once, so installing the first plugin keeps the user on Browse. README links open only https: the parser still autolinks bare http, www and email text, so a press checks the URL again. Adds a Browse e2e test against a local registry and Git repository: install from a row through the confirm sheet, stay on Browse, open the listing page, uninstall from it. * test(server): give the oversized-sibling diff refresh the same time budget as its siblings expect.poll defaults to one second, which a Windows git diff refresh can exceed. * test(server): wait as long as the other observer tests for native watcher events expect.poll defaults to one second; macOS FSEvents can deliver later than that on CI. * fix(app): keep a listed plugin's page usable after uninstalling it, and fetch the directory less An installed plugin's page finds its listing through the plugin, so uninstalling a directory plugin from the Installed tab left "not installed or listed" with no way back. The page now becomes the listing's page, offering Install again. Updates are re-checked when the host's plugins change and after a failed update, whose proposal named a revision that no longer exists. The directory, listing and update queries refetch on mount only once stale, so opening a plugin's page no longer refetches the whole directory and every update check. * test(app): install the plugin before opening Plugins in the busy-queue reload test Plugins opens on Browse when the host has no plugins and stays there after the first install, so a plugin installed through the daemon after the page opened never showed on Installed. * test(website): wait for hydration before scrolling to the hero in a short window The router resets the scroll position when the page hydrates. Scrolling to the mockup before that left it below the window, so its start line never came on screen and the opening scene never played. It failed 7 of 10 runs on webkit. * fix(server): show the registry setup error on Browse instead of asking to retry The registry's request headers were built inside the try around fetch, so a setup error such as credentials over plain HTTP came back as "Could not reach plugin registry. Retry later." Install already built them first. * fix(app): show plugin errors without the request details meant for logs A daemon RPC error's message ends with requestType=… code=…; the daemon's own text is in userMessage. Gallery alerts and toasts now show that text. * fix(app): show why an update failed on the plugin's page The update operation's failure was recorded under the plugin ID, but the page only read it to show the spinner, so a failed update looked as if nothing happened. The page now shows the error in its own alert, without the plugin's Failed badge, because the installed version keeps running. While an update is still available the button reads Retry. * fix(app): show a plugin page's update error only while the update is offered The failed update stayed in the operations store after the plugin was updated elsewhere or uninstalled, so the page kept saying the update failed. The page now shows it with the Update button it belongs to, as the Installed tab's Updates row does, and uninstalling forgets it.
@getpaseo/client
TypeScript SDK for building integrations on top of a Paseo daemon.
npm install @getpaseo/client
import { createPaseoClient } from "@getpaseo/client";
const client = createPaseoClient({ url: "ws://127.0.0.1:6767/ws" });
await client.connect();
const agent = await client.agents.create({
config: { provider: "codex/gpt-5.5" },
cwd: "/Users/me/dev/storefront",
prompt: "Review the current diff and name the riskiest change.",
});
const result = await agent.waitForFinish();
console.log(result.lastMessage);
await client.close();
The public API is the package root. Imports under @getpaseo/client/internal/* are unsupported implementation details used by Paseo's own packages.
Read the SDK documentation for agents, workspaces, terminals, provider discovery, events, recipes, and the API reference. Runnable TypeScript patterns also live in examples/.
Runtime
The client needs a WebSocket implementation. Modern browsers and Node.js 22 provide one globally.
Use a WebSocket URL ending in /ws, such as ws://127.0.0.1:6767/ws. Pass password when the daemon requires authentication.
The client advertises its supported protocol capabilities by default. Optional capabilities
overrides extend or override that declaration; browser hosting must be supplied by the caller.
Connecting alone does not subscribe to agent timelines or catalog events. See the
event guide for subscription lifetimes and timeline replacements.
Stability
The high-level API exported from @getpaseo/client is the supported SDK surface. The SDK and daemon remain protocol-compatible across versions, but newly added capabilities can require a newer daemon.