Skip to content

[Windows][Codex App][Blocker] Repeated freezes and full application crashes consumed 100% of my weekly Pro usage within 24 hours #35606

Description

@KaanSevinc

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

26.721.41059

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

The Codex App on Windows has become unusable because tasks repeatedly freeze, abort, or crash the entire application.

This is a separate and broader issue in addition to a previously reported tool-output/context failure. That earlier issue produced the message:

“Output exceeded the available model context and was truncated”

even for a one-line Git command.

The current issue affects the complete desktop application:

  • Tasks stop progressing and freeze.
  • Tasks abort before completing any meaningful work.
  • Failed task windows suggest restarting, updating, or creating another task.
  • Newly created tasks also fail.
  • The complete Codex application closes unexpectedly.
  • After reopening it, the application may report that it is not working.
  • I am then required to open the Microsoft Store and use Update or Restore before the application can be used again.
  • After restarting, updating, or restoring the application, the same instability can return.

The problem is not limited to a specific repository or an old task. It also occurs in newly created tasks.

The local repository remains accessible in a normal terminal. No repository corruption, Git permission failure, or filesystem permission error is reported.

The application currently cannot be used reliably for development work.

Within approximately 24 hours, these repeated crashes, frozen tasks, restarts, and replacement tasks consumed 100% of my weekly ChatGPT Pro usage allowance while producing almost no meaningful project progress.

This is an unacceptable state for a paid Pro subscription. Please investigate both the application crashes and whether the usage consumed by failed runs can be restored or credited.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019fa37d-cbcf-7f60-8cbd-29f6db561fc3

What is the expected behavior?

Codex should remain stable while completing development tasks.

A failed tool call or task should not freeze or terminate the entire desktop application.

If an internal error occurs, Codex should:

  • stop the failed operation cleanly
  • preserve the current workspace and task state
  • display a useful diagnostic message
  • allow the task to be retried
  • avoid requiring the complete task context to be recreated
  • avoid consuming substantial paid usage for repeated failed operations
  • remain launchable without requiring Microsoft Store repair or updates

Creating a new task should provide a reliable recovery path.

Usage consumed by application crashes and failed internal operations should not be charged against the user’s weekly allowance.

Additional information

The issue occurred approximately 40 times within the last 24 hours across multiple tasks, restarts, and newly created chats.

This is not an isolated crash. It is a persistent failure pattern that has made Codex effectively unusable and consumed 100% of my weekly Pro usage allowance within approximately one day.

A separate concern is that Codex has created approximately 60 GB of application data on the system drive, even though my development workspace is located on another partition. The application does not clearly explain what these files contain, which projects they belong to, whether they are safe to remove, or how the storage location can be changed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingperformancerate-limitsIssues related to rate limits, quotas, and token usage reportingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions