@stevecastaneda/paseo-progress 0.3.1 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/OVERVIEW.md +14 -0
  2. package/README.md +4 -0
  3. package/package.json +2 -1
package/OVERVIEW.md ADDED
@@ -0,0 +1,14 @@
1
+ Progress gives each worktree a live dashboard for long agent jobs. The agent records its tickets or steps with a `paseo-progress` command, along with what's stuck, questions for you and finished work. The Progress panel in Explorer shows all of it. Needs Paseo 0.9 or later, and Node.js 22.18 or later on the computer running the Paseo daemon.
2
+
3
+ The panel shows how much of the estimated work is done, what the agent is doing right now, and where each ticket stands. A ticket turns stuck when it's blocked or runs past its estimate without an update. Press a ticket to see its timeline, activity, questions and deliverables. Images and text files the agent records open in a preview inside Paseo.
4
+
5
+ When the agent needs a decision, it asks a numbered question with lettered options and says which one it recommends. A pill above the message box counts open questions and stuck work. Each option has a Copy button. Paste the answer into the chat and the agent records it.
6
+
7
+ Nothing updates unless the agent runs the command, so agents need the plugin's skill. The panel has two setup buttons, and each one shows where it will write before you press it:
8
+
9
+ - Install command writes `~/.local/bin/paseo-progress` on the daemon host.
10
+ - Install skill links the plugin's `paseo-progress` skill into `~/.agents/skills`, `~/.claude/skills` and `~/.codex/skills`. New agent sessions pick it up.
11
+
12
+ Both work from files inside the plugin and download nothing. Neither one replaces a file you made.
13
+
14
+ Progress keeps each worktree's data under `~/.local/state/paseo-progress/` on the daemon host, outside the repo. You can also save runs into the repo. Pick a folder and Progress writes each run there too, and it remembers the folder in the repo's local git config. There's no view across worktrees, and a deleted worktree's folder stays behind until you remove it.
package/README.md CHANGED
@@ -127,6 +127,10 @@ npm run dev
127
127
 
128
128
  ## Changelog
129
129
 
130
+ ### 0.3.2
131
+
132
+ - 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.
133
+
130
134
  ### 0.3.1
131
135
 
132
136
  - 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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@stevecastaneda/paseo-progress",
3
- "version": "0.3.1",
3
+ "version": "0.3.2",
4
4
  "description": "A live progress dashboard per worktree for Paseo, drawn from a file agents write with the paseo-progress command.",
5
5
  "license": "MIT",
6
6
  "author": "Steve Castaneda",
@@ -23,6 +23,7 @@
23
23
  },
24
24
  "files": [
25
25
  "paseo-plugin.json",
26
+ "OVERVIEW.md",
26
27
  "dist/",
27
28
  "index.client.tsx",
28
29
  "index.server.ts",