@bridge4dev/runner 0.44.1 → 0.44.2

package/dist/adapters/codex.d.ts

@@ -67,6 +67,20 @@ export declare function parseElicitation(params: Record<string, unknown>): Agent
  * never enumerated on our side.
  */
 export declare function readEfforts(value: unknown): EffortOption[];
+/**
+ * When a Codex window resets → ISO, or null if it did not say.
+ *
+ * Epoch SECONDS on the wire, captured live from codex-cli 0.147.0 on 2026-08-16:
+ * `resetsAt: 1787221437` is 2026-08-20. Read as a string it was silently dropped,
+ * which is why no Codex window has ever shown a reset time and why #258 had
+ * nothing to schedule a wake-up from on this agent.
+ *
+ * The range check is not decoration. A clock built from a misread number is
+ * worse than no clock at all: milliseconds mistaken for seconds would promise a
+ * reset in the year 58600, and #258 would arm a timer on it. Outside the range,
+ * we say we do not know — which is the honest answer and the safe one.
+ */
+export declare function codexResetsAt(raw: unknown): string | null;
 export declare class CodexAdapter implements AgentAdapter {
     private readonly deps;
     readonly id: "codex";

package/dist/adapters/codex.js

@@ -1399,16 +1399,28 @@ class CodexSession {
             const usedPercent = num(window['usedPercent'] ?? window['used_percent']);
             if (usedPercent === undefined)
                 continue;
-            const minutes = num(window['windowMinutes'] ?? window['window_minutes']) ?? null;
-            // Live 2026-08-15: Codex sent a percentage with NO length, so the label
-            // fell back to «Limit window» — true but useless. The slot itself carries
-            // the answer on every ChatGPT plan: `primary` is the short window,
-            // `secondary` the weekly one. Used only when the minutes are missing, so
-            // a provider that does state them still wins.
+            // `windowDurationMins` is the name codex-cli 0.147.0 actually sends —
+            // captured from a live `account/rateLimits/updated` on 2026-08-16:
+            //
+            //   primary:   {usedPercent: 4, windowDurationMins: 10080, resetsAt: 1787221437}
+            //   secondary: null
+            //
+            // The two older spellings are kept behind it, not in front: a Codex that
+            // still sends them keeps working, and the current one stops being read as
+            // «length unknown». That misreading is what made the panel label a WEEKLY
+            // window «5 hours» — the number was right and the heading was not.
+            const minutes = num(window['windowDurationMins'] ?? window['windowMinutes'] ?? window['window_minutes']) ??
+                null;
             // Only when the length is ABSENT. A stated length we do not recognise is
             // information — 43 200 minutes is a monthly window, and calling it «5
             // hours» because it arrived first would be worse than admitting we have
             // no name for it.
+            //
+            // The slot fallback stays for exactly that case, but it is now the last
+            // resort rather than the usual path. And note what the live payload shows:
+            // `primary` is NOT reliably the short window. Here it is the weekly one
+            // and `secondary` is null, so guessing by slot was wrong in the only case
+            // we have ever observed.
             const key = minutes === null
                 ? slot === 'primary'
                     ? 'five_hour'
@@ -1418,7 +1430,12 @@ class CodexSession {
                 key,
                 windowMinutes: minutes,
                 usedPercent: clampPercent(usedPercent),
-                resetsAt: str(window['resetsAt'] ?? window['resets_at']) ?? null,
+                // Epoch SECONDS on the wire, not an ISO string — reading it with `str()`
+                // returned undefined for every snapshot ever received, which is why no
+                // Codex window has ever shown a reset time. The string form is still
+                // accepted in case a future version switches. Same fact, two encodings,
+                // one place that knows it — exactly as the Claude adapter already does.
+                resetsAt: codexResetsAt(window['resetsAt'] ?? window['resets_at']),
             });
         }
         this.rateLimitWindows = windows.sort((a, b) => (a.windowMinutes ?? Number.MAX_SAFE_INTEGER) - (b.windowMinutes ?? Number.MAX_SAFE_INTEGER));
@@ -1474,8 +1491,15 @@ class CodexSession {
         }
     }
     rateLimitRefusal(error) {
+        // The machine-readable cause FIRST. Codex 0.147.0 says `usageLimitExceeded`
+        // — Exceeded, not Reached — so not one of the four substrings below ever
+        // matched it, and the auto-pause never armed on this agent at all: a refused
+        // turn went to FAILED instead of sleeping until the window reopened.
+        // Demonstrated by test, 2026-08-16, not inferred.
+        const code = str(asRecord(error)['codexErrorInfo']);
         const haystack = JSON.stringify(error).toLowerCase();
-        const refused = haystack.includes('ratelimitreached') ||
+        const refused = code === 'usageLimitExceeded' ||
+            haystack.includes('ratelimitreached') ||
             haystack.includes('rate_limit_reached') ||
             haystack.includes('usage_limit_reached') ||
             haystack.includes('usagelimitreached');
@@ -1913,6 +1937,31 @@ function truncateRecord(value) {
     }
     return out;
 }
+/**
+ * When a Codex window resets → ISO, or null if it did not say.
+ *
+ * Epoch SECONDS on the wire, captured live from codex-cli 0.147.0 on 2026-08-16:
+ * `resetsAt: 1787221437` is 2026-08-20. Read as a string it was silently dropped,
+ * which is why no Codex window has ever shown a reset time and why #258 had
+ * nothing to schedule a wake-up from on this agent.
+ *
+ * The range check is not decoration. A clock built from a misread number is
+ * worse than no clock at all: milliseconds mistaken for seconds would promise a
+ * reset in the year 58600, and #258 would arm a timer on it. Outside the range,
+ * we say we do not know — which is the honest answer and the safe one.
+ */
+export function codexResetsAt(raw) {
+    if (typeof raw === 'string' && raw) {
+        const parsed = Date.parse(raw);
+        return Number.isNaN(parsed) ? null : new Date(parsed).toISOString();
+    }
+    if (typeof raw !== 'number' || !Number.isFinite(raw))
+        return null;
+    // 2001-09-09 … 2286-11-20 in epoch seconds.
+    if (raw < 1_000_000_000 || raw > 9_999_999_999)
+        return null;
+    return new Date(raw * 1000).toISOString();
+}
 function stringifyMcpResult(item) {
     const errorMessage = str(asRecord(item['error'])['message']);
     if (errorMessage)

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const RUNNER_VERSION = "0.44.1";
+export declare const RUNNER_VERSION = "0.44.2";
 //# sourceMappingURL=version.d.ts.map

package/dist/version.js

@@ -1,3 +1,3 @@
 // Kept in sync with package.json by the release script (manual for now).
-export const RUNNER_VERSION = '0.44.1';
+export const RUNNER_VERSION = '0.44.2';
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bridge4dev/runner",
-  "version": "0.44.1",
+  "version": "0.44.2",
   "description": "DevBridge dev runner — connects a dev server to DevBridge and runs agent sessions (Claude Code / Codex)",
   "homepage": "https://bridge4.dev",
   "license": "MIT",