@stevecastaneda/paseo-progress 1.3.0 → 1.4.0

package/OVERVIEW.md

@@ -2,7 +2,7 @@ Progress gives each worktree a live dashboard for long agent jobs. The agent rec
 
 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, videos and text files the agent records open in a preview inside Paseo, and a folder opens as a list of its files. Videos play only in the desktop app. Any other file opens in an app on the computer running the Paseo daemon, and so does a previewed file when you press Open. Open is hidden when that computer can't open files, like a Linux server with no desktop. That's true from your phone too. The app opens on that computer, not on the phone.
 
-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.
+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. In Settings you choose what the agent does while it waits: stop, work around the question, or keep building on its recommendation.
 
 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:
 

package/README.md

@@ -13,12 +13,14 @@ The dashboard shows:
 - percent of estimated work done, time done of time estimated (like "1h 30m of 2h"; once everything is done, how long it really took), and a bar with one segment per ticket
 - **Stuck:** blocked tickets, working tickets with no update for longer than their estimate, and blockers the agent flags
 - **Tickets:** estimate, status, and the working ticket's stage. A ticket that waits for another (`--waits-for T03`) shows "Waits for Ticket 03" under its title 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 summary on top shows its status and stage, time worked against the estimate as a bar that turns red past it, the agent's latest status line while it's working, and the agent on it. Tabs below hold the rest, each only when it has something: the ticket's write-up when it has a `--source` file (the start of it, with the rest a press away), a timeline of its stages and statuses with how long each took, and the activity, questions and deliverables that belong to it. The agent on a ticket shows by its chat title; pressing it opens that chat. Items tagged with `--ticket` belong exactly; older, untagged ones are matched by when they happened and marked "by time"
-- **Questions:** each with a permanent reference (Q1, Q2, ...), lettered options, and the option the agent recommends. The agent builds nothing a question affects until you answer; it works on other things meanwhile, and stops when nothing else is left. 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, videos and text files preview in Paseo (with **Back** to the question), a folder lists its files there, 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.
+- **Questions:** each with a permanent reference (Q1, Q2, ...), lettered options, and the option the agent recommends. You pick what the agent does while you decide in Paseo's Settings (Settings, Plugins, Progress, Settings). **Stop**: it stops all work until you answer. **Work around**, the default: it holds what your answer affects and keeps working on the rest. **Keep building**: it builds its recommendation and changes course if you pick another, except for big questions, which wait. A question is big when building ahead would send something off your computer, when the answer sets something people or programs outside the repo rely on, or when most of the remaining work would be built on it. Each open question shows what the agent is doing: "Agent stopped until you answer", "Waiting for you" (with the reason when it's big), or "Building with B: <its label>". 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, videos and text files preview in Paseo (with **Back** to the question), a folder lists its files there, 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.
 - **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
 
 <img src="images/2-ticket.png" alt="A ticket's story: its status, time against the estimate, the agent on it, and its timeline" width="400"> <img src="images/3-question.png" alt="A question waiting for an answer, with lettered options, the agent's recommendation and Copy buttons" width="400">
 
-The 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 says so, for example `3 questions`. With something stuck too, it shortens to `3Q · 1 stuck` to fit. 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.
+<img src="images/5-settings.png" alt="The Questions setting in Paseo's Settings, set to Work around" width="600">
+
+The panel lives in Explorer, beside the agent chat, so you can watch both. Open it from Command Center with **Open Progress**. The cog at the top right of the panel opens the plugin's Settings. After an update, the panel shows what's new in that version once. When questions are waiting or something is stuck, a pill above the message box says so, for example `3 questions`. With something stuck too, it shortens to `3Q · 1 stuck` to fit. 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.
 
 <img src="images/4-pill.png" alt="The pill above the message box, showing two questions waiting" width="600">
 
@@ -36,7 +38,7 @@ Or from Paseo's plugin registry: `paseo plugin add stevecastaneda/progress`.
 
 Enable plugins under **Settings → Plugins** on the Paseo host. You need Node.js 22.18 or later on the daemon host.
 
-Then 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.
+Then 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. On Windows it also adds `paseo-progress.cmd` next to it, because PowerShell and cmd only run files with an extension like `.cmd`. 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:
 
