@agent-native/core 0.32.2 → 0.32.18

package/dist/client/agent-chat-adapter.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agent-chat-adapter.d.ts","sourceRoot":"","sources":["../../src/client/agent-chat-adapter.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAsB,MAAM,qBAAqB,CAAC;AAgBhF,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,+BAA+B,CAAC;AAKrE,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AAE7D,MAAM,MAAM,oBAAoB;AAC9B;;;;GAIG;AACD,KAAK;AACP,0EAA0E;GACxE,WAAW,CAAC;AAs2BhB;;;;GAIG;AACH;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,CAAC,EAAE;IAC/C,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE;QAAE,OAAO,EAAE,MAAM,GAAG,SAAS,CAAA;KAAE,CAAC;IAC3C,SAAS,CAAC,EAAE;QAAE,OAAO,EAAE,MAAM,GAAG,SAAS,CAAA;KAAE,CAAC;IAC5C,SAAS,CAAC,EAAE;QAAE,OAAO,EAAE,eAAe,GAAG,SAAS,CAAA;KAAE,CAAC;IACrD,WAAW,CAAC,EAAE;QAAE,OAAO,EAAE,OAAO,GAAG,MAAM,GAAG,SAAS,CAAA;KAAE,CAAC;IACxD,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE;QAAE,OAAO,EAAE,eAAe,GAAG,IAAI,GAAG,SAAS,CAAA;KAAE,CAAC;IAC3D,OAAO,CAAC,EAAE,oBAAoB,CAAC;CAChC,GAAG,gBAAgB,CAqgCnB"}
+{"version":3,"file":"agent-chat-adapter.d.ts","sourceRoot":"","sources":["../../src/client/agent-chat-adapter.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAsB,MAAM,qBAAqB,CAAC;AAgBhF,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,+BAA+B,CAAC;AAKrE,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AAE7D,MAAM,MAAM,oBAAoB;AAC9B;;;;GAIG;AACD,KAAK;AACP,0EAA0E;GACxE,WAAW,CAAC;AA62BhB;;;;GAIG;AACH;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,CAAC,EAAE;IAC/C,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE;QAAE,OAAO,EAAE,MAAM,GAAG,SAAS,CAAA;KAAE,CAAC;IAC3C,SAAS,CAAC,EAAE;QAAE,OAAO,EAAE,MAAM,GAAG,SAAS,CAAA;KAAE,CAAC;IAC5C,SAAS,CAAC,EAAE;QAAE,OAAO,EAAE,eAAe,GAAG,SAAS,CAAA;KAAE,CAAC;IACrD,WAAW,CAAC,EAAE;QAAE,OAAO,EAAE,OAAO,GAAG,MAAM,GAAG,SAAS,CAAA;KAAE,CAAC;IACxD,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE;QAAE,OAAO,EAAE,eAAe,GAAG,IAAI,GAAG,SAAS,CAAA;KAAE,CAAC;IAC3D,OAAO,CAAC,EAAE,oBAAoB,CAAC;CAChC,GAAG,gBAAgB,CAggCnB"}

package/dist/client/agent-chat-adapter.js

@@ -21,7 +21,14 @@ const MAX_STARTUP_RECOVERY_ATTEMPTS = 8;
 const MAX_STALE_RUN_CONTINUATIONS = 3;
 const MAX_STALLED_TRANSIENT_CONTINUATIONS = 8;
 const MAX_TOTAL_TRANSIENT_CONTINUATIONS = 32;
-const MAX_EMPTY_TRANSIENT_CONTINUATIONS = 1;
+// How many consecutive continuations that produce NO progress (no streamed
+// text, no completed/in-flight tool) we tolerate before giving up. A complex
+// first turn can spend the whole soft-timeout window (~40s) "thinking" with no
+// visible output; giving up after a single such window made the agent feel like
+// it "craps out / stops midway" on heavier prompts (Analytics). Retrying a few
+// times lets a transient slow start recover, while the cap still terminates a
+// genuinely stuck turn with a clear message instead of looping forever.
+const MAX_EMPTY_TRANSIENT_CONTINUATIONS = 3;
 const RETRY_BASE_DELAY_MS = 500;
 const RETRY_MAX_DELAY_MS = 8_000;
 const MAX_HISTORY_ATTACHMENT_CHARS = 60_000;
@@ -1042,7 +1049,6 @@ export function createAgentChatAdapter(options) {
                     // Either real output or an actively-running tool counts as progress
                     // for the stalled/empty caps.
                     const madeProgress = madeContentProgress || hasInFlightTool;
-                    const madeVisibleProgress = visibleContent.length > 0;
                     const madeDurableToolProgress = visibleContent.some((part) => part.type === "tool-call" && part.result !== undefined);
                     if (signal.reason === "loop_limit") {
                         stalledTransientContinuationAttempts = 0;
@@ -1050,13 +1056,12 @@ export function createAgentChatAdapter(options) {
                     }
                     else {
                         totalTransientContinuationAttempts += 1;
-                        const madeActivityProgress = signal.activityTrail.length > 0 ||
-                            Boolean(lastActivityTool(signal.activityTrail));
-                        if (!madeVisibleProgress &&
-                            signal.reason === "run_timeout" &&
-                            !madeActivityProgress) {
-                            return { ok: false, resetVisibleContent: false };
-                        }
+                        // A run_timeout that produced nothing visible and no activity (the
+                        // model spent the whole soft-timeout window thinking before its
+                        // first output) is NOT an immediate give-up: a transient slow start
+                        // routinely recovers on the next continuation. Let it fall through
+                        // to the empty-continuation budget below so it retries a bounded
+                        // number of times before surfacing the "no visible progress" error.
                         // Reset the empty-continuation counter on real progress — streamed
                         // text/completed tool OR an in-flight tool the server is running —
                         // not merely on a non-zero part count, which whitespace-only or