한국어 · Plugin guides · Compatibility · Support · Contributing
Four independently installable plugins for Git workspace visibility, provider usage, reusable prompts and Windows command execution while working with Paseo agents.
Maintained by NaruForge and contributors. This is a community project, independently maintained and not endorsed or operated by the Paseo team.
Release candidate: current source targets Paseo 0.9.0-beta.2 as collection v0.1.0-rc.4. All four plugins use the exact 0.9.0-beta.2 SDK. The collection remains a prerelease; see the 0.9 evidence and limitations. Use 0.9.0-beta.2 daemon, app and CLI. Keep v0.1.0-rc.3 for Paseo 0.8.0 and v0.1.0-rc.2 for Paseo 0.7.2.
Provider Usage uses Paseo’s official usage API. Branch Garden remains preview; the other plugins remain experimental. Prior 0.8 runtime and Git-source reports retain their original scope.
| Plugin | What it does | Requirements | Maturity |
|---|---|---|---|
branch-garden |
Inspect registered Git projects, workspaces, branches and worktrees without changing Git state. | Current source: Paseo 0.9.0-beta.2; Git; registered projects or workspaces | Preview; v0.1.0-rc.4 |
command-deck |
Save Project commands and run, inspect and stop PowerShell terminals from the Composer. | Windows Host, PowerShell 7, Paseo 0.9.0-beta.2 | Experimental, v0.1.0-rc.4; app runtime verification pending |
prompt-palette |
Save reusable prompts in Host Settings, preview and send them from the Agent Composer. | Paseo 0.9.0-beta.2 source; existing Agent with a Workspace | Experimental, v0.1.0-rc.4 |
provider-usage |
Inspect enabled Provider usage through Paseo, with configurable pills and a sidebar managed by Paseo Layout. | Paseo 0.9.0-beta.2 source; enabled provider connections | Experimental; v0.1.0-rc.4 |
Branch Garden and Provider Usage are maintained as this repository's core offering; this does not imply Paseo-team support. Prompt Palette and Command Deck remain experimental. Branch Garden's interface is in English. Provider Usage remains experimental at the provider integration boundary and still includes Korean status messages. Each English guide includes representative screenshots from the installed Paseo 0.8.0 Windows app; see the capture scope.
- Use Paseo 0.9.0-beta.2 daemon, app and CLI. Install the tools listed in the plugin guide on the daemon host.
- In Paseo Settings → Plugins, enable plugins if you choose to trust them.
- Review the release source and choose one command:
paseo plugin add NaruForge/Paseo-Plugin:plugins/branch-garden --ref v0.1.0-rc.4
paseo plugin add NaruForge/Paseo-Plugin:plugins/provider-usage --ref v0.1.0-rc.4
paseo plugin add NaruForge/Paseo-Plugin:plugins/prompt-palette --ref v0.1.0-rc.4
paseo plugin add NaruForge/Paseo-Plugin:plugins/command-deck --ref v0.1.0-rc.4No npm installation is required. --ref pins the tag; a pinned installation does not advance on plugin update. Omitting --ref tracks main. Command Deck requires a Windows host and PowerShell 7. See Git installation and Settings-preserving upgrade/rollback guidance.
paseo plugin ls
paseo plugin logs branch-gardenExpect the chosen runtime to be running without load errors. The manifest ID is the default runtime ID; use the actual ID in later commands if installed with --id. Installations are per daemon. Remote commands use paseo --host <host> plugin ls. See the plugin guides above for actions and configuration for maintenance.
Legacy Paseo 0.7.2: only Branch Garden and Provider Usage are available at v0.1.0-rc.2. Preserve that tag until upgrading both daemon and app. Use these pinned commands and the corresponding tagged guides:
paseo plugin add NaruForge/Paseo-Plugin:plugins/branch-garden --ref v0.1.0-rc.2
paseo plugin add NaruForge/Paseo-Plugin:plugins/provider-usage --ref v0.1.0-rc.2The v0.1.0-rc.4 collection includes all four plugins. Match the daemon, app and CLI to 0.9.0-beta.2 and read the 0.9 evidence. Git add/update/recovery for the three existing plugins on 0.8 is recorded in the Git source verification; Command Deck Git activation remains unverified.
For local source evaluation, clone this repository on the daemon host, enter its root, and review the selected commit before installing. Git is needed to clone; npm is only needed for development checks. Run in PowerShell or a POSIX shell:
git clone https://github.com/NaruForge/Paseo-Plugin.git
cd Paseo-Plugin
git rev-parse HEADIf you already have a checkout, use that repository root and review its ref and local changes. Follow the directory installation steps in the Branch Garden, Provider Usage, Prompt Palette, or Command Deck guide. These examples use PowerShell on the daemon host; choose a separate --id when another source is already installed under the default ID.
For the 0.9.0-beta.2 candidate, review and pin v0.1.0-rc.4. Keep v0.1.0-rc.3 for 0.8.0 and v0.1.0-rc.2 for 0.7.2. Choose one command:
paseo plugin add NaruForge/Paseo-Plugin:plugins/branch-garden --ref v0.1.0-rc.4
paseo plugin add NaruForge/Paseo-Plugin:plugins/provider-usage --ref v0.1.0-rc.4
paseo plugin add NaruForge/Paseo-Plugin:plugins/prompt-palette --ref v0.1.0-rc.4
paseo plugin add NaruForge/Paseo-Plugin:plugins/command-deck --ref v0.1.0-rc.4The command pins the reviewed v0.1.0-rc.4 tag. See Git source details for branch tracking, remote hosts and rollback.
Configuration: No plugin needs a custom host settings file. Provider Usage stores display preferences, Prompt Palette stores its library, and Command Deck stores Project commands in built-in Host Settings. Removal deletes those values; record preferences and copy prompts and commands first. Command Deck also deletes its installation identifier; existing terminals are not killed and are not adopted after reinstall. See prerequisites and removal guidance.
Paseo plugins are trusted, unsandboxed code. The backend has the daemon user's filesystem, process and network access. Review source before installing. Git and usage inspection are read-only. Prompt Palette saves settings and sends Agent messages on explicit user action. Command Deck saves commands and runs user-selected PowerShell with the daemon user's privileges, and can send Ctrl+C or terminate an owned terminal on explicit action. These are implementation boundaries, not an OS sandbox.
Security and data access lists the files, commands and endpoints used by each plugin. The plugins do not directly modify Git state or provider authentication. Prompt Palette can start Agent work under the Agent's existing permissions. Saved Command Deck commands can read or write files, start processes and use the network under the daemon account.
npm ci
npm run checkNode.js 22 and npm are used in CI. The check command validates documentation, Git-source imports, release metadata, all workspace types, and all tests on Windows, macOS and Linux. See Contributing, Design rules and the Korean development guide.
.
├── plugins/
│ ├── branch-garden/
│ ├── provider-usage/
│ ├── prompt-palette/
│ └── command-deck/
├── docs/
│ ├── CONFIGURATION.md
│ ├── COMPATIBILITY.md
│ ├── GIT_INSTALLATION.md
│ ├── RELEASING.md
│ ├── DESIGN.md
│ └── verification/
├── scripts/
├── .github/
├── plugins.json
├── README.ko.md
└── package.json
plugins.json is this repository's descriptive catalog, checked against the actual manifests. It is not a Paseo registry format. A plugin entry’s paseoVersion overrides the catalog default, allowing independently migrated workspaces to retain exact SDK checks.
Five previously developed plugins have been removed before the first public release. Existing installations must be removed explicitly; updating this repository does not uninstall them. See removal instructions.
Changelog · Release process · Support · Security reports · Issue tracker
Use the issue forms for bugs and proposals. English and Korean reports are welcome. The maintainer tracks work in GitHub Issues; you do not need access to the maintainer's private Project to contribute.
Upstream: Plugin versions · current reference · v0.8 reference · v0.7 reference · Community projects