stream disconnected before completion: URL error: TLS support not compiled in

Resolved 💬 6 comments Opened Jan 23, 2026 by gregkonush Closed Jan 25, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.89.0

What subscription do you have?

pro

Which model were you using?

gpt-5.2-codex

What platform is your computer?

macos

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

ghostty

What issue are you seeing?

stream disconnected before completion: URL error: TLS support not compiled in

What steps can reproduce the bug?

issue one prompt

What is the expected behavior?

prompt works

Additional information

_No response_

View original on GitHub ↗

6 Comments

etraut-openai contributor · 5 months ago

Are you using any non-standard configuration settings? In particular, do you have the "responses_websockets" feature enabled? This feature is still under development. Disabling this feature should make the problem go away.

gregkonush · 5 months ago

ah yes, I turned off responses_websockets feature and it works now, thanks

DanSnow · 5 months ago

Unfortunately, I am experiencing the same issue, but the workaround mentioned above doesn't apply to my case.

I have confirmed that responses_websockets is not enabled. I even performed a clean reset by removing the ~/.codex directory and re-logging in, but the "TLS support not compiled in" error persists.

Furthermore, I have tested this using both the npm and Homebrew versions to rule out distribution-specific issues, but the result remains the same.

Environment:

  • Codex Version: 0.89.0
  • OS: macOS
  • Terminal: Ghostty
etraut-openai contributor · 5 months ago

@DanSnow, does the problem go away if you downgrade to an earlier version (0.88 or 0.87)? If so, what is the first version where you started to see this?

DanSnow · 5 months ago

Yes, I tried 0.87, and it works. I got the same error with 0.88 as well.

DanSnow · 5 months ago

Sorry, I just found the issue. It's responses_websockets. I just found it's enabled within the project-level codex config. After turning it off, the 0.89.0 version works again