Four local plugins for Paseo: workspace notes and QA planning, reusable prompts, Linear issue work, and development-port controls.
Warning
Paseo plugins are experimental, trusted code. Server-side plugin code runs without a sandbox on the daemon machine. Read the source before installing it, and expect Paseo API changes to require updates.
| Plugin | What it adds | Extra requirement |
|---|---|---|
| Workspace Companion | Markdown notes, a draggable agent board with workspace archiving, and transcript-aware manual QA plans | A configured Paseo coding-agent provider for QA generation |
| Prompt Library | A reusable prompt library in the sidebar and composer attachment picker | None |
| Linear | Issue search, comments, status changes, and priority changes | A Linear personal API key |
| Dev Ports | Workspace port discovery, safe process stopping, browser links, and private Tailscale Serve controls | Linux daemon; Tailscale is optional |
Each plugin is independently installable. You do not need to enable all four.
Requirements:
- A current Paseo daemon and CLI with plugin support
- Bun for dependency installation and verification
- Git
Clone the repository on the machine that runs the Paseo daemon:
git clone https://github.com/Dey11/paseo-plugins.git
cd paseo-plugins
bun install --frozen-lockfile
bun run test
bun run typecheckIn Paseo, open Settings → Plugins and enable plugins. Then install only the directories you want:
paseo plugin install "$PWD/plugins/workspace-companion"
paseo plugin install "$PWD/plugins/prompt-library"
paseo plugin install "$PWD/plugins/linear"
paseo plugin install "$PWD/plugins/dev-ports"
paseo plugin lsEvery installed plugin should report running. Open the Command Center with ⌘K on macOS or Ctrl+K on Windows and Linux to find its actions.
See the installation guide for remote daemons, updates, removal, and plugin-specific configuration. The usage guide explains each workflow.
Pull the repository, install any changed dependencies, run the checks, then reload the installed plugins:
git pull --ff-only
bun install --frozen-lockfile
bun run test
bun run typecheck
paseo plugin reload workspace-companion
paseo plugin reload prompt-library
paseo plugin reload linear
paseo plugin reload dev-portsReloading a plugin does not restart the Paseo daemon or interrupt unrelated agents.
Plugin state is stored under the daemon's Paseo home, normally ~/.paseo/plugin-data/. The repository never needs access to your project files beyond the behavior described in each plugin guide.
- Linear mutations require an explicit confirmation in the UI.
- Dev Ports only shows same-user listeners inside registered Paseo workspaces. It sends
SIGTERMand never force-kills a process. - Dev Ports creates private Tailscale Serve mappings. It never enables Tailscale Funnel.
- Workspace Companion sends the focused agent transcript and current workspace changes to the provider configured for QA planning.
Read SECURITY.md before installing the plugins on a shared daemon.
bun install
bun run format:check
bun run test
bun run typecheckThe suite uses Bun workspaces. Each plugin keeps its own Paseo manifest, strict TypeScript project, runtime contracts, and focused tests. See CONTRIBUTING.md for repository rules.
Paseo does not currently provide a stable plugin distribution format. This repository distributes source directories that the daemon compiles locally. Use a recent Paseo release and consult the official plugin quickstart and plugin reference when the API changes.