Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex macOS app crashing on long tasks [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#19081•Fetched 2026-04-24 06:01:16
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
sudo-relaxsudo-relax
Participants
github-actions[bot]github-actions[bot]sudo-relaxsudo-relax
Timeline (top)
labeled ×4cross-referenced ×2commented ×1

Root Cause

This creates major problems for longer workflows because:

RAW_BUFFERClick to expand / collapse

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

Version 26.417.41555 (1858)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

The Codex desktop app has become increasingly unstable after recent updates. currently on Version 26.417.41555 (1858)

During long-running tasks (around 40–50 minutes), the app frequently crashes, especially when using OMX plugins. This has been a consistent issue over the past week.

The main problem is that when the app crashes, the task cannot resume from where it left off. This makes long workflows extremely frustrating and time-consuming, as there’s no clear way to recover progress or determine where the process failed.

Would appreciate a fix or at least a way to resume interrupted tasks.

⸻

What steps can reproduce the bug?

Steps to reproduce

  1. Open the Codex macOS desktop app.
  2. Start a long-running task that involves multiple tool calls and OMX plugin usage.
  3. Let the task continue for 40–50+ minutes.
  4. Keep the session active while Codex continues processing a large context and working through the task.
  5. After prolonged usage, the app eventually crashes unexpectedly.
  6. Reopen the app and try to continue the same workflow.
  7. Notice that the task does not reliably resume from the exact stopping point, making it hard to recover progress.

Bug explanation The Codex macOS desktop app becomes unstable during long-running, high-context tasks, especially when OMX plugins are involved. After extended use, the app crashes unexpectedly. The bigger issue is not just the crash itself, but that recovery is poor: the interrupted task does not cleanly resume from the exact point where it stopped.

This creates major problems for longer workflows because:

  • significant progress can be lost
  • it is difficult to determine the last completed step
  • resuming requires manual inference and repetition
  • long sessions become unreliable for production use

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix or workaround for the Codex app instability and poor task recovery is to implement a checkpointing or autosave feature that saves the task's progress at regular intervals.

Guidance

  • Investigate the feasibility of adding a checkpointing mechanism that saves the task's state at regular intervals (e.g., every 10-15 minutes) to allow for easier recovery in case of a crash.
  • Consider implementing an autosave feature that periodically saves the task's progress, enabling users to resume from the last saved point.
  • Review the OMX plugin usage and its potential impact on the app's stability, as it seems to be a contributing factor to the crashes.
  • Explore the possibility of optimizing the app's memory management and resource allocation to reduce the likelihood of crashes during long-running tasks.

Example

No specific code snippet can be provided without more information about the Codex app's internal implementation. However, a general example of a checkpointing mechanism could involve using a timer to periodically save the task's state to a file or database.

Notes

The provided information suggests that the issue is related to the app's stability and recovery mechanisms, but without more details about the app's internal workings, it's challenging to provide a more specific solution. The proposed workaround focuses on improving the app's ability to recover from crashes, rather than addressing the underlying cause of the instability.

Recommendation

Apply a workaround, such as implementing a checkpointing or autosave feature, to improve the app's recovery capabilities and reduce the impact of crashes on long-running tasks. This approach can help mitigate the issue until a more permanent fix can be developed.

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…
#SSR setup#ISR setup#authentication setup#request error#file not found

Still need to ship something?

×6

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

Back to top recommendations

TRENDING