{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifsybjtcifut3sv2bhy5h3hfm7qpc6kc2b5p7wt3nzxisvvq57fom",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmbuod2i3vv2"
  },
  "path": "/t/codex-rate-limits-discussion-thread/1378553?page=18#post_368",
  "publishedAt": "2026-05-20T10:41:51.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’ve tried hard to adapt to the new Codex limits instead of just complaining about them.\n\nI wrapped my use cases in skills, optimized my `AGENTS.md`, added agent-specific npm scripts with limited output, narrowed task scopes, and tried older models like GPT-5.4 mini with low effort/intelligence settings.\n\nBut even then, the first message of a brand-new Codex chat can instantly consume around 10% of the hourly limit. That makes the limit feel unpredictable and very hard to work around, even when using the product carefully.\n\nI used to promote Codex to colleagues because the pricing felt reasonable compared to Claude Code. I can’t honestly say that anymore. For the first time, moving more of this workflow to local models like Qwen actually starts to make practical sense.\n\nI’m not asking for unlimited usage. I’m asking for predictable, usable limits and clearer visibility into what a task is going to cost before it consumes a significant part of the allowance. The change in token usage changed; this suddenly made existing accounts less usable. I am hoping someone from OpenAI reads this and reconsiders.",
  "title": "Codex Rate Limits Discussion Thread"
}