openai / openai/codex

Complaint from a $200/month Pro user—99% of quota remains, but Codex keeps reporting “Selected model is at capacity,” severely disrupting normal use

Open
#46,143 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug context rate-limits
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)?

Powered by Codex & OWL 版本 26.911.61220 发布于 2026年9月17日

What subscription do you have?

200$pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

我是每月支付200美元的ChatGPT Pro用户。本月使用Codex时频繁、连续出现错误,已严重影响正常使用。2026年9月16日仍在反复发生,并非偶发的一次失败。

我提供的额度截图显示:
通用每周使用限额剩余99%;
GPT-5.3-Codex-Spark的5小时和每周使用限额均剩余100%。

连续报错截图显示:
“Selected model is at capacity. Please try a different model.”

此外,远程上下文压缩也出现错误:
“Error running remote compact task: Selected model is at capacity. Please try a different model.”

请注意:截图中的Spark是额度页面列出的项目,不代表已确认它就是报错请求使用的模型。请结合实际请求日志排查。

我的核心问题是:付费订阅仍有效、页面显示大量额度可用,但服务持续无法正常使用。请不要在未核实日志的情况下,将此问题简单按额度耗尽处理,或只建议购买额外额度、等待额度重置。

请将此问题转交人工支持及相关工程团队,并答复:

  1. 连续失败的具体原因,是否涉及模型容量、请求路由、账号限流或远程上下文压缩服务异常。
  2. 恢复正常使用的处理方案及预计时间;若暂时无法给出时间,请明确说明。
  3. 对于已付费但持续无法正常使用的受影响时段,是否提供订阅延期、费用减免或其他补偿。

请提供可追踪的工单编号,不要仅以通用排障模板结束处理。

Image Image
What steps can reproduce the bug?

只要正常运行codex就能够复现,并且是高频率出现,已经完全无法正常使用了。一直报Selected model is at capacity. Please try a different model.错误。

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the supplied Codex version, Windows platform details, screenshots, and the repeated capacity errors, then correlate the affected requests with actual service logs. Check whether model capacity, routing, account limits, or remote compaction explains the failures; done means identifying the cause and documenting a recovery path or support escalation.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.