Branch Garden

Release v0.1.0-rc.3 targets final Paseo 0.8.0. See final-version checks and remaining runtime limits. Screenshots below show the installed Paseo 0.8.0 Windows app.

paseo plugin add NaruForge/Paseo-Plugin:plugins/branch-garden --ref v0.1.0-rc.3

Inspect registered Git projects, active workspaces, local branches and worktrees on the selected host. No branch is checked out, reset or deleted.

Collection · Compatibility · Install · Support

Current source targets Paseo 0.8.0. Runtime entries, imports and exact SDK dependencies have been migrated and checked with the target compiler, including a copy without node_modules. The user has completed Paseo 0.8 runtime verification; see the runtime record and reported scope. See the source verification and #82. The historical v0.1.0-rc.2 installation instructions below remain specific to 0.7.

Screenshots

Captured from the installed Paseo 0.8.0 Windows app on 2026-09-10, in the dark desktop layout. Images are cropped from real screens; see the capture scope.

The overview shows totals for the selected Host. The separate detail crop below shows only this public repository, including its active Workspace and kept default branch.

Install

Choose Paseo 0.7.2 for this published release command. Enable trusted plugins in the intended daemon’s Settings → Plugins, then run:

paseo plugin add NaruForge/Paseo-Plugin:plugins/branch-garden --ref v0.1.0-rc.2
paseo plugin ls

This pins the 0.7-compatible release; update does not advance a pinned tag. Omitting --ref tracks the default branch, which already contains 0.8 source incompatible with 0.7. Review and trust source before enabling plugins; see Git installation.

For current 0.8 source evaluation, follow the source checkout steps, then run this in PowerShell from the repository root on the daemon host:

$repoRoot = (Resolve-Path .).Path
paseo plugin ls
paseo plugin install (Join-Path $repoRoot "plugins/branch-garden")
paseo plugin ls

Expect runtime ID branch-garden with status running and no load error. If that ID already exists, choose a distinct --id branch-garden-dev and use it in subsequent commands. Open Branch Garden in the sidebar.

For Git source evaluation of 0.8 source, choose a reviewed published commit that contains this plugin. Do not use v0.1.0-rc.2 for 0.8:

paseo plugin add NaruForge/Paseo-Plugin:plugins/branch-garden --ref v0.1.0-rc.3

The command pins v0.1.0-rc.3. Git add/update/recovery for this plugin is recorded in the Git source verification; see Git installation.

Requirements and configuration

For the pinned v0.1.0-rc.2 release: Paseo 0.7.2. For current source: daemon and app compatible with ^0.8.0, with development checks pinned to 0.8.0; this is not a final 0.8 runtime certification. Git is required on the daemon host. No repository-specific configuration is required. The plugin reads the selected host's existing Paseo project/workspace registry. Windows is the primary runtime environment; macOS/Linux automated checks and live runtime evidence are tracked separately in Compatibility.

Use

Open Branch Garden in the sidebar, select the intended host and refresh. Expand a project to inspect workspace state, dirty worktrees and branch information. Registered projects can appear without active workspaces. Empty results mean no repositories matched the current scan or filter; they do not mean the filesystem is empty.

The plugin's labels, accessibility text, warnings and error messages are in English. Scan times use a 24-hour clock in the client's local time zone. Project, workspace and branch names remain unchanged; diagnostic details returned by Git or the host may use that tool's language. Paseo's surrounding interface follows its own language setting.

Use All, Cleanup candidates or Needs review to filter repositories. Expand Kept branches to see branches retained because they are the default branch, checked out, or unmerged with an existing upstream. Classification is advisory; this plugin never deletes branches.

Data access and limitations

Reads project/workspace metadata and bounded read-only Git commands. It never prunes worktrees, deletes branches or writes Git configuration. Detached HEAD, missing repositories and scan failures are displayed explicitly. A snapshot can become stale while another process changes the repository.

Troubleshooting

Check that Git is installed on the daemon host, that the selected host owns the workspace and that its repository still exists. Refresh after external Git changes.

paseo plugin ls
paseo plugin logs branch-garden

Use the actual runtime ID if installed with --id. For 0.8 CLI remote diagnostics, the syntax is paseo --host <host> plugin ls; check the daemon and app versions independently. Directory development installations use reload instead of update. If it still fails, follow Support with redacted logs and the installed ref.

Update and remove

Run paseo plugin ls against the intended Host before changing an installation. These examples use the default ID branch-garden; replace it with your actual ID if you used --id. On the 0.8 CLI, put remote selection before the command: paseo --host <host> plugin ls.

For a Git source installation, check the tracked ref and update it:

paseo plugin status branch-garden
paseo plugin update branch-garden
paseo plugin ls

Branches advance; fixed tags and commits do not. For a directory source, after reviewing changes to the local checkout use paseo plugin reload branch-garden, then paseo plugin ls. See ref changes and rollback before switching a pinned installation.

Removal is optional and separate from troubleshooting. Branch Garden has no saved plugin settings. Removal leaves your original repositories, branches and worktrees intact. A Git-source removal deletes the managed checkout; a directory-source removal leaves the original source directory intact.

paseo plugin remove branch-garden
paseo plugin ls

Confirm only the intended runtime has disappeared. No daemon restart is needed.