Note
Release mirror: this GitHub repository mirrors releases of the canonical monorepo, which lives on a private Forgejo instance. It is read-only for development purposes.
Monorepo for xpufx Paseo tooling: shared runtime libraries, plugins, MCP servers, and agent skills.
Note
Platform Support: Developed and tested primarily on Linux, but structured to work cross-platform on macOS and Windows.
plugins/top/— Live host system resource monitor, timeline telemetry, and customizable metric pills (v0.4.0).packages/paseo-plugin-helper/— Shared runtime library for Paseo plugins (UI components, server utilities, RPC contracts, settings schema, and testing harness). Published to npm aspaseo-plugin-helper.plugins/mcp-tools/— MCP server fleet management and diagnostic plugin.plugins/x-comms/— Cross-daemon agent conversation mesh plugin.plugins/forges/— Forge/Gitea-family issue tracker and workflow integration plugin.plugins/slash/— Slash-command console: manage and run custom composer slash commands.plugins/twofado/— Approval-gate surface for the 2fado privileged-command daemon.plugins/plugin-updates/— Git-source update monitor and updater for installed plugins.plugins/demo/— Conformance testbed and canonical showcase forpaseo-plugin-helperprimitives.
Install each plugin from npm:
# Host system resource monitor
paseo plugin add npm:@xpufx/paseo-topOr install directly from this Git repository:
# Host system resource monitor
paseo plugin add xpufx/paseo --path plugins/topReplace top with any published plugin ID listed above. Each plugin README has
copy-paste commands for that plugin.
npm install
make check # Run full typecheck and unit test suite
make doctor # Freshness diagnostic for helper build and running daemons
make reload # Auto-rebuild helper, stamp git versions, and reload daemonsmain— Current SDK mainline. Feature work targets here.- Maintenance branch — Preserved baseline; only necessary bug and security fixes belong here.
Normal PRs target main; only bug and security fixes are backported to the
maintenance branch, generally landing on main first. Milestones distinguish
maintenance fixes from current feature and migration work.
See docs/branch-policy.md for details.
# Typecheck or test a single plugin
npm run typecheck --workspace=plugins/top
npm test --workspace=plugins/topPlugins are publish-ready as @xpufx/paseo-<id>; see scripts/publish-npm.mjs.
The flow keeps proof-of-presence (npm 2FA/OTP) on the human while agents/CI do
the mechanical work:
make npm-stage # agent/CI: pack tarballs into publish-stage/ (no registry, no 2FA)
# upload publish-stage/ as a CI artifact
make npm-publish-dry # human: print the exact publish commands
make npm-publish # human: npm publish --access public (prompts for OTP)node scripts/publish-npm.mjs with no flags stays a credential-free dry run.
Registry-native alternative (npm >= 11.19): only an explicitly dispatched
npm stage workflow with the NPM_TOKEN repository secret runs
npm stage publish <tarball> (no 2FA). It skips versions already pending in
npm staging; after each newly accepted version it uses the existing
notify-only 2fado notify CLI path to send a package/version outcome. The
notification is best-effort: when 2fado is missing from the runner or its
daemon socket is unreachable, the workflow and helper log a warning and still
stage and upload the tarballs. Duplicate skips and failed staging attempts do
not notify; the human runs npm stage approve <stage-id> (2FA).
Published plugins are tested with Node.js 18 or later by
npm run test:npm-acquisition: each package is packed, installed into a new
consumer with production dependencies only and lifecycle scripts disabled, and
then only its paseo-plugin.json build commands run.
Plugin persistent storage converges on ~/.paseo/plugin-data/xpufx/<pluginId>/, managed canonically by paseo-plugin-helper.
MIT