pi-squad 0.19.4 → 0.19.5

package/CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.19.5] - 2026-07-24
+
+### Fixed
+
+- Terminal task failures are now reported to the main session immediately when the rest of the squad keeps running (new `squad-task-failed` notification with the exact task, agent, error, and repair guidance). Previously an individual agent death — e.g. `Agent devops exited before RPC response` — was invisible in chat until the whole squad stalled or finished. When no runnable work remains, the existing `squad-failed` summary is sent instead, never both.
+- A task that completes after an interim failure (spawn retry, RPC race during reopen) no longer displays the stale error annotation forever; successful completion clears `task.error`.
+
 ## [0.19.4] - 2026-07-24
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-squad",
-  "version": "0.19.4",
+  "version": "0.19.5",
   "description": "Multi-agent collaboration extension for pi — task decomposition, dependency management, parallel execution, TUI panel",
   "type": "module",
   "scripts": {

package/src/scheduler-runtime.ts

@@ -66,6 +66,29 @@ export function wireSchedulerEvents(pi: ExtensionAPI, scheduler: Scheduler, squa
 				}
 				break;
 			}
+			case "task_failed": {
+				// A task died terminally while the squad continues. Without this the
+				// main session learns about individual failures only when the whole
+				// squad later stalls or finishes. When no runnable work remains the
+				// imminent squad_failed event carries the failure summary instead, so
+				// skip the task-level message to avoid duplicate notifications.
+				try {
+					const tasks = store.loadAllTasks(squadId);
+					const squadContinues = tasks.some((task) => task.status === "in_progress" || task.status === "pending");
+					if (!squadContinues) break;
+					const failed = tasks.find((task) => task.id === event.taskId);
+					pi.sendMessage({
+						customType: "squad-task-failed",
+						content: `[squad] Task '${event.taskId}'${failed ? ` (${failed.agent})` : ""} FAILED in '${squadId}' while other tasks continue.\n` +
+							`Error: ${event.message ?? failed?.error ?? "unknown"}\n` +
+							`Dependents of this task stay blocked. Repair now with squad_modify — resume_task to retry it, set_dependencies to reroute, or cancel_task if obsolete — or the squad will stall after the remaining tasks finish.`,
+						display: true,
+					}, { triggerTurn: true, deliverAs: "followUp" });
+				} catch (error) {
+					logError("squad-scheduler", `task-failed delivery failed for ${squadId}/${event.taskId}: ${(error as Error).message}`);
+				}
+				break;
+			}
 			case "squad_failed": {
 				const tasks = store.loadAllTasks(squadId);
 				const failed = tasks.filter((task) => task.status === "failed");

package/src/scheduler.ts

@@ -994,8 +994,11 @@ export class Scheduler {
 			.filter((m) => m.from === task.agent && (m.type === "text" || m.type === "done"));
 		const output = agentMessages.map((m) => m.text).join("\n");
 
+		// Clear any interim failure annotation (spawn retry, RPC race): a task
+		// that ultimately completed must not display a stale error forever.
 		store.updateTaskStatus(this.squadId, taskId, "done", {
 			output: output || "Task completed",
+			error: null,
 			completed: store.now(),
 		});