Issue with the breakdown of the transport method
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
codex-cli 0.154.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.6-sol
What platform is your computer?
Darwin 25.6.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
VS Code
Codex doctor report
What issue are you seeing?
I am facing an issue with the WebSocket transport: for every prompt, I have to wait through five attempts before it switches to the HTTP fallback, and I haven't found an option to lock the transport method.
What steps can reproduce the bug?
Uploaded thread: 01a0934d-d72a-7e43-9a74-89cb86030f6c
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the WebSocket retry and HTTP fallback behavior in Codex CLI 0.154.0 using the uploaded thread 01a0934d-d72a-7e43-9a74-89cb86030f6c. No source file, test, or expected behavior is named in the issue, so identify the transport entry point first. Done should mean the repeated attempts or transport-selection behavior matches an agreed expectation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100