Desktop: local repo auto compaction at 0% usage hard-stops and leaves local repo/worktree unstable

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

26.506.31421

What subscription do you have?

Pro x5

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Note: This is newly introduced behaviour which I have observed since the introduction of manual /compact. Previous behaviour allowed tasks to complete cleanly when after reaching 0% rate limit the automated context compacting was triggered.

Problem: When using the Codex Desktop App against a local repository, if context compaction is triggered automatically by the system when usage/rate limit is at 0%, Codex will hard-stop instead of continuing, leaving the local repository/worktree in an unstable state after the hard stop.

Observed/claimed behavior:

• Codex is operating on a local repo from the Desktop App.
• Usage/rate limit reaches 0%.
• Automated context compaction starts or is attempted.
• Codex hard-stops.
• The local repo/worktree is left dirty, partially modified, or otherwise ambiguous.
• Manual recovery through git is required or alternatively wait until rate limit resets and then ask agent to recover/continue.

This appears to be a repository-integrity bug, not just a compaction/rate-limit UX bug. Quota exhaustion should not leave the user's working tree partially modified or ambiguous.

What steps can reproduce the bug?

Approximate reproduction path:

1. Open Codex Desktop App.
2. Open a local repository.
3. Work in a long-running session until context compaction is needed.
4. Continue until usage/rate limit reaches 0% or near 0%.
5. Wait for system to trigger compaction automatically
6. Observe that Codex hard-stops.
7. Inspect the repo with:

git status --short
git diff
git diff --staged

Observe that the repo/worktree is left unstable, partially modified, or otherwise ambiguous.

What is the expected behavior?

Same behaviour as before the introduction of manual /compact: tasks can always complete cleanly.

Additional information

_No response_