{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihveqbs3rjqzrhdwd74ge4x3bqsc4xilgb476qjranxpkbp3wjany",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlvoxhumlhu2"
  },
  "path": "/t/frustrated-with-new-codex-limits-for-the-pro-users/1380784#post_11",
  "publishedAt": "2026-05-15T15:25:21.000Z",
  "site": "https://community.openai.com",
  "textContent": "I understand the sarcasm about my “bank account,” but that is not the issue. The problem is not whether I can afford it. The problem is that Codex limits are unclear, unpredictable, and in real usage the quota can disappear before meaningful work even starts. Also, API pricing and practical Codex usage are not the same thing. Even if GPT-5.5 is “only” around twice as expensive per token and supposedly uses fewer tokens, that does not solve the user-side problem: the product still feels unreliable when the limit is consumed too quickly. My point is simple: if Codex is sold as a serious coding tool for paid users, then access should be more predictable. At minimum, the UI should explain the limits honestly, and there should be some fallback/basic model for audits, tests, or smaller tasks after the main quota is exhausted.",
  "title": "Frustrated with new Codex Limits for the Pro Users"
}