@@ -47,6 +49,15 @@ node "$([ -f "$dir/dist/server/cli.js" ] && echo "$dir/dist/server/cli.js" || ec
 
 If `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 as one JavaScript file in `dist/`, built with esbuild when publishing, because Node won't run TypeScript from `node_modules`. That file includes zod (MIT), so installing the plugin downloads no other packages.
 
+The command, and **Install skill** in the panel, look for Paseo's own command in this order:
+
+1. `PASEO_BIN`, if you set it.
+2. `PASEO_CLI`, which Paseo sets for the agents it starts.
+3. `paseo` on your `PATH`.
+4. The app's default install: `/Applications/Paseo.app/Contents/Resources/bin/paseo` on macOS, `%LOCALAPPDATA%\Programs\Paseo\resources\bin\paseo.cmd` on Windows.
+
+Setting `PASEO_PROGRESS_PLUGIN_DIR` to a plugin folder makes the command run that copy without asking Paseo. Use it only for testing, because an installed plugin's folder changes with every update.
+
 ## Where progress is kept
 
 Each worktree's progress lives outside the repo, in its own folder under `~/.local/state/paseo-progress/` on the daemon host. There's nothing to set up and nothing to hide: git never sees these files, and the plugin never edits a `.gitignore` or git's exclude file. The panel's empty state shows the exact path.
@@ -63,7 +74,7 @@ Earlier versions kept progress in `.scratch/` in each worktree, hidden by a `.sc
 
 ## Agent skill
 
-The 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.
+The 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, and finish. It stays short and leaves the details to `paseo-progress --help`. 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. On Windows the links are junctions, which don't need admin rights or Developer Mode. 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.
 
 From a terminal instead:
 
@@ -99,7 +110,8 @@ paseo-progress finish "Snapshots ship for all four tables"
 - Statuses are `not_started`, `working`, `blocked`, `done`, and `skipped`. Skipped tickets leave the totals.
 - `ticket add` and `ticket update` take an optional `--source <path or link>[=<label>]`: where the ticket is written up, like its spec file or issue. It shows under the ticket's status in its dialog and opens like a deliverable. `--source ""` clears it. Tickets without one are fine.
 - A working ticket is stuck once it goes longer than its estimate without an update, timed from its last status, stage or note change, or activity tagged to it. The ticket's dialog still shows total time worked against the estimate.
-- `question ask` needs `--recommend`, the agent's pick. The question dialog tags that option "Recommended".
+- `question ask` needs `--recommend`, the agent's pick. The question dialog tags that option "Recommended". Its output tells the agent the question mode and what to do until the answer. `--big "<why>"` marks a big question, which waits for the answer even in Keep building. `start` and `show` also print the mode.
+- Paseo keeps the question mode in its own settings, which only the plugin's server can read, so the server copies it to `~/.local/state/paseo-progress/settings.json` for the command. Without that file, for example while the plugin is off, the command uses Work around.
 - Deliverable paths are stored relative to the worktree root. Web links open in Paseo's browser. Pressing an image (PNG, JPEG, GIF, WebP, up to 10 MB) or text deliverable (Markdown, text, logs, JSON, YAML, CSV; the first 256 KB) previews it in a dialog inside Paseo, which also works from a phone; **Open** there opens the file in its default app. **Open** shows only when the computer running Paseo can open files. A Linux server with no desktop can't, so there a file Paseo can't preview copies its path and says why. A video (MP4, MOV, WebM, up to 200 MB) plays in the same dialog in the desktop app. When there are several files, **Previous** and **Next** step through them, and so do the left and right arrow keys. Pressing a folder lists its files in the same dialog. Press a file to preview it, or a folder inside to list that one, and **Back** returns to the list. Pressing any other local deliverable opens it with its default app on the machine running the Paseo daemon (for example HTML in your browser). On macOS, **Open** sends text files to your default browser. Only recorded deliverables inside the worktree open this way; otherwise the path is copied. The copy icon on each row copies the path.
 - Several agents can share one run. When another session adds a ticket, each agent sees it at the end of its next command's output (and in `show`), and the skill has it work that ticket in order after its current one. An agent only hears about tickets added since its own last update in the run, and only once.
 - Subagents record their own progress. Since Paseo 0.11, an agent waiting on background subagents shows as idle, so only the subagents' updates show the work is still going. The skill has the agent give each subagent the worktree path and ticket id, and the subagent records its stages and a ticker line on that worktree's dashboard.
@@ -125,6 +137,23 @@ The progress file, `progress.jsonl`, holds one JSON event per line, each with a
 
 ## Changelog
 
