@yeaft/webchat-agent 1.0.342 → 1.0.344

package/local-runtime/version.json

@@ -1 +1 @@
-{"version":"1.0.342"}
+{"version":"1.0.344"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeaft/webchat-agent",
-  "version": "1.0.342",
+  "version": "1.0.344",
   "description": "Remote worker agent for Yeaft Web Code Agent — connects the native Yeaft engine, CLI providers, and workbench tools",
   "main": "index.js",
   "type": "module",

package/yeaft/debug-trace.js

@@ -23,6 +23,14 @@ const MAX_TEXT_BYTES = 1024 * 1024;
 const MAX_TOOL_INPUT = 10 * 1024;
 const MAX_INLINE_VALUE_BYTES = 1024 * 1024;
 const MAX_RAW_REQUEST_BYTES = 2 * 1024 * 1024;
+// Raw provider responses are diagnostic duplicates of the normalized response,
+// tool calls, usage and request delta already stored on each loop. Keeping up
+// to 1 MiB per loop made long tool turns produce 100+ MiB trace files. Every
+// buffered flush then JSON.stringify()'d and rewrote that entire file on the
+// agent's single event loop, so several active Sessions appeared deadlocked.
+// A 64 KiB prefix is enough to inspect provider envelopes without letting
+// always-on diagnostics dominate runtime latency.
+const MAX_RAW_RESPONSE_BYTES = 64 * 1024;
 const TRACE_FLUSH_INTERVAL_MS = 5_000;
 const TRACE_FLUSH_DIRTY_LOOPS = 10;
 const MAX_SEARCH_PATTERN_CHARS = 300;
@@ -758,8 +766,8 @@ export class DebugTrace {
       stopReason: info.stopReason || null,
       at: Date.now(),
       rawResponse: typeof info.rawResponse === 'string'
-        ? truncateText(info.rawResponse, MAX_TEXT_BYTES)
-        : safeJsonValue(info.rawResponse),
+        ? truncateText(info.rawResponse, MAX_RAW_RESPONSE_BYTES)
+        : safeJsonValue(info.rawResponse, MAX_RAW_RESPONSE_BYTES),
       requestDelta: buildRequestDelta(previousSnapshot, snapshot),
     };
     if (loopIndex >= 0) trace.loops[loopIndex] = loop;