From 68bc8f0eae1776ea9eb1ff0ad0d704bef75b13f9 Mon Sep 17 00:00:00 2001 From: Yaacov Date: Mon, 16 Nov 2026 18:44:40 +0200 Subject: [PATCH 1/4] fix(rpc): report a usage limit as a 429 with its stated reset A long-wait 429 ("Provider requested 119172000ms wait, exceeds retry.maxDelayMs (300000ms)") ends the turn at once. Its prompt_result carried httpStatus only when the transport attached the response's status to the failed message, and Scient Desktop shows its quota-blocked state, with the reset time, only for a 429 (or cost_cap). A usage limit the classifier recognized but that came without a status therefore read as a generic failure. Such a failure now reports httpStatus 429; a status the provider sent is never replaced. The stated reset of "429 Subscription quota exhausted. Your usage window resets at 2026-11-16T12:15:34Z." was not read either: the retry hint parser knows "reset at