Preserve HTTP status on UnknownError so plugins can fallback #47039

Activity

1. github-actions

   assigned

   nexxeln

   on Sep 3, 2026
2. github-actions commented on Sep 3, 2026

   

   github-actionsBot

   on Sep 3, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Sessions fail on transient network errors instead of retrying #30611: Sessions fail on transient network errors instead of retrying — overlaps on the theme of error classification and what counts as retryable vs. hard failure at the transport/provider layer
   • [FEATURE]:Auto-Failover for Rate Limit Resilience #42513: Auto-Failover for Rate Limit Resilience — related in that both require the session error to carry enough information (status, error type) for fallback/retry logic to make decisions
3. RaviTharuma commented on Sep 3, 2026

   

   RaviTharuma

   on Sep 3, 2026

   Author

   More actions

   Both cited issues are still open, and neither covers this one.

   • Sessions fail on transient network errors instead of retrying #30611 is about whether transient network errors get retried at all — retry policy inside OpenCode.
   • [FEATURE]:Auto-Failover for Rate Limit Resilience #42513 asks for built-in auto-failover on rate limits — a feature request for OpenCode-side failover.

   This issue is narrower and is a prerequisite for both: the session error object loses the HTTP status when a provider failure is wrapped as UnknownError. Whatever retries — OpenCode's own logic in #30611, the failover in #42513, or an external plugin — cannot classify 401 vs 429 vs 503 if the status was already discarded at the wrap site. Fixing the wrap does not implement either of those features, and implementing either of them without the status still leaves the classifier blind.

   PR #47092 preserves the status on the Error wrap and does not change retry policy, which keeps it independent of the decisions still open on #30611 and #42513.
4. neriousy commented on Oct 19, 2026

   

   neriousy

   on Oct 19, 2026

   Member

   More actions

   This is fixed in v2: session errors preserve the provider’s HTTP status when available and expose typed classifications such as provider.auth, provider.rate-limit, and provider.internal, along with the response body. Plugins can classify these failures without relying on a generic UnknownError message; this does not add automatic failover.

   To get v2, run npm i -g @opencode/cli@latest. If you still see this on v2, please open a new issue with the details.
5. neriousy

   closed this as completedon Oct 19, 2026