Support max reasoning and compatible provider quota errors - #7258
Merged
IMax153 merged 1 commit intoAug 15, 2026
Conversation
🦋 Changeset detectedLatest commit: 88ca9f9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|
IMax153
approved these changes
Aug 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maxas a Responses API reasoning effort{ error, code }error payload used by OpenAI-compatible providers such as xAIbilling_insufficient_balanceresponses as non-retryable quota exhaustionContext
@effect/ai-openaiis also used with OpenAI-compatible endpoints. xAI can return billing errors as HTTP 402 with a flat{ error: string, code?: string }body, or use thebilling_insufficient_balancecode. Without decoding that shape, the useful provider message and code are lost and the error is classified incorrectly.I searched existing and merged PRs in the Effect repositories before opening this and did not find a proposal covering these cases.
Verification
pnpm lint-fixpnpm test packages/ai/openai/test/OpenAiClient.test.ts packages/ai/openai/test/OpenAiSchema.test.tspnpm check