stream disconnected - retrying sampling request (1/5 in 205ms)-codex
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 12/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust
- Domain
- networking
Research direction
The log points at the retry path in codex_core::responses_retry and the websocket connection in responses_websocket, which connects to wss://chatgpt.com/backend-api/codex/responses. Start by reading how the retry loop records sampling_error and why the auth_error fields come through empty. The issue does not say what behaviour is expected, so a first step is to ask the maintainers what the fix should be. It is not clear what done looks like yet.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
0.153.4
What subscription do you have?
stream disconnected - retrying sampling request (1/5 in 205ms)-codex
What platform is your computer?
No response
What issue are you seeing?
WARN codex_core::responses_retry
stream disconnected - retrying sampling request (1/5 in 205ms)...
turn_id=01a11e7e-60ec-7a30-8cd6-010e5e604426
retries=1 max_retries=5
sampling_error=unexpected status 503 Service Unavailable:
An error occurred while processing your request.
(2/5 in 401ms) ... status 503 Service Unavailable
(3/5 in 728ms) ... status 503 Service Unavailable
(4/5 in 1.553s) ... status 503 Service Unavailable
(5/5 in 3.386s) ... status 503 Service Unavailable
INFO responses_websocket:
successfully connected to websocket:
wss://chatgpt.com/backend-api/codex/responses
这次错误里没有记录 error.code、Retry-After 或服务端 request_id；相关字段是空的：
auth_error=""
auth_error_code=""
auth_request_id=""
auth_cf_ray=""
从日志看，每次重试都能重新连上 wss://chatgpt.com/backend-api/codex/responses，因此不像 TCP 443 或 WebSocket Upgrade 被完全拦截，更像服务端暂时返回 503（过载/后端不可用）。代理仍可能在握手后返回 503，但证据偏向服务端问题。
另外，当前环境确实有 Codex CLI，但版本不一致：
/opt/homebrew/bin/codex
codex-cli 0.153.4
桌面内置 CLI 是 0.160.1，当前桌面日志也显示 client_version=0.160.1。
What steps can reproduce the bug?
01a11e7e-49c0-7cd2-aff7-8de136e25b1d
What is the expected behavior?
No response
Additional information
No response
- Dominant language
- Rust
- Stars
- 129k
- Forks
- 20.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from openai/codex
-
Python SDK: CodexClient.close() leaves the app-server's stdout/stderr pipes open (and never waits after kill)Possibly taken @akhil9tiet claimed this 1 day ago. Openapp-server bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openai/codex#54908 · 2 comments ·
Maintainers usually reply within 1 day
-
bug CLI tool-calls windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Clarification about NODE_REPL_TRUSTED_BROWSER_CLIENT_SHA256S in the VS Code extension environmentOpendocumentation extension windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openai/codex#54780 · 1 comment ·
Maintainers usually reply within 1 day
-
bug context
Difficulty 2/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
Similar issues
-
documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug good first issue priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Konfirm-xyz/konfirm-contracts#163 ·
Maintainers usually reply within 1 day
-
area:gc-repack-output bug factory:dogfood factory:triaged priority:p3 type:bug type:ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gitbutlerapp/grit#1161 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
feature performance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
lance-format/lance#10137 ·
Maintainers usually reply within 2 days