@stevecastaneda/paseo-progress 1.13.0 → 1.14.0

package/OVERVIEW.md

@@ -1,12 +1,14 @@
-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.13 or later, and Node.js 22.18 or later on the computer running the Paseo daemon.
+Progress gives each worktree a live dashboard for long agent jobs. The agent records its tickets or steps, along with what's stuck, questions for you and finished work, with the Progress tools or the `paseo-progress` command. The Progress panel in Explorer shows all of it. Needs Paseo 0.13 or later, and Node.js 22.18 or later on the computer running the Paseo daemon.
 
 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, PDFs and text files the agent records open in a preview inside Paseo, with Markdown formatted, and a folder opens as a list of its files. Videos and PDFs show in the preview only in the desktop and web apps. A PDF in the Deliverables tab also has a button beside Copy that opens it in a Paseo tab, which is where it shows on an iPhone or iPad. Any PDF you open in a Paseo tab shows there too. 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. 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:
+On Paseo 0.14 and later, agents get the Progress tools once you turn on **Settings → your host → Agents → Enable Paseo tools**. That needs nothing installed, and every update names the agent that sent it. The setting is off by default and also lets agents start, message and stop other agents, so Progress leaves it to you. Without it, agents run the `paseo-progress` command. In the chat, each Progress tool call shows as one line of what it recorded, and opens to the full result.
 
-- Install command writes `~/.local/bin/paseo-progress` on the daemon host.
+Nothing updates unless the agent records it, 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:
+
+- Install command writes `~/.local/bin/paseo-progress` on the daemon host. With Paseo tools on, the command is only a fallback.
 - Install skill links the plugin's `paseo-progress` skill into `~/.agents/skills`, `~/.claude/skills` and `~/.codex/skills`. New agent sessions pick it up.
 
 Both work from files inside the plugin and download nothing. Neither one replaces a file you made.

package/README.md

@@ -2,7 +2,7 @@
 
 # Progress
 
-A plugin for Paseo 0.13 and later that gives each worktree a live progress dashboard. Agents record progress with the `paseo-progress` command, which adds one line per change to the worktree's progress file. That file lives outside the repo, so git never sees it. The **Progress** panel draws the dashboard from that file and updates by itself.
+A plugin for Paseo 0.13 and later that gives each worktree a live progress dashboard. Agents record progress with the Progress tools Paseo 0.14 hands them, or with the `paseo-progress` command. Each change adds one line to the worktree's progress file. That file lives outside the repo, so git never sees it. The **Progress** panel draws the dashboard from that file and updates by itself.
 
 <img src="images/1-panel.png" alt="The Progress panel in Explorer" width="440">
 
@@ -18,7 +18,7 @@ The dashboard shows:
 
 <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">
 
-<img src="images/5-settings.png" alt="Progress settings in Paseo: Questions set to Work around, Language set to System, and the Agent Skills section with View skill" width="600">
+<img src="images/5-settings.png" alt="Progress settings in Paseo: Questions set to Work around, Language set to System, the Agent Skills section with View skill, and Agent tools showing Paseo tools off with how to turn them on" 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 once, including any versions you skipped. 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 an open question, its choices and their Copy buttons, and what is stuck, so you can answer without leaving the chat. With more than one question, the arrows beside **Question 1 of 3** step through them. After you copy an answer, the popover opens on the next question. **Open Progress** at the bottom opens the panel in Explorer.
 
