codex - 💡(How to fix) Fix Codex is not responding... CONSTANTLY. [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21075Fetched 2026-05-05 05:53:49
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.429.

What subscription do you have?

Pro $100/mo

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Constantly get Codex is not responding with an hourglass. If you do anything it's basically out to lunch.

This is the only app on my computer that behaves this way.

It is horrible and newer versions don't fix it.

Do I need to use WPR/WPA to isolate this? this is driving me crazy.

I have one very long thread but now I'm avoiding using it and I still get the wait message.

I can't go more than a few minutes without getting this and it's gone for minutes at a time.

<img width="1232" height="677" alt="Image" src="https://github.com/user-attachments/assets/9633bf7f-aa0c-4985-818c-afc242c256c6" />

What steps can reproduce the bug?

Uploaded thread: e7675ff5-05c1-4241-b9a6-a9ae481b9cb3

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue might be resolved by investigating system resource usage or thread-related issues within the Codex App.

Guidance

  • Review the uploaded thread (e7675ff5-05c1-4241-b9a6-a9ae481b9cb3) to understand its content and potential impact on the app's performance.
  • Consider using WPR/WPA as suggested to isolate and analyze the issue, focusing on system calls, resource utilization, and potential bottlenecks.
  • Since the issue persists across different versions, it might be specific to the user's environment or data, suggesting a need to examine the app's handling of large threads or specific thread content.
  • Given the app becomes unresponsive for minutes at a time, there might be a timeout or a loop that's causing the app to hang, which could be identified through the suggested profiling tools.

Example

No specific code snippet can be provided without more details on the app's internal workings or the exact nature of the threads being uploaded.

Notes

The provided information lacks specific technical details about the Codex App's internal mechanisms or how it handles threads, making it challenging to provide a precise fix. The use of WPR/WPA could offer more insights into the system and application behavior during these incidents.

Recommendation

Apply workaround: Given the persistence of the issue across versions, using WPR/WPA to gather more detailed information about the system's behavior when the app becomes unresponsive seems like the most straightforward next step to understand and potentially mitigate the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex is not responding... CONSTANTLY. [1 comments, 2 participants]