paseo plugin add npm:@stevecastaneda/paseo-progress\nOr from GitHub: paseo plugin add stevecastaneda/paseo-plugins --path progress.
Enable plugins under Settings → Plugins on the Paseo host. You need Node.js 22.18 or later on the daemon host.
\nThen install the paseo-progress command agents run. Open Progress from Command Center and press Install command in the banner. It adds one file, ~/.local/bin/paseo-progress, on the machine running the Paseo daemon, and the banner disappears once agents can run it. The plugin writes nothing until you press it, and it never replaces a file something else put at that path.
To install from a terminal instead, or to put the command somewhere else:
\ndir=\"$(paseo plugin ls progress --json | node -pe 'JSON.parse(require(\"fs\").readFileSync(0))[0].path')\"\nnode \"$([ -f \"$dir/dist/server/cli.js\" ] && echo \"$dir/dist/server/cli.js\" || echo \"$dir/server/cli.ts\")\" install-launcher [path]\nIf paseo isn't on your PATH, use /Applications/Paseo.app/Contents/Resources/bin/paseo. The command doesn't name a plugin folder: each run asks Paseo (paseo plugin ls) which copy of the plugin it is running and runs that copy, so it keeps working after updates and npm run dev switches. The npm package carries the command compiled to JavaScript in dist/, because Node won't run TypeScript from node_modules.
The plugin keeps each worktree's progress in .scratch/progress.jsonl. The first time it creates .scratch/,…
paseo-progress. Agents need the skill, and an agent that skips the command leaves the dashboard behind..scratch/progress.jsonl. There's no view across worktrees.![\"The](\"images/1-panel.png\")
\n\nThe dashboard shows:\n\n- the run's title, a headline (\"2 of 4 tickets done, 5 questions waiting for you, 1 stuck\"), a one-line \"now\" ticker, and when it was last updated\n- a \"possibly stale\" warning after 15 minutes with no update while tickets remain, unless Paseo shows an agent in the workspace still running (for example one waiting on its subagents), and never once every ticket is done or skipped or the run is finished; working items swap their spinner for a pulsing amber warning\n- percent of estimated work done, time done of time estimated (like \"1 h 30 min of 2 h\"; once everything is done, how long it really took), and a bar with one segment per ticket\n- **Stuck:** blocked tickets, working tickets with no update for longer than their estimate, and blockers the agent flags\n- **Tickets:** estimate, status, and the working ticket's stage. A ticket that waits for another (`--waits-for T03`) shows an hourglass and \"Waits for Ticket 03\" until that one is done; waiting is the order of work, so it never counts as stuck, even if the agent also marked it blocked. Press a ticket for its story in a dialog: a timeline of its stages and statuses with how long each took, notes, time worked against the estimate, and the deliverables, questions and activity that belong to it. Items tagged with `--ticket` belong exactly; older, untagged ones are matched by when they happened and marked \"by time\"\n- **Questions:** each with a permanent reference (Q1, Q2, ...), lettered options, and the default the agent is using. Press a question to open it in a dialog, then press **Copy Q2 B** to copy `Q2 (title): B` for your reply. Files and links the agent attached (`--file`) open like deliverables: images and text files preview in Paseo (with **Back** to the question), links open in Paseo's browser, and other files open in their default app. From the pill's popover, the preview opens over the popover, which stays open so you can go back to it. Answers stay listed under the same reference.\n- **Activity**, **Answered** questions and **Deliverables** (press one to open it), sharing one card with a tab for each; the panel remembers the tab you picked. Each shows the newest 10, with **Show 10 older** below\n\nThe panel lives in Explorer, beside the agent chat, so you can watch both. Open it from Command Center with **Open Progress**. When questions are waiting or something is stuck, a pill above the message box shows it (`3 questions · 1 stuck`). Pressing it opens a popover with each open question, its choices and their Copy buttons, and what is stuck, so you can answer without leaving the chat. **Open Progress** at the bottom opens the panel in Explorer.\n\nOn phones, where Paseo has no Explorer pane, Progress opens as a tab of its own, and the pill stays above the message box while a run is open so there's always a way in. SVG files preview on desktop; on phones they open on the daemon host.\n\nThe first time a run starts in a worktree whose Progress panel has never been opened, the pill shows a spinner and reads **Progress** instead; pressing it opens the panel. Once the panel has been opened there, the plugin writes an empty `.scratch/progress-panel-opened` and the nudge never comes back, even for later runs. It doesn't open the panel by itself because Paseo switches to a workspace to open its panel, which would pull you away from whatever you're looking at.\n\n## Install\n\n```sh\npaseo plugin add npm:@stevecastaneda/paseo-progress\n```\n\nOr from GitHub: `paseo plugin add stevecastaneda/paseo-plugins --path progress`.\n\nEnable plugins under **Settings → Plugins** on the Paseo host. You need Node.js 22.18 or later on the daemon host.\n\nThen install the `paseo-progress` command agents run. Open **Progress** from Command Center and press **Install command** in the banner. It adds one file, `~/.local/bin/paseo-progress`, on the machine running the Paseo daemon, and the banner disappears once agents can run it. The plugin writes nothing until you press it, and it never replaces a file something else put at that path.\n\nTo install from a terminal instead, or to put the command somewhere else:\n\n```sh\ndir=\"$(paseo plugin ls progress --json | node -pe 'JSON.parse(require(\"fs\").readFileSync(0))[0].path')\"\nnode \"$([ -f \"$dir/dist/server/cli.js\" ] && echo \"$dir/dist/server/cli.js\" || echo \"$dir/server/cli.ts\")\" install-launcher [path]\n```\n\nIf `paseo` isn't on your `PATH`, use `/Applications/Paseo.app/Contents/Resources/bin/paseo`. The command doesn't name a plugin folder: each run asks Paseo (`paseo plugin ls`) which copy of the plugin it is running and runs that copy, so it keeps working after updates and `npm run dev` switches. The npm package carries the command compiled to JavaScript in `dist/`, because Node won't run TypeScript from `node_modules`.\n\nThe plugin keeps each worktree's progress in `.scratch/progress.jsonl`. The first time it creates `.scratch/`, it also writes `.scratch/.gitignore` naming only its own files, so git ignores them without any change to your repository's `.gitignore`. If `.scratch/.gitignore` already exists, the plugin leaves it alone.\n\n## Agent skill\n\nThe plugin ships an agent skill, `paseo-progress`, that tells agents when to run each command during a multi-ticket job: set up the run, move tickets through their stages, ask questions without stopping, flag stuck work, and finish. Press **Install skill** in the Progress panel. It links `paseo-progress` into `~/.agents/skills`, `~/.claude/skills`, and `~/.codex/skills` (the folders Paseo installs its own skills into), pointing at the copy of the plugin Paseo runs, so plugin updates reach agents. If Paseo later runs the plugin from somewhere else, the button changes to **Update skill**. It never replaces a skill it didn't link; that folder is skipped.\n\nFrom a terminal instead:\n\n```sh\nskill=\"$(paseo plugin ls progress --json | node -pe 'JSON.parse(require(\"fs\").readFileSync(0))[0].path')/skills/paseo-progress\"\nfor dir in ~/.agents/skills ~/.claude/skills ~/.codex/skills; do mkdir -p \"$dir\" && ln -s \"$skill\" \"$dir/paseo-progress\"; done\n```\n\n## Recording progress\n\nRun `paseo-progress --help` for every command, and `paseo-progress