Report API spend limit errors by scope (#62329)

## Why

Generic quota errors hide whether the project or organization spend limit
blocked a request. Reporting the scope tells users which limit to check.

## What changed

Recognize API key, project, and organization spend limit errors across
HTTP, SSE, and WebSocket responses. Show a message that names the scope and
treat the error as non-retryable, even when the provider sends
`Retry-After`. Apply the existing usage-limit handling to goals and
compaction.

Expose distinct `CodexErrorInfo` values in the app-server protocol and
generated bindings so clients can identify the limit in live errors and
failed turn history.

## Testing

Extend the transport tests to cover all three scopes and verify that they
stop retries. Extend the app-server test to check that the error survives
`thread/read` and that a subsequent turn can succeed in the same thread.

GitOrigin-RevId: 03341f7a78daa7540e7baa519f1a29ec07e34509
This commit is contained in:
Alex Chang
2026-11-18 18:11:54 +00:00
committed by copyberry
parent 0ba514837d
commit cc7a62e19c
47 changed files with 291 additions and 60 deletions
+1
View File
@@ -2514,6 +2514,7 @@ fn websocket_error_detail(err: &ApiError) -> String {
ApiError::ContentFilter
| ApiError::WebsocketMessageTooLarge
| ApiError::ContextWindowExceeded
| ApiError::SpendLimitExceeded(_)
| ApiError::QuotaExceeded
| ApiError::UsageNotIncluded
| ApiError::SessionBudgetExceeded