+### 1.4.0
+
+- [New] **Choose what agents do while a question waits.** Open Settings with the cog at the top right of the Progress panel. **Stop** halts all work until you answer. **Work around**, the default, holds only what your answer affects, which is how questions already worked. **Keep building** builds the agent's pick and changes course if you choose another.
+- [New] **Big questions always wait.** In Keep building, the agent still waits when building ahead would send something off your computer, set something people outside the repo rely on, or carry most of the remaining work. The question says which.
+- [Improved] **Every open question shows what the agent is doing.** It reads "Agent stopped until you answer", "Waiting for you", or "Building with B" and the name of option B.
+- [Improved] **A shorter agent skill.** It's about half as long, and agents get the rule for your mode each time they ask.
+- [New] **What's new, once per update.** After an update, a banner in the panel shows that version's changes. Closing it hides it until the next version.
+- [Fixed] **Bold text in ticket write-ups.** Words marked bold in a ticket's write-up used to show as plain text.
+
+### 1.3.1
+
+- Progress works on Windows (#84). Before, `paseo-progress` stopped with "The progress plugin is not installed in Paseo", and **Install skill** couldn't find the plugin. On Windows, Paseo's command is `paseo.cmd`, and Node can start a `.cmd` file only through cmd. Both now go through cmd on Windows, and both also check where Paseo installs its command.
+- On Windows, **Install command** also adds `paseo-progress.cmd`, so agents in PowerShell or cmd can run `paseo-progress`, not just those in Git Bash.
+- On Windows, **Install skill** makes junctions instead of symlinks, so it works without admin rights or Developer Mode.
+- The banner no longer says the command's folder is missing from `PATH` on Windows when it's there.
+- If you worked around this by hand, delete your own `paseo-progress.cmd`, then press **Update command**. Also remove `PASEO_PROGRESS_PLUGIN_DIR`, or the command keeps running the folder it names after the plugin updates. Skill links you made yourself keep working, and the panel offers **Update skill** once the plugin folder changes.
+
 ### 1.3.0
 
 - The file preview has a **Copy** button beside the path. It copies the full path, so you can paste it into your message to the agent without closing the preview. Before, the path was cut off when it was long, and you had to close the preview and copy it from the list.

package/client/launcher.tsx

@@ -22,7 +22,7 @@ export function skillQueryKey(hostId: string) {
 export function launcherNotice(status: LauncherStatus): { text: string; action?: string } | null {
   switch (status.state) {
     case "missing":
-      return { text: `Agents record progress with the paseo-progress command, which isn't installed yet. Installing adds one file: ${status.path}`, action: "Install command" };
+      return { text: `Agents record progress with the paseo-progress command, which isn't installed yet. Installing adds it at ${status.path}`, action: "Install command" };
     case "outdated":
       return { text: `An older paseo-progress command is installed at ${status.path}.`, action: "Update command" };
     case "foreign":
@@ -34,7 +34,7 @@ export function launcherNotice(status: LauncherStatus): { text: string; action?:
 
 // What the skill banner says, or null when every agent folder has the skill.
 export function skillNotice(status: SkillStatus): { text: string; action?: string } | null {
-  const folders = (state: string) => status.targets.filter((target) => target.state === state).map((target) => target.path.replace(/\/paseo-progress$/, ""));
+  const folders = (state: string) => status.targets.filter((target) => target.state === state).map((target) => target.path.replace(/[\\/]paseo-progress$/, ""));
   const skipped = folders("foreign").length ? ` Something else is already at ${folders("foreign").join(", ")}, so the plugin leaves it alone.` : "";
   switch (status.state) {
     case "missing":

package/client/panel.tsx

@@ -2,10 +2,11 @@ import { type PluginWorkspacePanelProps, useRpc, useWorkspace } from "@getpaseo/
 import { Icon } from "@getpaseo/plugin/client/react-native";
 import { DeliverablesList } from "./deliverables";
 import { LauncherBanner, SkillBanner } from "./launcher";
+import { WhatsNewBanner } from "./whats-new";
 import { HistoryRow } from "./history";
 import { AnsweredQuestionsList, QuestionsSection } from "./questions";
 import { Spinner, StalledPulse, WaitingDot } from "./spinner";
-import { IconSwap, Presence, StaggerRoot, nativeDriver } from "./motion";
+import { IconSwap, PressScale, Presence, StaggerRoot, nativeDriver } from "./motion";
 import { SectionTitle } from "./section-title";
 import { raised } from "./surfaces";
 import { unbroken, When } from "./when";
@@ -30,11 +31,13 @@ type Colors = PluginWorkspacePanelProps["theme"]["colors"];
 
 const mono = () => (Platform.OS === "ios" ? "Menlo" : "monospace");
 
-export function ProgressPanel(props: PluginWorkspacePanelProps) {
+type PanelProps = PluginWorkspacePanelProps & { openSettings(): void };
+
+export function ProgressPanel(props: PanelProps) {
   return <WorkspaceProgress key={`${props.host.id}:${props.workspaceId}`} {...props} />;
 }
 
-function WorkspaceProgress({ theme, workspaceId, host, layout, navigation }: PluginWorkspacePanelProps) {
+function WorkspaceProgress({ theme, workspaceId, host, layout, navigation, openSettings }: PanelProps) {
   const colors = theme.colors;
   const directory = useWorkspace(workspaceId, (workspace) => workspace.directory);
   // Paseo marks the workspace running while any of its agents is. Since 0.11 a Claude
@@ -56,12 +59,13 @@ function WorkspaceProgress({ theme, workspaceId, host, layout, navigation }: Plu
           Could not read progress: {errorText(query.error, "something went wrong")}
         </Text>
       ) : null}
+      <WhatsNewBanner colors={colors} host={host} />
       <LauncherBanner colors={colors} host={host} />
       <SkillBanner colors={colors} host={host} />
       {/* Fades in like the dashboard's sections instead of popping in after the spinner. */}
-      <Presence show={Boolean(result && !result.configured)}>{result && !result.configured ? <EmptyState colors={colors} file={result.file} /> : null}</Presence>
+      <Presence show={Boolean(result && !result.configured)}>{result && !result.configured ? <EmptyState colors={colors} file={result.file} openSettings={openSettings} /> : null}</Presence>
       {/* Keyed by run: a new run starts with fresh tabs, pages and dialogs. */}
-      {result?.configured ? <DashboardView key={result.dashboard.run?.startedAt ?? "none"} colors={colors} dashboard={result.dashboard} agentRunning={agentRunning} compact={layout.compact}
+      {result?.configured ? <DashboardView key={result.dashboard.run?.startedAt ?? "none"} colors={colors} openSettings={openSettings} dashboard={result.dashboard} agentRunning={agentRunning} compact={layout.compact}
         workspaceId={workspaceId} workspaceDirectory={result.root} file={result.file} navigation={navigation} /> : null}
       {result?.inRepo && directory ? <HistoryRow colors={colors} workspaceId={workspaceId} directory={directory} savedTo={result.savedTo} /> : null}
     </ScrollView>
@@ -84,7 +88,17 @@ function useMarkPanelOpened(workspaceId: string, directory: string | null, neede
   }, [needed, directory, workspaceId, mark]);
 }
 
-function EmptyState({ colors, file }: { colors: Colors; file: string }) {
+// Optical: the 24px button centers on a 20 to 21px title line.
+function SettingsButton({ colors, onPress }: { colors: Colors; onPress(): void }) {
+  return (
+    <PressScale accessibilityRole="button" accessibilityLabel="Open Progress settings" hitSlop={6} outerStyle={{ marginVertical: -2 }} onPress={onPress}
+      style={({ pressed, hovered }) => ({ padding: 4, borderRadius: 4, backgroundColor: pressed ? colors.border : hovered ? colors.surface1 : "transparent" })}>
+      <Icon name="Settings" size={16} color={colors.foregroundMuted} />
+    </PressScale>
+  );
+}
+
+function EmptyState({ colors, file, openSettings }: { colors: Colors; file: string; openSettings(): void }) {
   return (
     <View style={{ padding: 12, paddingTop: 20, gap: 10 }}>
       <View style={{ flexDirection: "row", alignItems: "center", gap: 8 }}>
@@ -92,6 +106,8 @@ function EmptyState({ colors, file }: { colors: Colors; file: string }) {
         <Text accessibilityRole="header" style={{ color: colors.foreground, fontSize: 14, lineHeight: 20, fontWeight: "500" }}>
           No progress recorded yet
         </Text>
+        <View style={{ flex: 1 }} />
+        <SettingsButton colors={colors} onPress={openSettings} />
       </View>
       <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>
         An agent working in this worktree records progress with the <Text style={{ color: colors.foreground }}>paseo-progress</Text> command. It shows up here as soon as the first run starts.
@@ -132,7 +148,8 @@ function useNow(intervalMs: number): number {
 
 const WIDE_MIN = 760;
 
-function DashboardView({ colors, dashboard, agentRunning, compact, workspaceId, workspaceDirectory, file, navigation }: {
+function DashboardView({ colors, dashboard, agentRunning, compact, workspaceId, workspaceDirectory, file, navigation, openSettings }: {
+  openSettings(): void;
   colors: Colors;
   dashboard: Dashboard;
   agentRunning: boolean;
@@ -155,9 +172,12 @@ function DashboardView({ colors, dashboard, agentRunning, compact, workspaceId,
     <StaggerRoot>
       <Presence show order={0}>
       <View style={{ paddingHorizontal: 12, paddingTop: 12, paddingBottom: 10, gap: 4, borderBottomWidth: 1, borderBottomColor: colors.border }}>
-        <Text accessibilityRole="header" style={{ color: colors.foreground, fontSize: 15, lineHeight: 21, fontWeight: "600" }}>
-          {dashboard.run?.title ?? "Progress"}
-        </Text>
+        <View style={{ flexDirection: "row", alignItems: "flex-start", gap: 8 }}>
+          <Text accessibilityRole="header" style={{ flex: 1, color: colors.foreground, fontSize: 15, lineHeight: 21, fontWeight: "600" }}>
+            {dashboard.run?.title ?? "Progress"}
+          </Text>
+          <SettingsButton colors={colors} onPress={openSettings} />
+        </View>
         {dashboard.run?.subtitle ? (
           <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>{dashboard.run.subtitle}</Text>
         ) : null}

package/client/questions.tsx

@@ -153,7 +153,10 @@ function QuestionRow({ colors, question, first, onOpen, onCopy }: {
       </PressScale>
       <PressableRow colors={colors} accessibilityRole="button" accessibilityLabel={`${question.id} choices`} onPress={onOpen}
         style={{ flex: 1, minWidth: 0, flexDirection: "row", alignItems: "flex-start", gap: 8, borderRadius: 4, margin: -4, padding: 4 }}>
-        <Text style={{ flex: 1, minWidth: 0, color: colors.foreground, fontSize: 13, lineHeight: 19 }}>{question.question}</Text>
+        <View style={{ flex: 1, minWidth: 0, gap: 2 }}>
+          <Text style={{ color: colors.foreground, fontSize: 13, lineHeight: 19 }}>{question.question}</Text>
+          <QuestionState colors={colors} question={question} />
+        </View>
         {/* Optical: centers the 14px chevron on the 19px first line. */}
         <View style={{ paddingTop: 2.5 }}><Icon name="ChevronRight" size={14} color={colors.foregroundMuted} /></View>
       </PressableRow>
@@ -183,10 +186,23 @@ export function QuestionView({ colors, question, now, onCopy, onOpenAttachment,
   );
 }
 
-// The agent's pick, under an open question that has no lettered options to tag.
+// Under an open question: whether the agent stopped, waits, or builds its pick,
+// and its pick when there are no lettered options to tag.
 export function QuestionState({ colors, question }: { colors: Colors; question: Question }) {
-  if (question.options.length || !question.recommended) return null;
-  return <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 17 }}>Recommended: <Text style={{ color: colors.foreground }}>{question.recommended}</Text></Text>;
+  const value = { color: colors.foreground };
+  // The letter alone means nothing in the rows that don't list the options.
+  const pick = question.options.find((option) => option.letter === question.recommended);
+  return (
+    <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 17 }}>
+      {question.state === "building" ? <>Building with <Text style={value}>{question.recommended}{pick ? `: ${pick.label}` : ""}</Text></> : (
+        <>
+          {!question.options.length && question.recommended ? <>Recommended: <Text style={value}>{question.recommended}</Text>. </> : null}
+          {question.state === "stopped" ? "Agent stopped until you answer" : "Waiting for you"}
+          {question.big ? <>. <Text style={value}>Big</Text>: {question.big}</> : null}
+        </>
+      )}
+    </Text>
+  );
 }
 
 // `onSurface1` when drawn on a surface1 background (Paseo's dialogs), so the

package/client/settings.tsx

@@ -0,0 +1,40 @@
+import { type PluginSurfaceProps, useSettings } from "@getpaseo/plugin/client";
+import { SettingsAction, SettingsCard, SettingsSection, SettingsSelect } from "@getpaseo/plugin/client/ui";
+import React from "react";
+import { Text } from "react-native";
+import { DEFAULT_QUESTION_MODE, QUESTION_MODE_RULES, QUESTION_MODES } from "../shared/question-modes";
+import { questionSettings } from "../shared/settings";
+
+const OPTIONS = QUESTION_MODES.map((value) => ({ label: QUESTION_MODE_RULES[value].label, value }));
+
+export function QuestionSettings({ theme }: PluginSurfaceProps) {
+  const settings = useSettings(questionSettings);
+  const muted = { color: theme.colors.foregroundMuted, fontSize: 13, lineHeight: 19 };
+  if (settings.status === "loading") return <Text style={muted}>Loading settings…</Text>;
+  if (settings.status !== "ready") {
+    return (
+      <SettingsSection title="Questions">
+        <Text style={muted}>{settings.error}</Text>
+        <SettingsCard>
+          <SettingsAction label="Try again" actionLabel="Reload" onPress={settings.reload} />
+          {settings.status === "invalid" ? <SettingsAction label={`Go back to ${QUESTION_MODE_RULES[DEFAULT_QUESTION_MODE].label}`} actionLabel="Reset" onPress={settings.reset} /> : null}
+        </SettingsCard>
+      </SettingsSection>
+    );
+  }
+  return (
+    <SettingsSection title="Questions">
+      <SettingsCard>
+        <SettingsSelect
+          label="When an agent asks you a question"
+          hint={QUESTION_MODE_RULES[settings.values.mode].hint}
+          error={settings.saveError}
+          value={settings.values.mode}
+          options={OPTIONS}
+          disabled={settings.saving}
+          onValueChange={(mode) => void settings.save({ ...settings.values, mode }, settings.revision)}
+        />
+      </SettingsCard>
+    </SettingsSection>
+  );
+}

package/client/surfaces.ts

@@ -3,17 +3,20 @@ import type { ViewStyle } from "react-native";
 
 type Colors = PluginWorkspacePanelProps["theme"]["colors"];
 
-// Relative luminance of a #rgb/#rrggbb or rgb() color, or null when unreadable.
-function luminance(color: string): number | null {
-  let rgb: number[] | null = null;
+// The red, green and blue of a #rgb/#rrggbb or rgb() color, or null when unreadable.
+function channels(color: string): number[] | null {
   const hex = color.trim().match(/^#([0-9a-f]{3}|[0-9a-f]{6})$/i);
   if (hex) {
     const digits = hex[1].length === 3 ? [...hex[1]].map((d) => d + d) : hex[1].match(/../g)!;
-    rgb = digits.map((d) => parseInt(d, 16));
-  } else {
-    const fn = color.match(/^rgba?\(\s*([\d.]+)[\s,]+([\d.]+)[\s,]+([\d.]+)/i);
-    if (fn) rgb = fn.slice(1, 4).map(Number);
+    return digits.map((d) => parseInt(d, 16));
   }
+  const fn = color.match(/^rgba?\(\s*([\d.]+)[\s,]+([\d.]+)[\s,]+([\d.]+)/i);
+  return fn ? fn.slice(1, 4).map(Number) : null;
+}
+
+// Relative luminance, or null when the color is unreadable.
+function luminance(color: string): number | null {
+  const rgb = channels(color);
   if (!rgb) return null;
   const [r, g, b] = rgb.map((v) => {
     const c = v / 255;
@@ -22,7 +25,7 @@ function luminance(color: string): number | null {
   return 0.2126 * r + 0.7152 * g + 0.0722 * b;
 }
 
-function isLight(colors: Colors): boolean | null {
+export function isLight(colors: Colors): boolean | null {
   const value = luminance(colors.surface0);
   return value === null ? null : value > 0.4;
 }
@@ -43,3 +46,12 @@ export function raised(colors: Colors): ViewStyle {
       : "0px 0px 0px 1px rgba(255, 255, 255, 0.08)",
   };
 }
+
+// A color at low opacity, for a tag's fill: the same hue as its text, never a
+// drifting second color. Paseo's own status badges use 12% in light themes and
+// 16% in dark ones, where the surface swallows more of it.
+export function tint(color: string, colors: Colors): string {
+  const rgb = channels(color);
+  if (!rgb) return colors.surface2;
+  return `rgba(${rgb.join(", ")}, ${isLight(colors) ? 0.12 : 0.16})`;
+}

package/client/ticket-dialog.tsx

@@ -8,6 +8,7 @@ import { type Link, ticketStory, type TimelineStep } from "../shared/ticket-stor
 import { type Attachment, AttachmentList, deliverableAttachment, ticketSourceAttachment } from "./attachments";
 import { StackedDialog } from "./dialog-stack";
 import { IconSwap } from "./motion";
+import { QuestionState } from "./questions";
 import { PressableRow } from "./row";
 import { Spinner, StalledPulse, WaitingDot } from "./spinner";
 import { StatusBadge } from "./status-badge";
@@ -98,7 +99,7 @@ export function TicketStoryView({ colors, dashboard, ticket, now, live, context,
                 <Text style={{ color: colors.foreground, fontSize: 13, lineHeight: 18 }}>{question.title}<LinkNote colors={colors} link={question.link} /></Text>
                 {question.answer
                   ? <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 17 }}>Answered <Text style={{ color: colors.statusSuccess, fontWeight: "600" }}>{question.answer.choice}</Text>{chosen ? <Text style={{ color: colors.foreground }}>: {chosen.label}</Text> : null}</Text>
-                  : null}
+                  : <QuestionState colors={colors} question={question} />}
               </View>
               <View style={{ paddingTop: 2 }}><Icon name="ChevronRight" size={14} color={colors.foregroundMuted} /></View>
             </PressableRow>

package/client/whats-new.tsx

@@ -0,0 +1,120 @@
+import { type PluginWorkspacePanelProps, useRpc } from "@getpaseo/plugin/client";
+import { Icon, Modal } from "@getpaseo/plugin/client/react-native";
+import { useQuery, useQueryClient } from "@tanstack/react-query";
+import React, { useState } from "react";
+import { Text, View } from "react-native";
+import { dismissWhatsNew, getWhatsNew } from "../shared/rpc";
+import { NOTE_KINDS, type NoteKind, type NoteTone, type WhatsNew, type WhatsNewNote } from "../shared/whats-new";
+import { spans } from "../shared/write-up";
+import { PressScale, Presence } from "./motion";
+import { isLight, raised, tint } from "./surfaces";
+import { BlockView, Spans } from "./write-up";
+
+type Colors = PluginWorkspacePanelProps["theme"]["colors"];
+
+// Once after an update: this version's headline, with its full notes a press
+// away. Closing either hides both for this version.
+export function WhatsNewBanner({ colors, host }: { colors: Colors; host: PluginWorkspacePanelProps["host"] }) {
+  const fetchWhatsNew = useRpc(getWhatsNew);
+  const dismiss = useRpc(dismissWhatsNew);
+  const queryClient = useQueryClient();
+  const queryKey = ["progress", "whats-new", host.id];
+  const query = useQuery({ queryKey, queryFn: () => fetchWhatsNew({}) });
+  const whatsNew = query.data ?? null;
+  // Paseo's Modal keeps drawing its content while it fades out, so the notes outlive the dismissal.
+  const [shown, setShown] = useState<WhatsNew | null>(null);
+  const [open, setOpen] = useState(false);
+  const close = (version: string) => {
+    queryClient.setQueryData(queryKey, null);
+    dismiss({ version }).catch(() => queryClient.invalidateQueries({ queryKey }));
+  };
+  const closeDialog = () => {
+    if (!shown) return;
+    setOpen(false);
+    close(shown.version);
+  };
+
+  return (
+    <>
+      <Presence show={Boolean(whatsNew)}>{whatsNew ? (
+        <View style={{ flexDirection: "row", alignItems: "center", flexWrap: "wrap", gap: 10, margin: 12, marginBottom: 0, padding: 8, borderRadius: 12, ...raised(colors), backgroundColor: colors.surface1 }}>
+          <View style={{ alignSelf: "flex-start", height: 17, justifyContent: "center" }}><Icon name="Gift" size={14} color={colors.foregroundMuted} /></View>
+          <Text selectable style={{ flex: 1, minWidth: 200, color: colors.foregroundMuted, fontSize: 12, lineHeight: 17 }}>
+            <Text style={{ color: colors.foreground, fontWeight: "500" }}>New in {whatsNew.version}:</Text> {whatsNew.headline}
+          </Text>
+          {/* 8px keeps the close button's 6px hit slop off the button beside it. */}
+          <View style={{ flexDirection: "row", alignItems: "center", gap: 8 }}>
+            <PressScale accessibilityRole="button" onPress={() => { setShown(whatsNew); setOpen(true); }}
+              style={({ pressed, hovered }) => ({ paddingHorizontal: 10, paddingVertical: 5, borderRadius: 4, backgroundColor: colors.accent, opacity: pressed ? 0.7 : hovered ? 0.85 : 1 })}>
+              <Text style={{ color: colors.accentForeground, fontSize: 12, lineHeight: 16, fontWeight: "600" }}>See what’s new</Text>
+            </PressScale>
+            <PressScale accessibilityRole="button" accessibilityLabel="Dismiss what's new" hitSlop={6} onPress={() => close(whatsNew.version)}
+              style={({ pressed, hovered }) => ({ padding: 5, borderRadius: 4, backgroundColor: pressed ? colors.border : hovered ? colors.surface2 : "transparent" })}>
+              <Icon name="X" size={16} color={colors.foregroundMuted} />
+            </PressScale>
+          </View>
+        </View>
+      ) : null}</Presence>
+      <Modal title={shown ? `What’s new in Progress ${shown.version}` : ""} icon={<Icon name="Gift" size={16} color={colors.foregroundMuted} />}
+        open={open} onOpenChange={(next) => { if (!next) closeDialog(); }}>
+        <Modal.Content>
+          {shown ? <Notes colors={colors} notes={shown.notes} /> : null}
+          <View style={{ flexDirection: "row", justifyContent: "flex-end", marginTop: 8 }}>
+            <PressScale accessibilityRole="button" onPress={closeDialog}
+              style={({ pressed, hovered }) => ({ paddingHorizontal: 12, paddingVertical: 6, borderRadius: 6, backgroundColor: colors.accent, opacity: pressed ? 0.7 : hovered ? 0.85 : 1 })}>
+              <Text style={{ color: colors.accentForeground, fontSize: 12, lineHeight: 16, fontWeight: "600" }}>Got it</Text>
+            </PressScale>
+          </View>
+        </Modal.Content>
+      </Modal>
+    </>
+  );
+}
+
+// Titled notes read as a short list of headings with their details; a changelog
+// written without titles stays a bulleted list.
+function Notes({ colors, notes }: { colors: Colors; notes: WhatsNewNote[] }) {
+  if (!notes.some((note) => note.title || note.kind)) {
+    return <View style={{ gap: 12 }}>{notes.map((note, index) => (
+      <BlockView key={index} colors={colors} block={{ kind: "item", marker: "•", depth: 0, spans: spans(note.body) }} first={index === 0} />
+    ))}</View>;
+  }
+  return (
+    <View style={{ gap: 20 }}>
+      {notes.map((note, index) => (
+        <View key={index} style={{ gap: 4 }}>
+          {note.title || note.kind ? (
+            <View style={{ flexDirection: "row", alignItems: "flex-start", gap: 8 }}>
+              {note.kind ? <KindTag colors={colors} kind={note.kind} /> : null}
+              {note.title ? <Text accessibilityRole="header" selectable style={{ flex: 1, color: colors.foreground, fontSize: 14, lineHeight: 20, fontWeight: "600" }}>{note.title}</Text> : null}
+            </View>
+          ) : null}
+          {note.body ? (
+            <Text selectable style={{ color: note.title ? colors.foregroundMuted : colors.foreground, fontSize: 13, lineHeight: 19 }}>
+              <Spans colors={colors} spans={spans(note.body)} />
+            </Text>
+          ) : null}
+        </View>
+      ))}
+    </View>
+  );
+}
+
+// Paseo has no violet for plugins, so it's Paseo's own "merged" purple, which
+// shares the status colors' lightness and chroma.
+const TONE_COLOR: Record<NoteTone, (colors: Colors) => string> = {
+  violet: (colors) => isLight(colors) ? "#7347af" : "#a890d5",
+  green: (colors) => colors.statusSuccess,
+  amber: (colors) => colors.statusWarning,
+};
+
+// Sits on the title's first line: 18px tall, 1px down in its 20px line. As wide
+// as "Improved" at least, so the titles beside the tags start at one edge.
+function KindTag({ colors, kind }: { colors: Colors; kind: NoteKind }) {
+  const color = TONE_COLOR[NOTE_KINDS[kind].tone](colors);
+  return (
+    <View style={{ marginTop: 1, minWidth: 64, borderRadius: 4, paddingHorizontal: 7, backgroundColor: tint(color, colors) }}>
+      <Text numberOfLines={1} style={{ textAlign: "center", color, fontSize: 11, lineHeight: 18, fontWeight: "500" }}>{NOTE_KINDS[kind].label}</Text>
+    </View>
+  );
+}

package/client/write-up.tsx

@@ -62,7 +62,7 @@ function TextButton({ colors, icon, label, accessibilityLabel, onPress, grow = f
   );
 }
 
-function BlockView({ colors, block, first }: { colors: Colors; block: Block; first: boolean }) {
+export function BlockView({ colors, block, first }: { colors: Colors; block: Block; first: boolean }) {
   switch (block.kind) {
     case "heading":
       return (
@@ -89,8 +89,9 @@ function BlockView({ colors, block, first }: { colors: Colors; block: Block; fir
   }
 }
 
-function Spans({ colors, spans }: { colors: Colors; spans: Span[] }) {
+export function Spans({ colors, spans }: { colors: Colors; spans: Span[] }) {
   return <>{spans.map((span, index) => span.code
     ? <Text key={index} style={{ fontFamily: MONO, fontSize: 12, color: colors.foreground }}>{span.text}</Text>
+    : span.strong ? <Text key={index} style={{ fontWeight: "600" }}>{span.text}</Text>
     : <React.Fragment key={index}>{span.text}</React.Fragment>)}</>;
 }