@monotykamary/pi-retry 0.3.3 → 0.3.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@monotykamary/pi-retry",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Extension suite for pi coding agent that handles 400/413 errors and connection errors with automatic retry",
   "type": "module",
   "author": "Tom X Nguyen",

package/retry.ts

@@ -366,15 +366,27 @@ export default function (pi: ExtensionAPI) {
       // Remove the error assistant message from the transcript so the LLM
       // can retry from the same context.  (The session's _prepareRetry does
       // the same thing for built-in retries.)
+      //
+      // IMPORTANT: We must strip BEFORE calling prompt([]) — if prompt
+      // starts successfully, the LLM sees the context without the error
+      // and generates a fresh response.  If prompt fails (swallowed by
+      // .catch()), we restore the message so the agent state stays
+      // consistent.
       const messages = _agent.state.messages;
-      if (messages.length > 0 && messages[messages.length - 1].role === "assistant") {
+      const hadErrorAssistant = messages.length > 0 && messages[messages.length - 1].role === "assistant";
+      if (hadErrorAssistant) {
         _agent.state.messages = messages.slice(0, -1);
       }
 
       // Guard 4: .catch() swallows the "already processing" error as a
       // last resort.  agent.prompt() is async, so errors become rejected
       // Promises — a try/catch around an un-awaited call catches nothing.
-      _agent.prompt([]).catch(() => {});
+      // If prompt failed, restore the stripped error message.
+      _agent.prompt([]).catch(() => {
+        if (hadErrorAssistant) {
+          _agent.state.messages = messages;
+        }
+      });
     } finally {
       _continueInProgress = false;
     }