Skip to content

Codex hangs during cli command execution #7156

Closed

Description

@nachoal

What version of Codex is running?

0.63.0

What subscription do you have?

pro

Which model were you using?

gpt-5.1-codex-max high

What platform is your computer?

macos

What issue are you seeing?

Hangs during terminal command execution

What steps can reproduce the bug?

Uploaded thread: 019aacc6-8ec2-76f1-afce-dda179c44f12

What is the expected behavior?

actually run basic bash cli commands without getting stuck.

Additional information

No response

Activity

  1. rehatkathuria commented on Nov 22, 2025

    @rehatkathuria

    I'm seeing this too

  2. enbrill commented on Nov 22, 2025

    @enbrill

    I think Codex is down, but it's not reported or showing as down.

  3. asafyish commented on Nov 22, 2025

    @asafyish

    can confirm. does half the job then stuck. worked till a few minutes ago (used it all day long without an issue)

  4. faicalghoul commented on Nov 22, 2025

    @faicalghoul

    same for me, codex seems down, sometimes switching to gpt-5.1-codex instead of max works but it's not consistent.

  5. timothymarois commented on Nov 22, 2025

    @timothymarois

    same for me. no longer works after the latest updates

  6. danielsikorskiy commented on Nov 22, 2025

    @danielsikorskiy

    same

  7. gregkonush commented on Nov 22, 2025

    @gregkonush

    codex is kind of down

  8. gregkonush commented on Nov 22, 2025

    @gregkonush

    post memes while we are waiting

  9. togosh commented on Nov 22, 2025

    @togosh

    down for me too

  10. PaulSolt commented on Nov 22, 2025

    @PaulSolt

    I get one response if I'm lucky. Then it just hangs.

  11. wovels commented on Nov 22, 2025

    @wovels
    Image it got up for a moment, to revert some 'problematic commitst', then went back down
  12. CubicFX commented on Nov 22, 2025

    @CubicFX

    I actually hadn't updated yet, was on a older model and was having this same issue. Just updated to try to fix it and it's still the same thing.

  13. 75 remaining items

  14. brianduff commented on Nov 23, 2025

    @brianduff

    This appears to be broken again.

  15. noalphakamp commented on Nov 23, 2025

    @noalphakamp

    Just when I thought I was able to start working again, im constantly getting reconnecting messages.

  16. attisbarros commented on Nov 23, 2025

    @attisbarros

    Reconnecting...

  17. rehatkathuria commented on Nov 23, 2025

    @rehatkathuria

    ■ stream disconnected before completion: Transport error: Error while reading
    the server response: error decoding response body, request id: XXXXX

  18. braincyclone commented on Nov 23, 2025

    @braincyclone

    This is still happening.

  19. pauldeden commented on Nov 23, 2025

    @pauldeden

    Same here.

  20. bclements commented on Nov 25, 2025

    @bclements

    Samesies

  21. dungthh commented on Nov 26, 2025

    @dungthh

    Same here.

  22. GonyRosenman commented on Nov 26, 2025

    @GonyRosenman

    still for a few days

  23. devtonic0 commented on Nov 28, 2025

    @devtonic0

    mine was working fine, all up until last night when it just started loading infinitely. been stuck on loading since last night, not even thinking, cant see my chats, nothing. Guess i either gotta go back to the basics and write it myself like a peasant, or switch to claude.

  24. vlad-at-work commented on Nov 29, 2025

    @vlad-at-work

    Same problem with the VSCode client, but it seems related to a very large chat / history that gets to 100% chat context window.

  25. devtonic0 commented on Nov 30, 2025

    @devtonic0

    Same problem with the VSCode client, but it seems related to a very large chat / history that gets to 100% chat context window.

    #7395

    here, i found whats bloating the session history.

  26. ASoldo commented on Dec 4, 2025

    @ASoldo

    happening again!!!! hangin on shell commands

  27. etraut-openai commented on Dec 4, 2025

    @etraut-openai
    Contributor

    I'm going to lock this issue because the root cause for this problem was due to a specific service outage, and it has been fixed. If you're seeing similar symptoms now, please file a new issue with relevant details.

  28. locked as resolved and limited conversation to collaborators on Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions