Files
codex/codex-rs/codex-api
Charlie Marsh 1c297f8997 Flush idle Responses WebSocket pongs under backpressure (#62742)
## Why

An idle Responses WebSocket still needs to answer server pings when the
write buffer is full. The pong must finish flushing once the peer drains
the socket, even if no further messages or requests arrive.

## What changed

Have the WebSocket pump flush automatically queued pongs and retry pending
flushes as the socket becomes writable. Bound incoming polling and the
number of pongs tracked while a flush is pending.

## Testing

Add an in-memory WebSocket test that forces a partial pong write and
checks that the peer receives the full heartbeat reply without further
traffic.

GitOrigin-RevId: 12865842c80a8a25a5e107be690f9c3962ce9775
2026-11-20 12:06:32 +00:00
..

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:
      • ResponsesApiRequest for the request body (model, input, tools, parallel_tool_calls, reasoning/text controls).
      • ResponsesOptions for transport/header concerns (conversation_id, session_source, extra_headers, compression, turn_state).
    • Output: a ResponseStream of ResponseEvent (both re-exported from common).
  • Memory summarize endpoint

    • Input: MemorySummarizeInput (re-exported as codex_api::MemorySummarizeInput):
      • model: String.
      • raw_memories: Vec<RawMemory> (serialized as traces for wire compatibility).
        • RawMemory includes id, metadata.source_path, and normalized items.
      • reasoning: Option<Reasoning>.
    • Output: Vec<MemorySummarizeOutput>.
    • MemoriesClient::summarize_input(&MemorySummarizeInput, extra_headers) wraps JSON encoding and retry/telemetry wiring.

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.