@@ -38,7 +38,9 @@ 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. 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.
+On Paseo 0.14 and later you can skip the command: turn on Paseo tools and agents get the Progress tools instead. See [Agent tools](#agent-tools). The command is still worth installing as a fallback, because agents in a chat that started before you turned the setting on, or in a reply that was running while the plugin reloaded, don't have the tools.
+
+To 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:
 
@@ -80,9 +82,39 @@ The choice covers every worktree of the repo and is kept in the repo's local git
 
 Earlier versions kept progress in `.scratch/` in each worktree, hidden by a `.scratch/.gitignore` they wrote. The first time the command or the panel touches a worktree after the upgrade, the plugin moves its files out of `.scratch/` and removes that `.gitignore` if it's exactly the one the plugin wrote. If `.scratch/` is then empty, it goes too; anything else you keep there stays. If git tracks the old progress file (for example, an agent committed it), the plugin leaves it where it is and keeps using it, so nothing changes in that repo.
 
+## Agent tools
+
+On Paseo 0.14 and later, Progress hands agents a tool for each common command, so recording progress needs nothing installed and every update names the agent that sent it. Paseo only gives plugin tools to agents while **Settings → your host → Agents → Enable Paseo tools** is on. It's off by default, and turning it on also gives agents Paseo's own tools for starting, messaging and stopping other agents. Progress never changes the setting. Once it's on, start a new chat or reload one to give it the tools.
+
+| Tool | Does what this command does |
+| --- | --- |
+| `progress_show` | `show` |
+| `progress_start` | `start` |
+| `progress_ticket_add` | `ticket add` |
+| `progress_ticket_update` | `ticket update` |
+| `progress_question_ask` | `question ask` |
+| `progress_question_answer` | `question answer` |
+| `progress_deliverable_add` | `deliverable add` |
+| `progress_activity_add` | `activity add` |
+| `progress_ticker` | `ticker set`, or `ticker clear` when the text is empty |
+| `progress_finish` | `finish` |
+| `paseo_progress` | Any command, given as the list of words you'd type after `paseo-progress` |
+
+Each tool runs the command inside the plugin, so it checks the same things and answers with the same words. Statuses and deliverable kinds are listed in the tool, so an agent can't send one the command doesn't know. Paths are relative to the agent's folder, like the command run there. Claude Code shows them as `mcp__paseo__progress_show` and so on, and holds them back until the agent searches for them. The skill tells agents to search.
+
+In the chat, a Progress tool call shows as one line of what it recorded, like "Added T01: Export button (30m)", beside the Progress icon. While the call runs, the line says what the tool is doing, like "Adding ticket…". A failed call shows its error in red. Tap the line to see everything the tool returned, such as the dashboard text from `progress_show`.
+
+<img src="images/6-chat-rows.png" alt="A chat with Progress tool calls as single lines: a started run, two added tickets, a failed update in red, and the dashboard text opened below Read the dashboard" width="600">
+
+**Agent tools** in Progress settings shows whether the setting is on and, while it's off, how to turn it on. A new worktree's empty panel says the same.
+
+<img src="images/7-empty-tools-note.png" alt="An empty Progress panel with the paseo-progress command example and a note on turning on Paseo tools" width="440">
+
+While it's on, the banner stops asking you to install the command and only offers it as a fallback. On Paseo 0.13 the panel never mentions tools. Reloading the plugin takes the tools away from a reply that's already running. Paseo gives them back before the chat's next message, and until then the skill has agents use the command.
+
 ## 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, 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. Paseo puts each plugin update in a new folder, so when Progress starts it repoints the links it made to that folder. If it can't, the button changes to **Update skill**. It never replaces a skill it didn't link; that folder is skipped. To read what agents get, open **View skill** under Agent Skills in Progress settings.
+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 has agents use the Progress tools when they have them and the command otherwise, 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. Paseo puts each plugin update in a new folder, so when Progress starts it repoints the links it made to that folder. If it can't, the button changes to **Update skill**. It never replaces a skill it didn't link; that folder is skipped. To read what agents get, open **View skill** under Agent Skills in Progress settings.
 
 From a terminal instead:
 
@@ -122,7 +154,7 @@ paseo-progress finish "Snapshots ship for all four tables"
 - 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. Markdown shows formatted, with links and images relative to the file's own folder; **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, and a PDF (up to 100 MB) shows there too. 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.
+- Subagents record their own progress. A Claude Code subagent can call the Progress tools too, and its updates carry its parent chat's agent id. 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.
 - `start` begins a fresh dashboard. Earlier runs stay in the file. Question references stay unique across runs.
 - `finish "<outcome>"` closes the run once every ticket is done or skipped, no question is open, and nothing is flagged stuck; otherwise it says what is left. The run stays on the dashboard, marked Finished with its outcome, and takes no more updates, so the next agent in the worktree starts a new run instead of adding to it.
 
@@ -133,7 +165,8 @@ The progress file, `progress.jsonl`, holds one JSON event per line, each with a
 ## Limitations
 
 - An agent hears about tickets other sessions added only when it next runs `paseo-progress`. One in the middle of a long step finds out when that step ends.
-- Nothing updates unless the agent runs `paseo-progress`. Agents need the skill, and an agent that skips the command leaves the dashboard behind.
+- Nothing updates unless the agent records it, with a Progress tool or `paseo-progress`. Agents need the skill, and an agent that skips it leaves the dashboard behind.
+- Agents get the Progress tools only on Paseo 0.14 and later, with Paseo tools turned on for the host. The setting also lets agents start, message and stop other agents, so Progress leaves it to you.
 - On Paseo 0.11 and later, an agent waiting on background subagents counts as idle. If those subagents record nothing, the dashboard shows "possibly stale" after 15 minutes while they're still working.
 - The command runs on the machine that hosts the Paseo daemon, and it needs Node.js 22.18 or later there.
 - Each worktree keeps its own dashboard. There's no view across worktrees.
@@ -145,6 +178,18 @@ The progress file, `progress.jsonl`, holds one JSON event per line, each with a
 
 ## Changelog
 
+### 1.14.0
+
+- [New] **Agents can record progress with Paseo tools.** On Paseo 0.14 and later, Progress hands agents a tool for each common command, like `progress_ticket_update` and `progress_question_ask`. Nothing needs installing, and every update names the agent that sent it. Agents get them once you turn on **Settings → your host → Agents → Enable Paseo tools**, which also lets them start, message and stop other agents. **Agent tools** in Progress settings shows whether it's on and how to turn it on. The skill now uses the tools when an agent has them and the `paseo-progress` command otherwise, so Paseo 0.13 and agents without the tools work as before.
+- [New] **Progress tool calls read plainly in the chat.** Instead of Paseo's generic tool row, each call shows the Progress icon and one line of what it recorded, like "Added T01: Export button (30m)". A failed call shows its error in red. Tap a row to see everything the tool returned.
+
+### 1.13.1
+
+- [Fixed] **Ticket tabs fit on a phone.** On a phone, a ticket's tabs used to wrap and leave Deliverables alone on a second line. They now stay in one row that you swipe sideways. When some tabs are out of sight, that edge of the row fades and shows an arrow you can tap. The tab you pick scrolls into view, and so does the one you had open when you come back to the ticket.
+- [Fixed] **Open chat stays on one line.** On a phone, the Open chat link beside a ticket's agent no longer wraps. The agent's name gets shorter instead.
+- [Fixed] **Larger question arrows in a phone's browser.** In the pill's popover, the arrows that step through questions and the Open Progress button now have the same finger-sized buttons in a phone's web browser as in the Paseo phone apps.
+- [Fixed] **Screen readers hear which tab is selected in the desktop and web apps.** They also hear whether the finished tickets and a write-up are shown or hidden. Before, only the phone apps passed this on.
+
 ### 1.13.0
 
 - [New] **PDF previews.** A PDF the agent records now opens in the preview in Paseo's desktop and web apps, with a loading percentage while it arrives. Any PDF you open in a Paseo tab now shows in that tab, up to 100 MB on desktop and 25 MB on a phone. A PDF deliverable also has a button beside Copy that opens it in a tab, which is how you see it on an iPhone or iPad.

package/client/chat-row-view.tsx

@@ -0,0 +1,78 @@
+import type { PluginTimelineItemProps } from "@getpaseo/plugin/client";
+import { Icon, ScrollView } from "@getpaseo/plugin/client/ui";
+import React, { useState } from "react";
+import { Platform, Pressable, Text, View } from "react-native";
+import { type ChatRow, chatRowText } from "./chat-row";
+import { useProgressLanguage } from "./language";
+
+const mono = () => (Platform.OS === "ios" ? "Menlo" : "monospace");
+
+// Sized like Paseo's own tool rows (ExpandableBadge in the app): 14px label,
+// 12px icon centered in a 22px slot, 8 by 4 padding. The -13 margin puts the
+// icon's glyph on the chat's text edge, where Paseo's rows put theirs.
+export function ChatRowView({ item, theme }: PluginTimelineItemProps<ChatRow>) {
+  const { colors } = theme;
+  const { messages: m } = useProgressLanguage();
+  const [expanded, setExpanded] = useState(false);
+  const [hovered, setHovered] = useState(false);
+  const row = item.data;
+  const { line, more } = chatRowText(row, m);
+  const failed = row.state === "failed";
+  const running = row.state === "running";
+  const open = expanded && more !== null;
+  // Only a row that opens lights up on hover, like Paseo's.
+  const active = more !== null && (hovered || expanded);
+  const iconColor = failed ? colors.statusDanger : active ? colors.foreground : colors.foregroundMuted;
+
+  const icon = active
+    ? <View style={{ marginLeft: -4, transform: [{ scale: 1.3 }, { rotate: expanded ? "90deg" : "0deg" }] }}><Icon name="ChevronRight" size={12} color={colors.foreground} /></View>
+    : <View style={{ marginLeft: -1, opacity: failed ? 0.8 : 1 }}><Icon name={failed ? "TriangleAlert" : "ListChecks"} size={12} color={iconColor} /></View>;
+
+  return (
+    <View style={{ marginHorizontal: -13 }}>
+      <Pressable
+        disabled={more === null}
+        onPress={() => setExpanded((value) => !value)}
+        onHoverIn={() => setHovered(true)}
+        onHoverOut={() => setHovered(false)}
+        accessibilityRole={more === null ? undefined : "button"}
+        aria-expanded={more === null ? undefined : expanded}
+        aria-busy={running}
+        style={({ pressed }) => ({
+          flexDirection: "row",
+          alignItems: "center",
+          borderRadius: 8,
+          borderWidth: 1,
+          borderColor: open ? colors.border : "transparent",
+          borderBottomLeftRadius: open ? 0 : 8,
+          borderBottomRightRadius: open ? 0 : 8,
+          backgroundColor: open ? colors.surface1 : "transparent",
+          paddingHorizontal: 8,
+          paddingVertical: 4,
+          opacity: pressed && more !== null ? 0.9 : 1,
+        })}
+      >
+        <View style={{ width: 22, height: 22, marginRight: 4, alignItems: "center", justifyContent: "center" }}>{icon}</View>
+        <Text
+          numberOfLines={1}
+          style={{
+            flexShrink: 1,
+            fontSize: 14,
+            color: failed ? colors.statusDanger : running || active ? colors.foreground : colors.foregroundMuted,
+            opacity: running ? 0.72 : 1,
+          }}
+        >
+          {line}
+        </Text>
+      </Pressable>
+      {open ? (
+        <View style={{ borderWidth: 1, borderTopWidth: 0, borderColor: colors.border, borderBottomLeftRadius: 8, borderBottomRightRadius: 8, overflow: "hidden" }}>
+          {/* Scrolling past the end stays in the output instead of moving the chat. */}
+          <ScrollView style={[{ maxHeight: 320 }, Platform.OS === "web" ? ({ overscrollBehavior: "contain" } as object) : null]} contentContainerStyle={{ paddingHorizontal: 12, paddingVertical: 8 }}>
+            <Text selectable style={{ color: failed ? colors.statusDanger : colors.foreground, fontFamily: mono(), fontSize: 12, lineHeight: 18 }}>{more}</Text>
+          </ScrollView>
+        </View>
+      ) : null}
+    </View>
+  );
+}

package/client/chat-row.ts

@@ -0,0 +1,83 @@
+import type { PluginTimelineTransformerContribution } from "@getpaseo/plugin/client";
+import { z } from "zod";
+import { PROGRESS_TOOL_NAMES, progressToolName } from "../shared/tools";
+import type { ProgressMessages } from "./messages";
+
+export const CHAT_ROW_KIND = "tool-call";
+export const CHAT_ROW_VERSION = 1;
+
+const tool = z.enum(PROGRESS_TOOL_NAMES);
+
+export const chatRowSchema = z.discriminatedUnion("state", [
+  z.object({ tool, state: z.literal("running") }),
+  z.object({ tool, state: z.literal("done"), output: z.string() }),
+  z.object({ tool, state: z.literal("failed"), error: z.string() }),
+  z.object({ tool, state: z.literal("canceled") }),
+]);
+
+export type ChatRow = z.output<typeof chatRowSchema>;
+
+type ToolCall = Parameters<PluginTimelineTransformerContribution<"tool_call">["transform"]>[0]["item"];
+
+function isRecord(value: unknown): value is Record<string, unknown> {
+  return typeof value === "object" && value !== null && !Array.isArray(value);
+}
+
+// The text a tool call carries, or undefined when its shape is unfamiliar.
+// Claude Code stores the result as { output: text } and an error as
+// { content: text or [{ text }] }; Codex keeps the MCP result { content: [{ text }] }.
+function readText(value: unknown): string | undefined {
+  if (value === null || value === undefined) return "";
+  if (typeof value === "string") return value;
+  if (Array.isArray(value)) {
+    const parts = value.map((part) => (typeof part === "string" ? part : isRecord(part) && typeof part.text === "string" ? part.text : undefined));
+    return parts.every((part) => part !== undefined) ? parts.join("\n") : undefined;
+  }
+  if (!isRecord(value)) return undefined;
+  const key = ["output", "content", "text", "message"].find((name) => name in value);
+  return key ? readText(value[key]) : undefined;
+}
+
+// A call to a Progress tool becomes the row's data. Anything else, or a call
+// whose detail can't be read, stays undefined so Paseo draws its own row.
+export function chatRow(item: ToolCall): ChatRow | undefined {
+  const name = progressToolName(item.name);
+  if (!name) return undefined;
+  if (item.status === "running") return { tool: name, state: "running" };
+  if (item.status === "canceled") return { tool: name, state: "canceled" };
+  if (item.status === "failed") {
+    const error = readText(item.error);
+    return error === undefined ? undefined : { tool: name, state: "failed", error };
+  }
+  const detail: unknown = item.detail;
+  if (!isRecord(detail) || !("output" in detail)) return undefined;
+  const output = readText(detail.output);
+  if (output === undefined) return undefined;
+  // Codex reports a tool's own error inside a completed MCP result.
+  if (isRecord(detail.output) && detail.output.isError === true) return { tool: name, state: "failed", error: output };
+  return { tool: name, state: "done", output };
+}
+
+export function transformChatRow({ item }: { item: ToolCall }) {
+  const data = chatRow(item);
+  return data && { items: [{ type: "plugin" as const, kind: CHAT_ROW_KIND, version: CHAT_ROW_VERSION, data }] };
+}
+
+// What the row says: one line, and the full text the row opens to. The line
+// truncates on a narrow chat, so any text at all can be opened.
+export function chatRowText(row: ChatRow, m: ProgressMessages): { line: string; more: string | null } {
+  const labels = m.toolRow[row.tool];
+  const firstLine = (text: string) => text.split("\n").map((line) => line.trim()).find(Boolean) ?? "";
+  const withMore = (line: string, text: string) => ({ line, more: text.trim() || null });
+  switch (row.state) {
+    case "running":
+      return { line: labels.running, more: null };
+    case "canceled":
+      return { line: m.toolRowCanceled(labels.name), more: null };
+    case "failed":
+      return withMore(firstLine(row.error) || m.toolRowFailed(labels.name), row.error);
+    case "done":
+      // Show starts with the worktree's path; the dashboard is what the agent read.
+      return withMore(row.tool === "progress_show" ? labels.name : firstLine(row.output) || labels.name, row.output);
+  }
+}

package/client/dialog-stack.tsx

@@ -25,7 +25,7 @@ export type Step =
 
 // Paseo gives each dialog its own backdrop, so opening a second one darkens
 // the screen while the first fades out; steps swap content inside this one instead.
-export function StackedDialog({ colors, root, onClose, questions = [], dashboard, now, live = true, context }: {
+export function StackedDialog({ colors, root, onClose, questions = [], dashboard, now, live = true, compact = false, context }: {
   colors: Colors;
   root: Step | null;
   onClose(): void;
@@ -34,6 +34,8 @@ export function StackedDialog({ colors, root, onClose, questions = [], dashboard
   dashboard?: Dashboard;
   now: number;
   live?: boolean;
+  // Paseo's phone-sized layout; the ticket's tabs scroll sideways there.
+  compact?: boolean;
   context: AttachmentContext;
 }) {
   // Paseo's Modal keeps drawing its content while it fades out, so closing keeps the steps.
@@ -103,7 +105,7 @@ export function StackedDialog({ colors, root, onClose, questions = [], dashboard
       ) : (
         <>
           {ticket && dashboard ? (
-            <TicketStoryView colors={colors} dashboard={dashboard} ticket={ticket} now={now} live={live} context={context} onOpenAgent={openAgent}
+            <TicketStoryView colors={colors} dashboard={dashboard} ticket={ticket} now={now} live={live} compact={compact} context={context} onOpenAgent={openAgent}
               onOpenAttachment={openAttachment} onOpenQuestion={(id) => push({ kind: "question", id })} />
           ) : null}
           {question ? (

package/client/launcher.tsx

@@ -5,7 +5,7 @@ import React from "react";
 import { Text, View } from "react-native";
 import { PressScale, Presence } from "./motion";
 import { raised } from "./surfaces";
-import { getLauncherStatus, getSkillStatus, installLauncher, installSkill, type LauncherStatus, type SkillStatus } from "../shared/rpc";
+import { getLauncherStatus, getSkillStatus, getToolsStatus, installLauncher, installSkill, type LauncherStatus, type SkillStatus, type ToolsState } from "../shared/rpc";
 import { messagesFor, type ProgressMessages } from "./i18n";
 import { errorText } from "./errors";
 import { useProgressLanguage } from "./language";
@@ -34,6 +34,22 @@ export function launcherNotice(status: LauncherStatus, m: ProgressMessages = mes
   }
 }
 
+// With Paseo tools on, the command is only a fallback: the banner offers an
+// install or update and stays quiet otherwise.
+export function setupNotice(status: LauncherStatus, tools: ToolsState, m: ProgressMessages = messagesFor("en")): { text: string; action?: string } | null {
+  const notice = launcherNotice(status, m);
+  if (tools !== "on") return notice;
+  return notice?.action ? { text: m.toolsOn, action: notice.action } : null;
+}
+
+// Whether agents get the Progress tools, or null until known. A Paseo that
+// can't say reads as 0.13: the command is how agents record progress.
+export function useToolsState(hostId: string): ToolsState | null {
+  const fetchStatus = useRpc(getToolsStatus);
+  const status = useQuery({ queryKey: ["progress", "tools", hostId], queryFn: () => fetchStatus({}), staleTime: 60_000, retry: false });
+  return status.data?.state ?? (status.isError ? "unsupported" : null);
+}
+
 // What the skill banner says, or null when every agent folder has the skill.
 export function skillNotice(status: SkillStatus, m: ProgressMessages = messagesFor("en")): { text: string; action?: string } | null {
   const folders = (state: string) => status.targets.filter((target) => target.state === state).map((target) => target.path.replace(/[\\/]paseo-progress$/, ""));
@@ -66,7 +82,8 @@ export function LauncherBanner({ colors, host }: { colors: Colors; host: PluginW
     },
     onError: (error) => toast.error(errorText(error, m.installCommandFailure)),
   });
-  const notice = status.data ? launcherNotice(status.data, m) : null;
+  const tools = useToolsState(host.id);
+  const notice = status.data && tools ? setupNotice(status.data, tools, m) : null;
   return <SetupBanner colors={colors} icon="Terminal" notice={notice} pending={mutation.isPending} onPress={() => mutation.mutate()} />;
 }
 

package/client/locales/en.ts

@@ -33,6 +33,31 @@ export const messages: ProgressMessages = {
   openSettings: "Open Progress settings",
   noProgress: "No progress recorded yet",
   emptyIntro: ["An agent working in this worktree records progress with the ", " command. It shows up here as soon as the first run starts."],
+  emptyIntroTools: "An agent working in this worktree records progress with the Progress tools Paseo gives it. It shows up here as soon as the first run starts.",
+  toolsOn: "Agents record progress with Paseo tools. The paseo-progress command is a fallback for agents without them.",
+  toolsNote: [
+    "Let agents record progress without the command.",
+    "Paseo can hand agents the Progress tools directly. Nothing to install, and every update shows which agent sent it. Turning this on also lets agents start, message and stop other agents. To turn it on, open Settings → your host → Agents → Enable Paseo tools, then start a new chat or reload one.",
+  ],
+  agentTools: "Agent tools",
+  paseoTools: "Paseo tools",
+  toolsStateOn: "On",
+  toolsStateOff: "Off",
+  toolRow: {
+    progress_show: { running: "Reading the dashboard…", name: "Read the dashboard" },
+    progress_start: { running: "Starting run…", name: "Start run" },
+    progress_ticket_add: { running: "Adding ticket…", name: "Add ticket" },
+    progress_ticket_update: { running: "Updating ticket…", name: "Update ticket" },
+    progress_question_ask: { running: "Asking question…", name: "Ask question" },
+    progress_question_answer: { running: "Recording answer…", name: "Record answer" },
+    progress_deliverable_add: { running: "Adding deliverable…", name: "Add deliverable" },
+    progress_activity_add: { running: "Logging activity…", name: "Log activity" },
+    progress_ticker: { running: "Updating the now line…", name: "Update the now line" },
+    progress_finish: { running: "Finishing run…", name: "Finish run" },
+    paseo_progress: { running: "Recording progress…", name: "Record progress" },
+  },
+  toolRowCanceled: (name) => `${name}: canceled`,
+  toolRowFailed: (name) => `${name}: failed`,
   finished: "Finished",
   lastUpdated: "Last updated ",
   activity: "Activity",

package/client/locales/zh-CN.ts

@@ -33,6 +33,31 @@ export const messages: ProgressMessages = {
   openSettings: "打开 Progress 设置",
   noProgress: "尚未记录进度",
   emptyIntro: ["在此工作树中工作的智能体会通过 ", " 命令记录进度。首次运行开始后，进度就会显示在这里。"],
+  emptyIntroTools: "在此工作树中工作的智能体会通过 Paseo 提供的 Progress 工具记录进度。首次运行开始后，进度就会显示在这里。",
+  toolsOn: "智能体通过 Paseo tools 记录进度。没有这些工具的智能体会改用 paseo-progress 命令。",
+  toolsNote: [
+    "让智能体无需命令即可记录进度。",
+    "Paseo 可以直接把 Progress 工具交给智能体。无需安装，每条更新都会显示是哪个智能体发送的。开启后，智能体还能启动其他智能体、给它们发消息，或停止它们。开启方法：打开 设置 → 你的主机 → Agents → 启用 Paseo tools，然后新建对话或重新加载一个对话。",
+  ],
+  agentTools: "智能体工具",
+  paseoTools: "Paseo tools",
+  toolsStateOn: "已开启",
+  toolsStateOff: "已关闭",
+  toolRow: {
+    progress_show: { running: "正在读取进度面板…", name: "读取进度面板" },
+    progress_start: { running: "正在开始运行…", name: "开始运行" },
+    progress_ticket_add: { running: "正在添加工单…", name: "添加工单" },
+    progress_ticket_update: { running: "正在更新工单…", name: "更新工单" },
+    progress_question_ask: { running: "正在提问…", name: "提问" },
+    progress_question_answer: { running: "正在记录回答…", name: "记录回答" },
+    progress_deliverable_add: { running: "正在添加交付物…", name: "添加交付物" },
+    progress_activity_add: { running: "正在记录动态…", name: "记录动态" },
+    progress_ticker: { running: "正在更新当前动态…", name: "更新当前动态" },
+    progress_finish: { running: "正在结束运行…", name: "结束运行" },
+    paseo_progress: { running: "正在记录进度…", name: "记录进度" },
+  },
+  toolRowCanceled: (name) => `${name}：已取消`,
+  toolRowFailed: (name) => `${name}：失败`,
   finished: "已结束",
   lastUpdated: "最后更新于 ",
   activity: "动态",

package/client/messages.ts

@@ -2,6 +2,7 @@ import type { PiecedKind } from "../shared/attachments";
 import type { TicketStatus } from "../shared/events";
 import type { QuestionMode } from "../shared/question-modes";
 import type { NoteKind } from "../shared/whats-new";
+import type { ProgressToolName } from "../shared/tools";
 
 // Text before and after a value the UI draws in its own style.
 export type Around = readonly [before: string, after: string];
@@ -16,6 +17,19 @@ export interface ProgressMessages {
   openSettings: string;
   noProgress: string;
   emptyIntro: Around;
+  // Paseo 0.14 can hand agents the Progress tools. The note offers it while the host's setting is off.
+  toolsOn: string;
+  emptyIntroTools: string;
+  toolsNote: readonly [lead: string, body: string];
+  agentTools: string;
+  paseoTools: string;
+  toolsStateOn: string;
+  toolsStateOff: string;
+  // A Progress tool call in the chat: the line while it runs, and the tool's
+  // name for a row whose output has nothing better to show.
+  toolRow: Record<ProgressToolName, { running: string; name: string }>;
+  toolRowCanceled: (name: string) => string;
+  toolRowFailed: (name: string) => string;
   finished: string;
   lastUpdated: string;
   activity: string;

package/client/panel.tsx

@@ -1,7 +1,7 @@
 import { type PluginWorkspacePanelProps, useRpc, useWorkspace } from "@getpaseo/plugin/client";
 import { Icon } from "@getpaseo/plugin/client/ui";
 import { DeliverablesList } from "./deliverables";
-import { LauncherBanner, SkillBanner } from "./launcher";
+import { LauncherBanner, SkillBanner, useToolsState } from "./launcher";
 import { WhatsNewBanner } from "./whats-new";
 import { HistoryRow } from "./history";
 import { AnsweredQuestionsList, QuestionsSection } from "./questions";
@@ -65,7 +65,7 @@ function WorkspaceProgress({ theme, workspaceId, host, layout, navigation, openS
       <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} openSettings={openSettings} /> : null}</Presence>
+      <Presence show={Boolean(result && !result.configured)}>{result && !result.configured ? <EmptyState colors={colors} hostId={host.id} 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} openSettings={openSettings} dashboard={result.dashboard} agentRunning={agentRunning} compact={layout.compact}
         workspaceId={workspaceId} workspaceDirectory={result.root} file={result.file} navigation={navigation} /> : null}
@@ -101,8 +101,9 @@ function SettingsButton({ colors, onPress }: { colors: Colors; onPress(): void }
   );
 }
 
-function EmptyState({ colors, file, openSettings }: { colors: Colors; file: string; openSettings(): void }) {
+function EmptyState({ colors, hostId, file, openSettings }: { colors: Colors; hostId: string; file: string; openSettings(): void }) {
   const { messages: m } = useProgressLanguage();
+  const tools = useToolsState(hostId);
   return (
     <View style={{ padding: 12, paddingTop: 20, gap: 10 }}>
       <View style={{ flexDirection: "row", alignItems: "center", gap: 8 }}>
@@ -113,14 +114,26 @@ function EmptyState({ colors, file, openSettings }: { colors: Colors; file: stri
         <View style={{ flex: 1 }} />
         <SettingsButton colors={colors} onPress={openSettings} />
       </View>
-      <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>
-        {m.emptyIntro[0]}<Text style={{ color: colors.foreground }}>paseo-progress</Text>{m.emptyIntro[1]}
-      </Text>
-      <View style={{ backgroundColor: colors.surface1, borderRadius: 6, padding: 10 }}>
-        <Text selectable style={{ color: colors.foreground, fontFamily: mono(), fontSize: 12, lineHeight: 18 }}>
-          {`paseo-progress start "Build the export feature"\npaseo-progress ticket add "Ticket 01: Export button" --estimate 60`}
+      {tools === "on" ? (
+        <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>{m.emptyIntroTools}</Text>
+      ) : (
+        <>
+          <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>
+            {m.emptyIntro[0]}<Text style={{ color: colors.foreground }}>paseo-progress</Text>{m.emptyIntro[1]}
+          </Text>
+          <View style={{ backgroundColor: colors.surface1, borderRadius: 6, padding: 10 }}>
+            <Text selectable style={{ color: colors.foreground, fontFamily: mono(), fontSize: 12, lineHeight: 18 }}>
+              {`paseo-progress start "Build the export feature"\npaseo-progress ticket add "Ticket 01: Export button" --estimate 60`}
+            </Text>
+          </View>
+        </>
+      )}
+      {/* The other way to start, next to the command it replaces. */}
+      {tools === "off" ? (
+        <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>
+          <Text style={{ color: colors.foreground, fontWeight: "600" }}>{m.toolsNote[0]}</Text> {m.toolsNote[1]}
         </Text>
-      </View>
+      ) : null}
       {/* So people know nothing lands in the repo. */}
       <Text style={{ color: colors.foregroundMuted, fontSize: 12, lineHeight: 18 }}>
         {m.savedOutside[0]}<Text selectable style={{ color: colors.foreground }}>{file}</Text>{m.savedOutside[1]}
@@ -253,7 +266,7 @@ function DashboardView({ colors, dashboard, agentRunning, compact, workspaceId,
             ) : (
               <TicketList colors={colors} dashboard={dashboard} live={live} now={now} workspaceId={workspaceId} onOpen={setOpenTicket} />
             )}
-            <TicketDialogs colors={colors} dashboard={dashboard} openId={openTicket} setOpenId={setOpenTicket} now={now} live={live} context={attachmentContext} />
+            <TicketDialogs colors={colors} dashboard={dashboard} openId={openTicket} setOpenId={setOpenTicket} now={now} live={live} compact={compact} context={attachmentContext} />
           </Card>
           </Presence>
         </View>
@@ -468,7 +481,7 @@ function FinishedRow({ colors, tickets, shown, onPress }: { colors: Colors; tick
   const chevron = shown ? "ChevronUp" : "ChevronDown";
   const narrow = useNarrow();
   return (
-    <PressableRow colors={colors} accessibilityRole="button" accessibilityState={{ expanded: shown }}
+    <PressableRow colors={colors} accessibilityRole="button" aria-expanded={shown}
       accessibilityLabel={m.toggleFinished(shown, label)} onPress={onPress}
       style={{ flexDirection: "row", alignItems: "flex-start", gap: 10, paddingHorizontal: 10, paddingVertical: 8, borderTopWidth: 1, borderTopColor: colors.border }}>
       <View style={{ width: 16, paddingTop: 2, alignItems: "center" }}>

package/client/pill-popover.tsx

@@ -32,8 +32,8 @@ export function AttentionPopover({ theme, host, layout, workspaceId, close, open
   const colors = theme.colors;
   // Paseo draws the desktop popover on surface1 and the phone sheet on surface0.
   const onSurface1 = !layout.compact;
-  // The phone apps are pressed with a finger.
-  const touch = layout.platform !== "web";
+  // Pressed with a finger: the phone apps, and any phone-sized screen, browsers included.
+  const touch = layout.compact || layout.platform !== "web";
   const directory = useWorkspace(workspaceId, (workspace) => workspace.directory);
   const query = useDashboard(host.id, workspaceId, directory);
   const dashboard = query.data?.configured ? query.data.dashboard : null;
@@ -210,7 +210,7 @@ function StepButton({ colors, touch, onSurface1, icon, label, target, onPress }:
   const button = onSurface1 ? { rest: colors.surface2, pressed: colors.surface1 } : { rest: colors.surface1, pressed: colors.surface2 };
   const size = stepSize(touch);
   return (
-    <PressScale accessibilityRole="button" accessibilityLabel={label} accessibilityState={{ disabled: !target }} disabled={!target}
+    <PressScale accessibilityRole="button" accessibilityLabel={label} disabled={!target}
       onPress={target ? () => onPress(target) : undefined} hitSlop={touch ? stepSlop : undefined}
       style={({ pressed }) => ({ width: size, height: size, alignItems: "center", justifyContent: "center", borderRadius: touch ? 8 : 4, opacity: target ? 1 : 0.35, ...raised(colors),
         backgroundColor: pressed ? button.pressed : button.rest })}>

package/client/settings.tsx

@@ -1,6 +1,6 @@
 import { type PluginSurfaceProps, useRpc, useSettings } from "@getpaseo/plugin/client";
 import { Icon, Modal } from "@getpaseo/plugin/client/ui";
-import { SettingsAction, SettingsCard, SettingsSelect } from "@getpaseo/plugin/client/ui";
+import { SettingsAction, SettingsCard, SettingsRow, SettingsSelect } from "@getpaseo/plugin/client/ui";
 import { useQuery } from "@tanstack/react-query";
 import React, { type ReactNode, useState } from "react";
 import { Text, View } from "react-native";
@@ -10,11 +10,11 @@ import { questionSettings, LANGUAGE_PREFERENCES } from "../shared/settings";
 import { parseBlocks, withoutTitle } from "../shared/blocks";
 import { errorText } from "./errors";
 import { useProgressLanguage } from "./language";
-import { useSkill } from "./launcher";
+import { useSkill, useToolsState } from "./launcher";
 import { BlockView } from "./blocks";
 
 export function QuestionSettings({ theme, host }: PluginSurfaceProps) {
-  return <><QuestionModeSettings theme={theme} /><DisplaySettings theme={theme} /><SkillSettings colors={theme.colors} hostId={host.id} /></>;
+  return <><QuestionModeSettings theme={theme} /><DisplaySettings theme={theme} /><SkillSettings colors={theme.colors} hostId={host.id} /><ToolsSettings colors={theme.colors} hostId={host.id} /></>;
 }
 
 type Colors = PluginSurfaceProps["theme"]["colors"];
@@ -76,6 +76,22 @@ function SkillSettings({ colors, hostId }: { colors: Colors; hostId: string }) {
   );
 }
 
+// Paseo 0.14 and later only: whether agents get the Progress tools, and how to turn them on.
+function ToolsSettings({ colors, hostId }: { colors: Colors; hostId: string }) {
+  const { messages: m } = useProgressLanguage();
+  const tools = useToolsState(hostId);
+  if (tools !== "on" && tools !== "off") return null;
+  return (
+    <Section colors={colors} icon="Wrench" title={m.agentTools}>
+      <SettingsCard>
+        <SettingsRow label={m.paseoTools} hint={tools === "on" ? m.toolsOn : m.toolsNote[1]}>
+          <Text style={{ color: colors.foregroundMuted, fontSize: 13 }}>{tools === "on" ? m.toolsStateOn : m.toolsStateOff}</Text>
+        </SettingsRow>
+      </SettingsCard>
+    </Section>
+  );
+}
+
 function QuestionModeSettings({ theme }: Pick<PluginSurfaceProps, "theme">) {
   const { messages: m } = useProgressLanguage();
   const settings = useSettings(questionSettings);