maxpool 1.5.33 → 1.5.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "maxpool",
-  "version": "1.5.33",
+  "version": "1.5.35",
   "description": "Multi-account Claude Code proxy with adaptive, rate-aware load balancing across Claude accounts",
   "type": "module",
   "main": "src/index.js",

package/src/tui.js

@@ -318,7 +318,14 @@ export class TUI {
     this.active.delete(id);
     const dur = r ? ((Date.now() - r.started) / 1000).toFixed(1) : '?';
     const acct = info.account || r?.account || '?';
-    this._addLog(`${info.method} ${info.path} → ${acct} (${info.status}, ${dur}s)`);
+    // Tag PROVIDER-routed requests with the maxpool session id so provider traffic
+    // (when-exhausted overflow, or an incompatible-session pin) is traceable back to
+    // the session that caused it: grep the event log for `→ glm-fallback … [sess X]`,
+    // then `ps eww -p <pid> | grep x-maxpool-session` to find the terminal. Truthiness
+    // guard — a header-less request has sessionKey '' (server.js headerValue) → no tag.
+    const isProvider = this.am.accounts.find(a => a.name === acct)?.type === 'provider';
+    const tag = (isProvider && r?.sessionKey) ? `  [sess ${String(r.sessionKey).slice(0, 8)}]` : '';
+    this._addLog(`${info.method} ${info.path} → ${acct} (${info.status}, ${dur}s)${tag}`);
   }
 
   _addLog(msg) {
@@ -946,6 +953,15 @@ export class TUI {
       const p = this.am._crossProviderFallbackPolicy?.() || 'when-exhausted';
       const pc = p === 'never' ? yellow(p) : p === 'always' ? green(p) : cyan(p);
       xpText = `  ${dim('·')}  ${dim('Cross-provider:')} ${pc}`;
+      // Overflow visibility: when GLM/Kimi actually served requests recently, surface the
+      // volume so provider traffic isn't a mystery — it's overflow that spilled here while
+      // OAuth was saturated. Reuses the SAME 15m load window as the per-row "15m Nr" column.
+      const now = Date.now();
+      let provReq = 0;
+      for (const a of this.am.accounts) {
+        if (a.type === 'provider') provReq += this.am._loadSummary?.(a, 15 * 60_000, now)?.requests || 0;
+      }
+      if (provReq > 0) xpText += `  ${dim('·')}  ${yellow(`providers: ${provReq} req/15m`)}`;
     }
     lines.push(` Routing  ${cyan(routing)}${xpText}`);
     const queuedCount = this.am.queueState?.waiting?.length || 0;
@@ -1040,13 +1056,16 @@ export class TUI {
 
   _renderAcct(idx, bw, showBoth) {
     const a = this.am.accounts[idx];
-    // Highlight the currently-active account. In manual mode that's the
-    // preferred account; in automatic mode it's the one most recently routed
-    // to (currentIndex). Previously only manual mode highlighted anything, so
-    // in automatic load-balancing no row was ever marked current.
+    // Highlight the ACTIVE account(s) — drives BOTH the ► marker and the green
+    // "active" status color. In manual mode that's the single pinned account (all
+    // traffic goes there). In automatic load-balancing there is no single "current"
+    // account, so mark every account SERVING a request right now (inFlight > 0) —
+    // an honest live view of what's working. When idle, nothing is marked; a
+    // throttled/idle provider is never falsely flagged (the old "most recently
+    // routed to" currentIndex could land the marker on an idle fallback).
     const isCur = this.am.routingMode === 'preferred'
       ? a.name === this.am.preferredAccountName
-      : idx === this.am.currentIndex;
+      : a.inFlight > 0;
     const isSel = this.mode === 'select' && idx === this.selIdx;
 
     // Prefix: selection marker + current marker