Stream error #4367

Activity

1. EthanDuan05

   added

   bugSomething isn't workingSomething isn't working

   on Sep 27, 2025
2. maxiedaniels commented on Sep 28, 2025

   

   maxiedaniels

   on Sep 28, 2025

   More actions

   I fixed this yesterday by logging out and back in on Codex, but its happening today suddenly again. Surely this is a bug?

   👍React with 👍1Reacted by 이정민

   ❤️React with ❤️1Reacted by Yucheng Duan
3. codedevmk commented on Sep 28, 2025

   

   codedevmk

   on Sep 28, 2025

   More actions

   same issue, yet when I check my context rate it clearly shows near zero usage.
   5h limit. 0% used · resets 11:13 PM
   Weekly limit. 10% used · resets Oct 1

   ❤️React with ❤️1Reacted by Yucheng Duan
4. CryptoScient commented on Sep 28, 2025

   

   CryptoScient

   on Sep 28, 2025

   Last edited by CryptoScient

   More actions

   I have tried everything in the past week to make this work but still get 401 errors. Only direct responces API works:

   What we’ve checked so far:
   • Headers policy: true none (no OpenAI-Project/OpenAI-Organization), project-only, project+org, and org-only. ✔️
   • Config hygiene: API‑key mode, wire_api="responses", correct TOML mapping. ✔️
   • CLI versions: 0.40.0 → 0.43.0‑alpha.2, each pinned with npx. ✔️
   • Base URLs: both root and v1 variants to detect path vs. auth issues. ✔️
   • Controls: direct Responses API (sync + SSE) succeed. ✔️

   This is exactly the right isolation sequence. It shows the problem is specific to the CLI’s streaming endpoint authorization, not key or project.

   If anyone finds the solution please let me know

   ❤️React with ❤️2Reacted by Yucheng Duan and Bl4ckh34d
5. Bl4ckh34d commented on Oct 4, 2025

   

   Bl4ckh34d

   on Oct 4, 2025

   More actions

   Same problem here but no solution so far.

   ❤️React with ❤️1Reacted by Yucheng Duan
6. scottjs commented on Oct 8, 2025

   

   scottjs

   on Oct 8, 2025

   More actions

   I was having this issue when trying to wire this up with a github action, this I had to run codex login first by piping the API key.

   This is how I've fixed it:

         - name: Prepare Codex home
           run: |
             export CODEX_HOME="${{ runner.temp }}/.codex"
             echo "CODEX_HOME=$CODEX_HOME" >> $GITHUB_ENV
             mkdir -p "$CODEX_HOME"
             touch "$CODEX_HOME/config.toml"
   
         - name: Codex login
           env:
             OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
           run: |
             printf '%s' "$OPENAI_API_KEY" | codex login --with-api-key
             codex login status
   
         - name: Run Codex CLI
           run: |
             set -e
             codex --full-auto exec -s workspace-write -- <<'PROMPT'
             Implement JIRA ticket ${{ inputs.issue_key }}: ${{ inputs.issue_summary }}.
   
             ${{ inputs.issue_description }}
   
             Requirements:
             - Follow repository conventions.
             - Do not modify CI workflows.
             - You are running in CI/CD mode.
             PROMPT
   

   This was originally inspired by: https://cookbook.openai.com/examples/codex/jira-github

   If you're just trying to use your standard ChatGPT account (and not use the API) the resetting your local env and re-logging in also seems to help.

   👍React with 👍1Reacted by Brian Rue
7. mahmutsalman commented on Oct 13, 2025

   

   mahmutsalman

   on Oct 13, 2025

   More actions

   I am having the same issue, too. Although I haven't used it and I have a usage limit, this error still occurs. After i log out and log in again it resolved for now.

   👍React with 👍1Reacted by Nhi Hin
8. naillizard commented on Oct 16, 2025

   

   naillizard

   on Oct 16, 2025

   Last edited by naillizard

   More actions

   I'm having this issue also, if I login with chatgpt plus it just works, I then logout from chatgpt and use an apikey from openai with full access and I start getting these errors:

   stream error: exceeded retry limit, last status: 401 Unauthorized, request id: ********-AKL; retrying....
   

   Funny thing is, using opencode with the gpt-5-codex works!

   
9. naillizard commented on Oct 16, 2025

   

   naillizard

   on Oct 16, 2025

   More actions

   I'm having this issue also, if I login with chatgpt plus it just works, I then logout from chatgpt and use an apikey from openai with full access and I start getting these errors:

   stream error: exceeded retry limit, last status: 401 Unauthorized, request id: ********-AKL; retrying....
   

   Funny thing is, using opencode with the gpt-5-codex works!

   

   never mind, I resolved it, missed an important step

   codex --config preferred_auth_method="apikey"

   https://developers.openai.com/codex/pricing#use-your-api-key-with-codex-cli
10. etraut-openai commented on Nov 12, 2025

    

    etraut-openai

    on Nov 12, 2025

    Contributor

    More actions

    This was a problem with token refresh. It has been fixed in more recent versions, so I'm going to close this issue. If you're seeing other stream errors with the latest version of codex, please open a new issue.
11. etraut-openai

    closed this as completedon Nov 12, 2025