[Windows][Quota] Luna is blocked when the Codex 5-hour quota is exhausted
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Latest(26.908.70816)
What subscription do you have?
Plus
What platform is your computer?
Windows11 x64
What issue are you seeing?
When my Codex 5-hour quota is exhausted, my Luna quota is still available. However, with the "Approve for me" approval mode enabled, a Luna task is repeatedly stopped with a message saying that my Codex quota has been exhausted.
This appears to treat the exhausted Codex quota as a global blocker, even though Luna still has remaining quota. The task can continue after switching to manual review.
Impact: Luna becomes unusable in "Approve for me" once the Codex 5-hour quota is exhausted.
What steps can reproduce the bug?
- Use Codex until the Codex 5-hour quota is exhausted while Luna still has remaining quota.
- Select or use Luna for a task.
- Enable "Approve for me".
- Start a task that requires approval or let it run.
- Observe that the task is stopped because the Codex quota is reported as exhausted.
- Switch to manual review and repeat; the task can continue.
No logs or local files are attached.
What is the expected behavior?
Luna should not be stopped solely because the Codex 5-hour quota is exhausted. Quota checks and approval gating should be model- or allowance-specific, or the error should identify the allowance that actually prevents the task from running.
Additional information
Please investigate the quota-routing and approval-gating logic between the Codex allowance and Luna. The issue is reproducible when the Codex 5-hour quota is exhausted but Luna still shows available quota.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the quota-routing and approval-gating logic for Luna and Codex allowances, then reproduce the reported Windows scenario with Codex exhausted and Luna available. Done means Luna can continue in “Approve for me” mode when only Codex quota is exhausted, or the error identifies the allowance that actually blocks the task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100