Codex 28 · Theme · #51

High RAM usage in Codex

9people describe this

1 on Rantr · 8 on X

6 problems · 2 ideas · first reported 10 Oct 2026

X replies to the promise post are counted apart from Rantr votes. “This happened to me too” adds your browser to this theme on Rantr, once.

Where OpenAI stands

Not addressed yet

No recorded announcement has answered this yet.

In their words

What people said

Problem
1. Bug: Worktrees don’t work properly. Changes get deleted. 2. Bug: Your models increasingly ignore instructions and behave destructively. 3. I can’t trust Codex with anything. It has deleted my app logic three times. 4. Codex consumes way too much RAM.

@peto455 on X ↗ · 19 Oct 2026
Problem
Im, for the first time, running out of RAM. What gives?

@evantruess on X ↗ · 15 Oct 2026
Problem
Can you optimize the memory usage of codex? It took so much space to run.

@54fby7yzwh on X ↗ · 14 Oct 2026
Idea
Great update! Could you also look into the memory leak issue? When the app is left open for a long time, memory usage grows exponentially. It looks very similar to what's being discussed in this issue. https://t.co/EdONzrIIAy

@justin260907 on X ↗ · 14 Oct 2026
Problem
While your at it, maybe look at why Codex takes 6G+ of memory for basically nothing a ruins a 32G laptop.

@R2Jules on X ↗ · 14 Oct 2026
Problem
On top of that, past few days constant all codex can eat on 64 GB of memory, needing to hard reboot the computer, @thsottiaux lmk if you need logs 🪵

@JamieBudesky on X ↗ · 13 Oct 2026
Problem
Love the bigger context, but Codex desktop is already eating my Mac. MacBook Air M4, 16GB RAM, 512GB SSD (408GB used). Swap at 13.6/14GB; Codex renderer ~550MB, codex CLI ~400MB. Any tips to keep Codex's memory and caches in check?

@yGvQWOKygU889PG on X ↗ · 12 Oct 2026
Idea
tibo, please fix chatgpt/codex app ram consumption! it does consume far more ram than claude desktop app and t3 code

@xy1ith on X ↗ · 10 Oct 2026

Your experience

Had this too? Say what happened.

JEV reads your words as you type and shows which theme they belong to. It may place them in another theme if that fits better.

What happened with “High RAM usage in Codex”?

0 / 1200

Tell us a little more — at least 20 characters.

Your words stay yours.

AI reads your draft as you type. Only what you publish is public. Privacy

Not sure where to start?

Think of the last task you tried. What were you doing, what happened, and what would have helped? You can also say you haven't tried a change yet.

01
What you said

Read as you type: a win, a problem or an idea, and the words that carry it.
Ready when you are
Who else had it

The theme your words join, and how many people on Rantr and X described it.
Where OpenAI stands

Shipped, reset, or not addressed yet, from the recorded announcements.
What to do now

A step the announcements make possible for you, when there is one.

Status

Where OpenAI stands

“Shipped” means an announcement was linked to the theme by AI, not that the problem is fixed for everyone. “Not addressed yet” means no recorded announcement was linked; it is not proof that nothing changed.

No recorded announcement has been linked to this theme yet.

Corrections

Changes to this theme

26 Oct 2026, 10:03 UTC

“Worktree changes disappear” was merged into this theme: JEV judged them the same problem.
15 Oct 2026, 05:24 UTC

Renamed from “Higher RAM use in app” to “High RAM usage in Codex” as more people described it.
15 Oct 2026, 05:24 UTC

“Memory usage grows over time” was merged into this theme: JEV judged them the same problem.

Follow this theme by email

We send a confirmation link first; nothing else is sent until you confirm. Then at most one email a day, only when the theme changes.

X thread: 2769 replies to the promise post collected (4 Oct 2026 – 26 Oct 2026): 2555 placed in a theme and 214 set aside as off-topic or unsafe. X replies are found by search and each one is checked against its public post on X. Last read: 26 Oct 2026, 23:46 UTC. Not every reply is read.

← Every theme