"Stream disconnected before completion" (using socks5h proxy after v0.87.0 > v0.88.0 upgrade)

Resolved 💬 11 comments Opened Jan 22, 2026 by dolzenko Closed Jan 24, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

v0.88.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.2-codex

What platform is your computer?

Linux 6.18.5-arch1-1 x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Ghostty

What issue are you seeing?

Reconnecting... 3/5 (10s • esc to interrupt)
└ Stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)

What steps can reproduce the bug?

Uploaded thread: 019be591-aad2-71e2-a346-9e56d2fc8e58

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

11 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #9670
  • #9675
  • #8302
  • #8294

Powered by Codex Action

Pippo809 · 5 months ago

Observing the same behavior

qwertyforce · 5 months ago

+1

Enthoes1 · 5 months ago

try backward the update. i encountered this bug today, while it happened in ide extension. this error is solved after backwarding to version 2 weeks ago

dolzenko · 5 months ago

Ok it seems to expect HTTP CONNECT proxy now, given your SOCKS server is on 127.0.0.1:1080

gost -L=http://127.0.0.1:18080 -F=socks5://127.0.0.1:1080
env HTTPS_PROXY="http://127.0.0.1:18080" HTTP_PROXY="http://127.0.0.1:18080" codex

fixes it in 0.88

etraut-openai contributor · 5 months ago

We've just fixed a regression that could explain the issue you're seeing. We'd appreciate it if you could try the latest prerelease version of the CLI (0.89.0-alpha.4 or newer) and see if that fixes the problem.

Sandy3100 · 5 months ago

I see this problem on codex@0.88.0, and it disappears after rolling back to codex@0.86.0.

etraut-openai contributor · 5 months ago

@Sandy3100, does 0.89.0 fix your issue?

etraut-openai contributor · 5 months ago

Please update to 0.89.0 or newer. This issue should be gone. Let us know if you're still seeing it with 0.89.0.

Sandy3100 · 5 months ago
@Sandy3100, does 0.89.0 fix your issue?

@etraut-openai yes,codex@0.89.0 also works perfectly.

dolzenko · 5 months ago

Works, thank you!