mirror of
https://github.com/openai/codex.git
synced 2026-11-19 22:30:42 +00:00
## Why HTTP sampling can attach private connector result bodies, but Responses WebSocket sampling leaves them out. WebSocket requests need the same destination and account checks before sending those bodies. ## What changed Apply the existing HTTP eligibility checks to each WebSocket attempt and attach only result bodies that belong to the current account and match the input being sent, including when that input is an incremental update. Keep prewarm requests free of private result bodies. Update `tungstenite` and `tokio-tungstenite` to keep sensitive payload bytes out of frame diagnostics. ## Testing Add regression coverage for connector results reaching the server while staying out of request observers and client logs. Cover custom-provider requests and retries across an account change with results from both Code Mode `exec` and `wait`. GitOrigin-RevId: df5ec8608e59bb3a0444fafd5268279e669ccb55
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.