Files
codex/codex-rs/codex-api
ssetty-oai f1b6986416 Support optional Apps tool results in Responses requests (#62388)
## What changed

Allow callers to attach eligible Apps tool results as `tool_result` on
selected executed tool calls in Responses HTTP and WebSocket requests.
Keep text content and optional object-valued `structuredContent`, with
a 1 MiB per-result limit and a 15 MiB budget for the enriched message.

Attach results after request observers receive the original JSON. Keep
result IDs local and suppress WebSocket payload tracing for enriched
frames. Preserve the enriched HTTP body on retries to the original
endpoint and retry with the original JSON on HTTP 307 and 308 redirects.
Codex's default request construction supplies no result bodies.

## Testing

Add coverage for result eligibility and size limits, HTTP retry and
redirect behavior, and TLS fallback without forwarding the enriched
body to a redirect destination.

GitOrigin-RevId: c3f2f86f31349e40fcb699d48637c3cbbbe38837
2026-11-19 01:14:54 +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.