codex - 💡(How to fix) Fix "Memories" consuming rate limit disproportionately [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19105Fetched 2026-04-24 06:00:54
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
0
Timeline (top)
commented ×3labeled ×3closed ×1cross-referenced ×1

Root Cause

I just ended up disabling the memories feature because it renders Codex unusable with the current rate limit consumption.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.417.41555

What subscription do you have?

Enterprise

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Since I activated "memories", my weekly rate limit has been going down disproportionately when Codex is idle. In the very beginning, it ate up almost the entirety of the remaining 40% of my weekly limit while the app was idle. I thought it was normal, as it had to go through all the existing threads. But then it continued. Now whenever I leave Codex idle, even if the only "new thread" since it last processed memories was a short one (< 500 tokens) during which I didn't do anything complicated, suddenly my weekly rate limit drops by 10% or more. Not sure if it's an issue with how inefficiently Codex is consuming tokens to generate memories, or a problem in how the consumption is calculated while memories are being created.

What steps can reproduce the bug?

  1. Activate memories in the Codex app on Windows.
  2. Wait for a few days until leaving the app idle doesn't cause token consumption anymore.
  3. Open a new thread, exchange a couple of messages. Check the remaining weekly rate limit at the end.
  4. Close any other Codex surfaces other than the app, and make sure all background/cloud tasks and automations are stopped.
  5. Leave the Codex app idle for ~1 hour.
  6. Check the remaining weekly rate limit again.

What is the expected behavior?

Based on normal rate limit consumption when actively using Codex, the weekly rate limit should be affected by no more than 2-3% for processing a short chat of ~400 tokens and extracting insights/memories from it.

Additional information

I just ended up disabling the memories feature because it renders Codex unusable with the current rate limit consumption.

extent analysis

TL;DR

Disable the "memories" feature to prevent excessive weekly rate limit consumption when the Codex app is idle.

Guidance

  • Verify that the issue is specific to the "memories" feature by re-enabling it and monitoring the weekly rate limit consumption.
  • Check if there are any background tasks or automations that could be contributing to the excessive token consumption.
  • Consider reaching out to the Codex support team to report the issue and request assistance in optimizing the token consumption for the "memories" feature.
  • Monitor the weekly rate limit consumption when actively using the Codex app to establish a baseline for normal consumption.

Notes

The issue seems to be specific to the "memories" feature and the Codex app on Windows. The exact cause of the excessive token consumption is unclear, but disabling the feature appears to mitigate the issue.

Recommendation

Apply workaround: Disable the "memories" feature until a fix or optimization is available, as it currently renders the Codex app unusable due to excessive rate limit consumption.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix "Memories" consuming rate limit disproportionately [3 comments, 3 participants]