Skip to content

feat(codex): forward native Responses with Codex upstream constraints - #234

Merged
caigee-cmd merged 4 commits into
mainfrom
feat/codex-provider
Sep 25, 2026
Merged

caigee-cmd merged 4 commits into
mainfrom
feat/codex-provider

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

  • Keep /v1/responses on the original request and route it only to adapters that implement native Responses, instead of rebuilding it through ChatRequest.
  • Apply the ChatGPT Codex request constraints used by CLIProxyAPI (forced stream/store/include, rejected sampling fields, item id normalization, tool schema cleanup, routing and responses-lite headers) to both the native path and Chat/Messages requests translated into Codex Responses.
  • Collect a complete non-stream Responses object from the upstream SSE terminal event, restore namespace tool names, and treat response.failed as a terminal error without appending a second error frame.

Test plan

  • go test ./internal/providers/codex ./internal/translate ./internal/executor ./internal/gateway
  • Live ChatGPT Codex account acceptance for /v1/responses, /v1/chat/completions, and /v1/messages

…aints

Keep /v1/responses on the original request, and apply the same ChatGPT Codex rewrites CLIProxyAPI uses to both native and translated Chat/Messages requests.
Describe the three public entries as they work now, including the shared Codex upstream constraints, and move unfinished protocol work out of the current path.
@caigee-cmd
caigee-cmd merged commit 68c12b7 into main Sep 25, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant