At 09:12 on October 9, 2026, a single test command using gpt5.6 luna with low reasoning effort consumed 9% of my usage allowance. This is clearly abnormal. I request a reset or compensation.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 5/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- payments
Research direction
The payload names no source file, test or entry point; it is a report of unexpected usage-quota consumption on one account, with a feedback ID and the same sentence repeated in several fields. Read the three comments first to see whether maintainers have taken it up. Any real work needs the usage-metering code, which the payload does not show, and a reproduction. Account refunds or quota resets are decided by the maintainers, not by a code change.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
2026年10月9日09:12 ，用gpt5.6 luna 轻度发了一条test命令，结果消耗9%的使用量，明显异常。要求重置或者补偿。
What subscription do you have?
2026年10月9日09:12 ，用gpt5.6 luna 轻度发了一条test命令，结果消耗9%的使用量，明显异常。要求重置或者补偿。
What platform is your computer?
2026年10月9日09:12 ，用gpt5.6 luna 轻度发了一条test命令，结果消耗9%的使用量，明显异常。要求重置或者补偿。
What issue are you seeing?
2026年10月9日09:12 ，用gpt5.6 luna 轻度发了一条test命令，结果消耗9%的使用量，明显异常。要求重置或者补偿。
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a11e43-bdb8-7c63-b083-810360f9a31c
What is the expected behavior?
No response
Additional information
No response
- Dominant language
- Rust
- Stars
- 129k
- Forks
- 20.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from openai/codex
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
app-server documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openai/codex#55328 · 1 comment ·
Maintainers usually reply within 1 day
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openai/codex#55122 · 2 comments ·
Maintainers usually reply within 1 day
-
Python SDK: CodexClient.close() leaves the app-server's stdout/stderr pipes open (and never waits after kill)Possibly taken @akhil9tiet claimed this 2 days ago. Openapp-server bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openai/codex#54908 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
home-assistant/installer#308 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
swc-project/swc-next#1053 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nautechsystems/nautilus_trader#5387 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NomicFoundation/edr#1872 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
linebender/resvg#1179 · 1 comment ·
Maintainers usually reply within 2 days