{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidlyy5s7ma6fmydwgi26yj6aijklkrmwwdwx6qqkz4apevhdkuzqq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnvqt2uw7tg2"
  },
  "path": "/t/codex-rate-limits-discussion-thread/1378553?page=19#post_383",
  "publishedAt": "2026-06-10T02:44:42.000Z",
  "site": "https://community.openai.com",
  "textContent": "update on codex pro 20x quota case 09851164\n\nsupport has now received a machine readable evidence package with aggregate local codex session log summaries\n\ncurrent weekly window june 6 to june 10\nvisible token increments 834191839 about 834 million\ncached input 771482752 about 771 million\ngeneral codex weekly used percent 84\n\nprior reset aligned week may 30 to june 6\nvisible token increments 1102151877 about 1 billion 102 million\nmax weekly used percent only 14\n\nthis is the same paid pro 20x account\nthis week has lower visible token volume than the prior reset aligned week but dramatically higher quota burn\n\nthis needs a backend quota accounting review not a generic explanation about rolling or capacity managed limits\n\nplease escalate to codex quota accounting and check cached token accounting long running context compaction fast mode go mode bucket classification spark versus general codex quota buckets and account tier classification\n\nplease restore or adjust the weekly quota while the investigation is pending",
  "title": "Codex Rate Limits Discussion Thread"
}