mirror of
https://github.com/openai/codex.git
synced 2026-11-18 22:20:48 +00:00
## Why If a provider keeps an SSE connection open after reporting a failure, Codex can hit the idle timeout and lose the original error and its retry advice. ## What changed End the SSE stream immediately on `response.failed` or a recognized `error` event. Classify statusless quota, plan usage, invalid prompt, and misalignment errors consistently across both event forms. Preserve `Retry-After` for overload and capacity errors, preferring error-level headers over event-level headers when both provide valid advice. ## Testing Add SSE regression tests that hold the connection open and verify immediate error delivery, terminal error handling, and retry delays. Extend WebSocket coverage for statusless errors received before the close handshake. GitOrigin-RevId: 69afd1d3b18ca3139e9b7ad98ae1481a432179f0
codex-api
Typed clients for Codex/OpenAI APIs built on top of the generic transport in codex-client.
- Hosts the request/response models and request builders for Responses and related Codex APIs.
- Owns provider configuration (base URLs, headers, query params), auth header injection, retry tuning, and stream idle settings.
- Parses SSE streams into
ResponseEvent/ResponseStream, including rate-limit snapshots and API-specific error mapping. - Serves as the wire-level layer consumed by
codex-core; higher layers handle auth refresh and business logic.
Core interface
The public interface of this crate is intentionally small and uniform:
-
Responses endpoint
- Input:
ResponsesApiRequestfor the request body (model,input,tools,parallel_tool_calls, reasoning/text controls).ResponsesOptionsfor transport/header concerns (conversation_id,session_source,extra_headers,compression,turn_state).
- Output: a
ResponseStreamofResponseEvent(both re-exported fromcommon).
- Input:
-
Memory summarize endpoint
- Input:
MemorySummarizeInput(re-exported ascodex_api::MemorySummarizeInput):model: String.raw_memories: Vec<RawMemory>(serialized astracesfor wire compatibility).RawMemoryincludesid,metadata.source_path, and normalizeditems.
reasoning: Option<Reasoning>.
- Output:
Vec<MemorySummarizeOutput>. MemoriesClient::summarize_input(&MemorySummarizeInput, extra_headers)wraps JSON encoding and retry/telemetry wiring.
- Input:
All HTTP details (URLs, headers, retry/backoff policies, SSE framing) are encapsulated in codex-api and codex-client. Callers construct prompts/inputs using protocol types and work with typed streams of ResponseEvent or other endpoint-specific response values.