Skip to content

[codex] Use custom provider without websockets#4

Merged
Che-Zhu merged 1 commit intomainfrom
codex/custom-provider-no-websocket
Apr 8, 2026
Merged

[codex] Use custom provider without websockets#4
Che-Zhu merged 1 commit intomainfrom
codex/custom-provider-no-websocket

Conversation

@Che-Zhu
Copy link
Copy Markdown
Collaborator

@Che-Zhu Che-Zhu commented Apr 8, 2026

Summary

  • configure Codex to use a custom provider when CODEX_OPENAI_BASE_URL is set instead of overriding the built-in openai provider
  • disable websocket transport for that provider with supports_websockets = false
  • keep the container runtime fixes for ca-certificates and bubblewrap, and update both READMEs to match the new provider-based behavior

Verification

  • node --check src/codex-runtime.mjs
  • node --check src/codex-app-server.mjs
  • node --check src/bootstrap.mjs
  • docker buildx build --platform linux/amd64 --load -t codex-gateway:provider-test .
  • ran the image locally with the third-party upstream and verified /healthz, POST /api/sessions, and POST /api/sessions/:id/turn
  • confirmed a real turn completed successfully and container logs no longer contained responses_websocket, wss://, or 503

@Che-Zhu Che-Zhu merged commit ec728a4 into main Apr 8, 2026
1 check passed
@Che-Zhu Che-Zhu deleted the codex/custom-provider-no-websocket branch April 9, 2026 13:07
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