@trevonistrevon/pi-loop 0.1.3 → 0.1.5

package/dist/index.js

@@ -65,7 +65,7 @@ export default function (pi) {
     const widget = new LoopWidget(store, undefined, monitorManager);
     scheduler = new CronScheduler(store, onLoopFire);
     widget.setScheduler(scheduler);
-    triggerSystem = new TriggerSystem(pi, scheduler);
+    triggerSystem = new TriggerSystem(pi, scheduler, store);
     // ── pi-tasks integration ──
     let tasksAvailable = false;
     const _PROTOCOL_VERSION = 1;
@@ -142,7 +142,7 @@ export default function (pi) {
             widget.setStore(store);
             scheduler = new CronScheduler(store, onLoopFire);
             widget.setScheduler(scheduler);
-            triggerSystem = new TriggerSystem(pi, scheduler);
+            triggerSystem = new TriggerSystem(pi, scheduler, store);
         }
         storeUpgraded = true;
     }
@@ -402,13 +402,17 @@ Use "pause" to temporarily stop a loop without removing it. Use "delete" to perm
     pi.registerTool({
         name: "MonitorCreate",
         label: "MonitorCreate",
-        description: `Start a background command and stream its output via pi events. Optionally auto-notify when done.
+        description: `Run a shell command in the background and get notified when it finishes. The core tool for async/parallel work.
 
-The monitor runs a shell command in the background. Each output line is emitted as a "monitor:output" pi event. Use this to watch logs, tail files, poll APIs, run experiments, etc.
+Fire off a build check, CI monitor, experiment, script, or any slow command — then keep working. Output streams back as "monitor:output" events. When the process exits, "monitor:done" fires (or "monitor:error" on failure).
+
+If you pass onDone with a prompt, the monitor auto-creates a one-shot completion loop — you get a system reminder with the exit code and output line count. No need to poll or create a separate loop.
+
+DO NOT use raw Bash while/sleep/for loops to watch something. DO NOT run slow commands inline that could be offloaded. Use MonitorCreate to run work in parallel while you continue.
 
 ## When to Use
 
-Use this tool to:\n- Start a long-running experiment and get notified when it finishes\n- Watch a log file or build output in the background\n- Poll an API and stream results\n- Run any background command whose output you want to track
+Default to MonitorCreate for any long-running or background work:\n- Watch a CI/CD build (hut, gh, curl polling) while you work on something else\n- Run experiments, benchmarks, or training scripts in parallel\n- Tail a log or poll an API endpoint\n- Fire off a slow curl/fetch and check the result later\n- Run any script or command you don't need to wait on inline
 
 ## Events emitted
 
@@ -416,10 +420,11 @@ Use this tool to:\n- Start a long-running experiment and get notified when it fi
 
 ## onDone — auto-notify on completion
 
-Pass onDone with a prompt and the monitor auto-creates a one-shot loop that fires when the process exits. The system reminder includes the exit code and output line count. No need to create a separate LoopCreate or poll MonitorList.\n\nExample: MonitorCreate command="python train.py" onDone="Check training results and report best loss"`,
+Pass onDone with a prompt and the monitor auto-creates a one-shot loop that fires when the process exits. The system reminder includes the exit code and output line count.\n\nExample: MonitorCreate command="python train.py" onDone="Check training results and report best loss"\nExample: MonitorCreate command="hut builds show 1769753" onDone="Analyze the build result and report status"`,
         promptGuidelines: [
-            "Use onDone to auto-notify when a long-running command finishes — no need for a separate LoopCreate.",
-            "When starting experiments or benchmarks, pass onDone so the agent automatically picks up the results.",
+            "Default to MonitorCreate for any long-running or background command — releases the agent to keep working on other tasks in parallel.",
+            "When the user asks to monitor CI builds, watch a build, check a remote job, or run an experiment, use MonitorCreate instead of inline bash/curl/wait.",
+            "Use onDone to auto-notify when a background command finishes — the agent will pick up the results automatically.",
         ],
         parameters: Type.Object({
             command: Type.String({ description: "Shell command to run in background" }),

package/dist/trigger-system.d.ts

@@ -1,13 +1,15 @@
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import type { CronScheduler } from "./scheduler.js";
+import type { LoopStore } from "./store.js";
 import type { LoopEntry } from "./types.js";
 export declare class TriggerSystem {
     private pi;
     private scheduler;
+    private store;
     private eventSubscriptions;
     private hybridTimers;
     private lastFireTime;
-    constructor(pi: ExtensionAPI, scheduler: CronScheduler);
+    constructor(pi: ExtensionAPI, scheduler: CronScheduler, store: LoopStore);
     start(): void;
     stop(): void;
     add(entry: LoopEntry): void;

package/dist/trigger-system.js

@@ -1,12 +1,14 @@
 export class TriggerSystem {
     pi;
     scheduler;
+    store;
     eventSubscriptions = new Map();
     hybridTimers = new Map();
     lastFireTime = new Map();
-    constructor(pi, scheduler) {
+    constructor(pi, scheduler, store) {
         this.pi = pi;
         this.scheduler = scheduler;
+        this.store = store;
     }
     start() {
         this.scheduler.start();
@@ -94,6 +96,10 @@ export class TriggerSystem {
             trigger: entry.trigger,
             timestamp: Date.now(),
         });
+        if (!entry.recurring) {
+            this.remove(entry.id);
+            this.store.update(entry.id, { status: "expired" });
+        }
     }
     matchesFilter(data, filter) {
         if (!filter)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trevonistrevon/pi-loop",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "A pi extension for cron/event-based agent re-wake loops and background process monitoring.",
   "author": "trevonistrevon",
   "license": "MIT",

package/src/index.ts

@@ -69,7 +69,7 @@ export default function (pi: ExtensionAPI) {
 
   scheduler = new CronScheduler(store, onLoopFire);
   widget.setScheduler(scheduler);
-  triggerSystem = new TriggerSystem(pi, scheduler);
+  triggerSystem = new TriggerSystem(pi, scheduler, store);
 
   // ── pi-tasks integration ──
   let tasksAvailable = false;
@@ -148,7 +148,7 @@ export default function (pi: ExtensionAPI) {
       widget.setStore(store);
       scheduler = new CronScheduler(store, onLoopFire);
       widget.setScheduler(scheduler);
-      triggerSystem = new TriggerSystem(pi, scheduler);
+      triggerSystem = new TriggerSystem(pi, scheduler, store);
     }
     storeUpgraded = true;
   }
@@ -439,13 +439,17 @@ Use "pause" to temporarily stop a loop without removing it. Use "delete" to perm
   pi.registerTool({
     name: "MonitorCreate",
     label: "MonitorCreate",
-    description: `Start a background command and stream its output via pi events. Optionally auto-notify when done.
+    description: `Run a shell command in the background and get notified when it finishes. The core tool for async/parallel work.
 
-The monitor runs a shell command in the background. Each output line is emitted as a "monitor:output" pi event. Use this to watch logs, tail files, poll APIs, run experiments, etc.
+Fire off a build check, CI monitor, experiment, script, or any slow command — then keep working. Output streams back as "monitor:output" events. When the process exits, "monitor:done" fires (or "monitor:error" on failure).
+
+If you pass onDone with a prompt, the monitor auto-creates a one-shot completion loop — you get a system reminder with the exit code and output line count. No need to poll or create a separate loop.
+
+DO NOT use raw Bash while/sleep/for loops to watch something. DO NOT run slow commands inline that could be offloaded. Use MonitorCreate to run work in parallel while you continue.
 
 ## When to Use
 
-Use this tool to:\n- Start a long-running experiment and get notified when it finishes\n- Watch a log file or build output in the background\n- Poll an API and stream results\n- Run any background command whose output you want to track
+Default to MonitorCreate for any long-running or background work:\n- Watch a CI/CD build (hut, gh, curl polling) while you work on something else\n- Run experiments, benchmarks, or training scripts in parallel\n- Tail a log or poll an API endpoint\n- Fire off a slow curl/fetch and check the result later\n- Run any script or command you don't need to wait on inline
 
 ## Events emitted
 
@@ -453,10 +457,11 @@ Use this tool to:\n- Start a long-running experiment and get notified when it fi
 
 ## onDone — auto-notify on completion
 
-Pass onDone with a prompt and the monitor auto-creates a one-shot loop that fires when the process exits. The system reminder includes the exit code and output line count. No need to create a separate LoopCreate or poll MonitorList.\n\nExample: MonitorCreate command="python train.py" onDone="Check training results and report best loss"`,
+Pass onDone with a prompt and the monitor auto-creates a one-shot loop that fires when the process exits. The system reminder includes the exit code and output line count.\n\nExample: MonitorCreate command="python train.py" onDone="Check training results and report best loss"\nExample: MonitorCreate command="hut builds show 1769753" onDone="Analyze the build result and report status"`,
     promptGuidelines: [
-      "Use onDone to auto-notify when a long-running command finishes — no need for a separate LoopCreate.",
-      "When starting experiments or benchmarks, pass onDone so the agent automatically picks up the results.",
+      "Default to MonitorCreate for any long-running or background command — releases the agent to keep working on other tasks in parallel.",
+      "When the user asks to monitor CI builds, watch a build, check a remote job, or run an experiment, use MonitorCreate instead of inline bash/curl/wait.",
+      "Use onDone to auto-notify when a background command finishes — the agent will pick up the results automatically.",
     ],
     parameters: Type.Object({
       command: Type.String({ description: "Shell command to run in background" }),

package/src/trigger-system.ts

@@ -1,5 +1,6 @@
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import type { CronScheduler } from "./scheduler.js";
+import type { LoopStore } from "./store.js";
 import type { LoopEntry } from "./types.js";
 
 export class TriggerSystem {
@@ -10,6 +11,7 @@ export class TriggerSystem {
   constructor(
     private pi: ExtensionAPI,
     private scheduler: CronScheduler,
+    private store: LoopStore,
   ) {}
 
   start(): void {
@@ -99,6 +101,11 @@ export class TriggerSystem {
       trigger: entry.trigger,
       timestamp: Date.now(),
     });
+
+    if (!entry.recurring) {
+      this.remove(entry.id);
+      this.store.update(entry.id, { status: "expired" });
+    }
   }
 
   private matchesFilter(data: any, filter?: string): boolean {