paseo plugin add npm:@stevecastaneda/paseo-setup-monitor\nOr from Paseo's plugin registry: paseo plugin add stevecastaneda/setup-monitor.
Turn on Settings → Plugins → Enable plugins on the daemon first.
","readmeText":"![\"\"](\"https://raw.githubusercontent.com/stevecastaneda/paseo-plugins/main/setup-monitor/icon.png\"){kind=icon}
\n\n# setup-monitor\n\nPaseo 0.11 live view of worktree setup. Paseo already tracks `worktree.setup` from `paseo.json`. After 0.3 it only opens the built-in Setup tab when that script fails, so a long `npm install` is silent. This plugin reads the same `workspace_setup_status` stream and shows it while it runs.\n\n- A button in the workspace top bar from the moment the worktree opens, before you've sent a message: a spinner and elapsed time while setup runs, then a green check or a red alert. It turns amber when Paseo holds setup back for a pull request from another repository. It stays until you dismiss it from the popover.\n- Click it for a popover: each setup command with its status and duration, a live log, and the failure reason if it failed. Click a command to see its log. For a held-back setup, the popover explains why and has a Run setup button.\n\n![\"The](\"images/button.png\")
\n\n![\"The](\"images/popover.png\")
![\"The](\"images/popover-failed.png\")
\n\n## Install\n\n```bash\npaseo plugin add npm:@stevecastaneda/paseo-setup-monitor\n```\n\nOr from Paseo's plugin registry: `paseo plugin add stevecastaneda/setup-monitor`.\n\nTurn on **Settings → Plugins → Enable plugins** on the daemon first.\n\n## Updates\n\nWorkspace and agent changes arrive through subscriptions rather than repeated\nlist requests. Setup status refreshes every two seconds while the plugin is\nactive. Each workspace has at most one pending status request, and its button\nand popover share that result instead of making separate requests.\n\n## Changelog\n\n### 1.0.0\n\n- Version 1.0. From now on, a new first number means an update breaks something, a new middle number means a new feature, and a new last number means a fix.\n- The setup timer counts from when setup started, in every window. It used to start over at 0s when you reloaded or opened another window.\n- The running command's row shows how long that command has run. It used to show the time for all of setup.\n- **Dismiss** is in the popover's header now, so a long failure can't push it out of view.\n- When a command fails, its error shows once, at the end of its log. It used to show in red above the log as well.\n- Paseo holds back setup for a pull request from another repository until you choose to run it. Setup Monitor used to show nothing then. Now its button turns amber, and the popover says where the pull request comes from and has a **Run setup** button.\n- New screenshots in this README.\n\n### 0.5.0\n\n- Needs Paseo 0.11 or later. The plugin now carries its own icon and screenshots, and Paseo 0.9 and 0.10 refuse to load a plugin that does. On an older Paseo, the version you already have keeps working.\n- The plugin store now takes the icon and screenshots from each release, so they match the version you install.\n- New screenshots in this README.\n\n### 0.4.4\n\n- Installing the plugin no longer downloads any other npm packages. The plugin used to install `@getpaseo/client` just for its types; it now gets them from the plugin SDK that Paseo already provides.\n\n### 0.4.3\n\n- The package description now says setup progress lives in a top-bar button. It used to say Explorer, where the plugin showed it before 0.4.0.\n\n### 0.4.2\n\n- The plugin's page in Paseo's plugin store now uses the plugin's own description instead of text the store copied from paseo.cafe.\n\n### 0.4.1\n\n- Installs again with npm 12. Installing failed with `npm ci` asking for a `package-lock.json`, because npm 12 no longer reads the lockfile this plugin shipped ([#53](https://github.com/stevecastaneda/paseo-plugins/issues/53)). The plugin no longer runs its own install step; Paseo's npm install already brings in what it needs.\n- Install from npm or Paseo's plugin registry. Installing straight from GitHub no longer works.\n"}