codex - 💡(How to fix) Fix Codex 0.134+ WebSocket reconnection issue after tool calls

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

no recent error logs available. Client logs: No recent error logs available

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

Codex 0.134+

What subscription do you have?

API only

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex 0.134+ WebSocket reconnection issue after tool calls

Environment:

  • Version: 0.134.0+ (Codex desktop 26.527.3686.0)
  • Platform: Microsoft Windows NT 10.0.26200.0 x64
  • Scenario: Custom API proxy + tool_calls

Problem: Codex disconnects after executing tool calls. Server logs show all requests return 200 OK with no errors. Codex client logs show no recent error logs available.

Steps to reproduce:

  1. Configure custom API proxy
  2. Send request with tools
  3. Model returns tool_calls
  4. Codex executes tool, sends tool_result
  5. Codex disconnects, cannot continue conversation

Expected behavior: Codex should continue conversation after tool execution.

Actual behavior: Codex disconnects after tool call.

Server logs: No errors, all requests successful Client logs: No recent error logs available

This may be related to WebSocket reconnection logic in 0.134.0 (#23867, #23775, #23951).

What steps can reproduce the bug?

  1. Configure custom API proxy
  2. Send request with tools
  3. Model returns tool_calls
  4. Codex executes tool
  5. Codex disconnects

Proxy logs: No errors, 200 OK responses Client logs: No recent errors

Issue: WebSocket reconnection after tool call execution

What is the expected behavior?

Codex should continue the conversation after executing a tool call and receiving the response. Instead, it disconnects and requires restart

Additional information

This issue started after updating to 0.134.0+. Previous version 0.133.0 worked fine with the same proxy configuration. The WebSocket reconnection logic changes in 0.134.0 (#23867, #23775, #23951) may have introduced this regression.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex 0.134+ WebSocket reconnection issue after tool calls