@arhen/pi-core-subagent 1.2.2 → 1.3.0

package/README.md

@@ -133,7 +133,7 @@ Background + intercom:
 | Tool | Purpose |
 |---|---|
 | `subagent` | single / `tasks` (parallel or graph via `needs`) / `chain` (`{previous}`); `background:true` fire-and-forget; `allowIntercom:true` enables child talk tools; `notifyPerTask: true` wakes you as each task completes (default off) |
-| `subagent_status` | live per-task snapshot (non-blocking) |
+| `subagent_status` | live per-task snapshot (non-blocking), including each child's session file path |
 | `subagent_result` | full output of a run or one task |
 | `await_subagent` | block until a run finishes (optional `timeoutMs`) |
 | `reply_subagent` | answer a child's `ask_parent` question |
@@ -161,6 +161,23 @@ Read-only pane over the session's subagents:
 - `x` then `y` — abort ONE subagent (only mutation; `n`/any other key cancels)
 - `esc` — close
 
+## Watching a child from outside
+
+`subagent_status` returns each running child's session file (JSONL). Children are `AgentSession`s in this process — they have no TTY — but their transcript is a real file, so any external viewer can follow one:
+
+```sh
+tail -f /path/from/subagent_status.jsonl
+```
+
+In a terminal multiplexer, that is a pane per agent — e.g. with [Herdr](https://herdr.dev):
+
+```sh
+herdr pane split --current --direction right
+herdr pane run w1:p2 "tail -f /path/from/subagent_status.jsonl"
+```
+
+The extension has no multiplexer integration and does not want one: it exposes the path, your agent already knows how to drive its own terminal. For an in-pi view of the same stream, use [`/subagents peek`](#peek--subagents-peek-or-ctrlshifta).
+
 ## Context budget
 
 - Parent tools: 6 schemas with short descriptions. **No catalog, no context hook** — nothing injected per request.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arhen/pi-core-subagent",
-  "version": "1.2.2",
+  "version": "1.3.0",
   "type": "module",
   "description": "pi extension: fast in-process subagents with a dependency-graph scheduler (needs edges gate tasks and carry upstream output into dependent prompts), plus background runs, intercom and agent-to-agent mailbox. Leader defines agents inline.",
   "license": "MIT",

package/src/index.ts

@@ -1473,14 +1473,18 @@ export default function (pi: ExtensionAPI) {
 	pi.registerTool<typeof RunIdParam, { run?: RunSnapshot }>({
 		name: "subagent_status",
 		label: "Subagent Status",
-		description: "Live status of a subagent run (non-blocking): per-task state.",
+		description: "Live status of a subagent run (non-blocking): per-task state, plus each child's session file path (JSONL) so you can tail it from outside — e.g. in a terminal multiplexer pane.",
 		promptSnippet: "Check progress of a subagent run.",
 		parameters: RunIdParam,
 		async execute(_id, params) {
 			const { runId } = params as { runId: string };
 			const run = manager.getRun(runId);
 			if (!run) return { content: [{ type: "text", text: `Unknown runId: ${runId}` }], isError: true, details: {} };
-			return { content: [{ type: "text", text: compactLines(run).join("\n") }], details: { run: cloneRun(run) } };
+			// Session file paths are the one primitive an outside tool needs: `tail -f` it in a
+			// multiplexer pane, a log viewer, anything. Cheaper than owning a pane integration.
+			const files = run.tasks.filter((t) => t.sessionFile).map((t) => `${t.id} (${t.agent}): ${t.sessionFile}`);
+			const text = [compactLines(run).join("\n"), ...(files.length > 0 ? ["", "Live session files (tail -f to watch):", ...files] : [])].join("\n");
+			return { content: [{ type: "text", text }], details: { run: cloneRun(run) } };
 		},
 	});