lsm / neokai / 25954432999

81%

Build Type

push

github

Committed by web-flow

Commit Message

feat: add 429 retry exhaustion detection and auto-recovery (#1915)

* feat: add 429 retry exhaustion detection and auto-recovery

When providers return 429 (rate limited), the SDK retries with
exponential backoff. When all retries exhaust, the session previously
stalled indefinitely requiring manual user intervention.

This change adds:
- RateLimitWatchdog: detects 429 exhaustion and schedules auto-retry
  after a 10-minute cooldown (configurable), up to 3 cycles
- rate_limit_cooldown processing state variant for UI visibility
- Frontend RateLimitCooldownBanner with countdown, retry-now, and cancel
- RPC handlers: session.cancelRateLimitRetry, session.retryNowAfterRateLimit
- Watchdog auto-cancels when user sends a new message before retry fires

* fix: address review feedback for 429 auto-retry feature

- P0: skip setIdle() after scheduling rate limit cooldown to preserve state
- P1: add rate_limit_cooldown to isAgentSessionAlive status check
- P2: remove lastUserMessage from processingState (kept in watchdog only)
- P2: add finally blocks to RateLimitCooldownBanner buttons for state reset
- P3: remove unused jest import from watchdog test
- Fix duplicate rateLimitCooldownScheduled declaration scoping

* fix: harden 429 detection and propagate cooldown status to space projections

- Case-insensitive rate-limit matching (handles "Rate limit" etc.)
- Exclude 402/quota/billing errors from auto-retry path
- Refuse cooldown scheduling when no user message available to retry
- Gate errorManager.handleError when cooldown scheduled (avoids
  terminal session.error in Space workflows during recoverable 429)
- Add rate_limit_cooldown to space activity SQL CASE projection
- Add rate_limit_cooldown to deferred injection busy-state check

* fix: await cooldown state write, add cooldown to space activity types

- Make scheduleRetry async and await setRateLimitCooldown to prevent
  race with concurrent user messages or retry-now
- Add null message guard to schedule... (continued)

Coverage Stats

8361 of 11649 branches covered (71.77%)

Branch coverage included in aggregate %.

165 of 292 new or added lines in 8 files covered. (56.51%)

6 existing lines in 2 files now uncovered.

68219 of 80222 relevant lines covered (85.04%)

296.49 hits per line