@trevonistrevon/pi-loop 0.4.4 → 0.4.6

package/README.md

@@ -107,6 +107,8 @@ Only task counts and the single active/next task are shown in the widget so atte
 | `PI_LOOP_SCOPE` | `memory` (ephemeral), `session` (per-session file), `project` (shared) | `session` |
 | `PI_LOOP_DEBUG` | Debug logging to stderr | unset |
 
+In `session` scope (default), loop and task files are saved per session ID (e.g. `.pi/tasks/tasks-<sessionId>.json`) so concurrent sessions and worktree agents do not share state. In `memory` scope nothing persists to disk.
+
 ## Limits
 
 25 active loops, 25 running monitors. Recurring loops expire after 7 days.

package/dist/index.js

@@ -53,9 +53,14 @@ export default function (pi) {
             return undefined;
         return join(process.cwd(), ".pi", "loops", "loops.json");
     }
-    function resolveTaskStorePath() {
+    function resolveTaskStorePath(sessionId) {
         if (loopScope === "memory")
             return undefined;
+        if (loopScope === "session" && sessionId) {
+            return join(process.cwd(), ".pi", "tasks", `tasks-${sessionId}.json`);
+        }
+        if (loopScope === "session")
+            return undefined;
         return join(process.cwd(), ".pi", "tasks", "tasks.json");
     }
     let store = new LoopStore(resolveStorePath());
@@ -319,6 +324,7 @@ export default function (pi) {
     let storeUpgraded = false;
     let persistedShown = false;
     let _latestCtx;
+    let _sessionId;
     function upgradeStoreIfNeeded(ctx) {
         if (storeUpgraded)
             return;
@@ -347,6 +353,7 @@ export default function (pi) {
     }
     pi.on("turn_start", async (_event, ctx) => {
         _latestCtx = ctx;
+        _sessionId = ctx.sessionManager.getSessionId();
         widget.setUICtx(ctx.ui);
         upgradeStoreIfNeeded(ctx);
         widget.update();
@@ -381,6 +388,7 @@ export default function (pi) {
         triggerSystem.stop();
         agentRunning = false;
         pendingNotifications.clear();
+        _sessionId = undefined;
         const isResume = event?.reason === "resume";
         storeUpgraded = false;
         persistedShown = false;
@@ -995,7 +1003,7 @@ Use MonitorList to find the monitor ID, then stop it with this tool.`,
     setTimeout(async () => {
         if (tasksAvailable || nativeTasksRegistered)
             return;
-        nativeTaskStore = new TaskStore(resolveTaskStorePath());
+        nativeTaskStore = new TaskStore(resolveTaskStorePath(_sessionId));
         nativeTasksRegistered = true;
         const taskStore = nativeTaskStore;
         pi.registerCommand("tasks", {
@@ -1032,6 +1040,7 @@ Fields:
 - metadata: optional tags/metadata`,
             promptGuidelines: [
                 "Use TaskCreate to track complex multi-step work across turns.",
+                "Break work into small, independently completable tasks. A task should be finishable in one focused session — if a task would take multiple turns, split it further.",
                 "TaskCreate accepts `subject` and `description` parameters only — do not invent extra fields unless the schema explicitly adds them.",
             ],
             parameters: Type.Object({
@@ -1047,7 +1056,11 @@ Fields:
                     status: entry.status,
                 });
                 widget.update();
-                return Promise.resolve(textResult(`Task #${entry.id} created: ${entry.subject}`));
+                const pending = taskStore.pendingCount();
+                const hint = pending >= 5
+                    ? `\n(${pending} pending tasks — consider creating a worker loop: LoopCreate trigger='tasks:created' recurring: true maxFires: 30 prompt='Run TaskList, pick next pending task, mark it in_progress, implement it, run validation, complete it. If no pending tasks remain, call LoopDelete on your own loop ID.')`
+                    : "";
+                return Promise.resolve(textResult(`Task #${entry.id} created: ${entry.subject}${hint}`));
             },
         });
         pi.registerTool({
@@ -1079,11 +1092,12 @@ Fields:
             label: "TaskUpdate",
             description: `Update task status or details. Set status to "in_progress" before starting work, "completed" when done.
 
-Statuses: pending → in_progress → completed`,
+Statuses: pending → in_progress → completed
+Parameters: id (required), status, subject, description`,
             promptGuidelines: [
-                "Use TaskUpdate with parameter `id`, not `taskId`.",
-                "TaskUpdate accepts only `id`, `status`, `subject`, and `description`.",
-                "When a tool validation error clearly indicates a recoverable schema mismatch, correct the arguments and retry without narrating the recovery unless the user needs to know.",
+                "TaskUpdate uses parameter `id`, not `taskId`.",
+                "Accepted parameters: `id` (required), `status`, `subject`, `description`.",
+                "When validation fails with 'must have required properties id', you passed `taskId` instead of `id`. Correct silently and retry.",
             ],
             parameters: Type.Object({
                 id: Type.String({ description: "Task ID to update" }),

package/package.json

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

package/src/index.ts

@@ -73,8 +73,12 @@ export default function (pi: ExtensionAPI) {
     return join(process.cwd(), ".pi", "loops", "loops.json");
   }
 
-  function resolveTaskStorePath(): string | undefined {
+  function resolveTaskStorePath(sessionId?: string): string | undefined {
     if (loopScope === "memory") return undefined;
+    if (loopScope === "session" && sessionId) {
+      return join(process.cwd(), ".pi", "tasks", `tasks-${sessionId}.json`);
+    }
+    if (loopScope === "session") return undefined;
     return join(process.cwd(), ".pi", "tasks", "tasks.json");
   }
 
@@ -349,6 +353,7 @@ export default function (pi: ExtensionAPI) {
   let storeUpgraded = false;
   let persistedShown = false;
   let _latestCtx: ExtensionContext | undefined;
+  let _sessionId: string | undefined;
 
   function upgradeStoreIfNeeded(ctx: ExtensionContext) {
     if (storeUpgraded) return;
@@ -378,6 +383,7 @@ export default function (pi: ExtensionAPI) {
 
   pi.on("turn_start", async (_event, ctx) => {
     _latestCtx = ctx;
+    _sessionId = ctx.sessionManager.getSessionId();
     widget.setUICtx(ctx.ui);
     upgradeStoreIfNeeded(ctx);
     widget.update();
@@ -417,6 +423,7 @@ export default function (pi: ExtensionAPI) {
     triggerSystem.stop();
     agentRunning = false;
     pendingNotifications.clear();
+    _sessionId = undefined;
 
     const isResume = event?.reason === "resume";
     storeUpgraded = false;
@@ -1076,7 +1083,7 @@ Use MonitorList to find the monitor ID, then stop it with this tool.`,
 
   setTimeout(async () => {
     if (tasksAvailable || nativeTasksRegistered) return;
-    nativeTaskStore = new TaskStore(resolveTaskStorePath());
+    nativeTaskStore = new TaskStore(resolveTaskStorePath(_sessionId));
     nativeTasksRegistered = true;
     const taskStore = nativeTaskStore;
 
@@ -1115,6 +1122,7 @@ Fields:
 - metadata: optional tags/metadata`,
       promptGuidelines: [
         "Use TaskCreate to track complex multi-step work across turns.",
+        "Break work into small, independently completable tasks. A task should be finishable in one focused session — if a task would take multiple turns, split it further.",
         "TaskCreate accepts `subject` and `description` parameters only — do not invent extra fields unless the schema explicitly adds them.",
       ],
       parameters: Type.Object({
@@ -1130,7 +1138,12 @@ Fields:
           status: entry.status,
         });
         widget.update();
-        return Promise.resolve(textResult(`Task #${entry.id} created: ${entry.subject}`));
+
+        const pending = taskStore.pendingCount();
+        const hint = pending >= 5
+          ? `\n(${pending} pending tasks — consider creating a worker loop: LoopCreate trigger='tasks:created' recurring: true maxFires: 30 prompt='Run TaskList, pick next pending task, mark it in_progress, implement it, run validation, complete it. If no pending tasks remain, call LoopDelete on your own loop ID.')`
+          : "";
+        return Promise.resolve(textResult(`Task #${entry.id} created: ${entry.subject}${hint}`));
       },
     });
 
@@ -1164,11 +1177,12 @@ Fields:
       label: "TaskUpdate",
       description: `Update task status or details. Set status to "in_progress" before starting work, "completed" when done.
 
-Statuses: pending → in_progress → completed`,
+Statuses: pending → in_progress → completed
+Parameters: id (required), status, subject, description`,
       promptGuidelines: [
-        "Use TaskUpdate with parameter `id`, not `taskId`.",
-        "TaskUpdate accepts only `id`, `status`, `subject`, and `description`.",
-        "When a tool validation error clearly indicates a recoverable schema mismatch, correct the arguments and retry without narrating the recovery unless the user needs to know.",
+        "TaskUpdate uses parameter `id`, not `taskId`.",
+        "Accepted parameters: `id` (required), `status`, `subject`, `description`.",
+        "When validation fails with 'must have required properties id', you passed `taskId` instead of `id`. Correct silently and retry.",
       ],
       parameters: Type.Object({
         id: Type.String({ description: "Task ID to update" }),