@pify/autopilot 0.1.0 → 0.1.1

package/README.md

@@ -33,6 +33,8 @@ It drives each turn on `agent_settled` (fully idle) via a triggered message, so
 
 Give a goal (recommended) and it works toward that, one concrete step per turn; without one it just continues the current task. It stops on any of: the done signal, the turn cap, no progress, an error, or `/autopilot off`.
 
+**With [`@pify/goal`](https://github.com/pifydev/goal):** both self-drive the idle agent, so arm only one at a time — running both just means the turn gets nudged twice. Pick autopilot for "keep going until done" or goal for its evidence-gated, budgeted completion.
+
 ## Settings
 
 `.pi/autopilot.json` (project) or `<agentDir>/autopilot.json` (global):

package/extensions/autopilot.ts

@@ -91,9 +91,14 @@ export default function autopilot(pi: ExtensionAPI) {
     turns++;
     renderStatus(ctx);
     try {
+      // deliverAs "followUp" (not "nextTurn"): while idle, pi runs a message
+      // delivered as followUp/steer immediately (triggerTurn → _runAgentPrompt),
+      // whereas a "nextTurn" message is only QUEUED into whatever turn starts
+      // next and never drives one itself — which meant autopilot armed but never
+      // actually advanced. followUp is what @pify/goal uses to self-drive too.
       await pi.sendMessage(
         { customType: NUDGE_TYPE, content: nudgeText(), display: false },
-        { triggerTurn: true, deliverAs: "nextTurn" },
+        { triggerTurn: true, deliverAs: "followUp" },
       );
     } catch {
       // A /reload or a busy session makes the captured handle throw; stop

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pify/autopilot",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Let the main agent keep going on its own between turns — opt-in, hard-capped by turn count and a no-progress breaker, and it never runs while you are being asked something",
   "keywords": [
     "pi-package",