Luna Reserve can read files and run commands, but file edits are rejected by the regular usage limit #42910

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

26.901.41123

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When using Luna Reserve after the regular Codex usage allowance has been exhausted, Luna itself continues to work, but file-editing operations are rejected because of the account usage limit.

The important point is that Luna Reserve is not completely blocked.

In the affected session, Luna Reserve can still:

• read files in the workspace
• inspect the project
• run commands
• reason about the requested changes

However, when it attempts to modify a file, the managed file-edit operation / apply_patch is rejected with a message indicating that the account usage limit has been reached.

The Codex App reports messages such as:

"apply_patch itself was rejected due to the Codex usage limit."

and:

"The file editing tool was rejected due to the account usage limit, so the changes could not be applied."

This makes Luna Reserve effectively read-only for coding work once the regular Codex allowance is exhausted.

What steps can reproduce the bug?

1. Exhaust the regular Codex usage allowance while Luna Reserve is still available.
2. Start a new Codex App thread directly with Luna Reserve.
3. Open a local project/workspace.
4. Ask Luna to inspect and modify an existing source file.
5. Allow file modification when prompted.
6. Observe that Luna can read files and run commands successfully.
7. Observe that the actual file-edit operation is rejected due to the account usage limit.

I also reproduced the same behavior in a thread that originally used another model and later switched to Luna Reserve.

Most importantly, the issue also reproduces in a brand-new thread started directly with Luna Reserve.

Therefore, this does not appear to be caused by model switching or stale thread state.

What is the expected behavior?

If Luna Reserve is available and able to continue a Codex task after the regular usage allowance has been exhausted, file-editing operations should also be executable under the Luna Reserve allowance.

At minimum, the same workspace operations that are necessary to complete a normal coding task should remain available, including modifying existing files and creating new files.

If file modification is intentionally excluded from Luna Reserve, the UI and documentation should state this clearly, because the current behavior makes Luna Reserve appear fully usable while silently making coding tasks effectively read-only.

Additional information

This appears to be related to quota / entitlement handling for file-mutation operations rather than a general Luna Reserve failure.

Observed behavior:

• Luna Reserve inference works.
• Workspace file reads work.
• Command execution works.
• File modifications fail.
• The failure explicitly refers to the account / Codex usage limit.
• Granting file modification approval does not resolve it.
• The issue reproduces even in a fresh thread started directly with Luna Reserve.

This suggests that the file-edit path may still be checking the regular Codex usage entitlement instead of the Luna Reserve entitlement.

Related issues:

• Codex CLI cannot use Luna Reserve after standard usage limit is exhausted #40939 — Codex CLI cannot use Luna Reserve after standard usage limit is exhausted
• Cannot use gpt-reserve #41520 — Cannot use gpt-reserve
• [Desktop] Manual switch to GPT-5.6 Luna after usage exhaustion shows an active model, but every prompt remains blocked #42153 — Desktop: manual switch to GPT-5.6 Luna after usage exhaustion remains blocked

Those reports concern Luna Reserve being unavailable more generally. This report is slightly different: Luna Reserve itself remains usable, but file-edit operations specifically are blocked by the regular usage limit.

I can provide screenshots showing both successful file reads / command execution and failed file-edit operations.