Codex Desktop memory grows from ~19 GB to 63 GB overnight with Figma MCP connected on Windows

What version of Codex App are you using?

Codex Desktop: 26.623.19656.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

• OS: Windows 11 Pro
• OS version: 10.0.26200
• RAM: 64 GB
• GPU: NVIDIA GeForce GPU

What issue are you seeing?

Codex Desktop appears to accumulate memory over a long idle/overnight session.

The machine has 64 GB RAM. At the beginning of the session, only Codex Desktop, an MCP connection to Figma, and a few small background apps were open. The system memory usage was around 19 GB.

After leaving the machine on overnight without closing Codex, the next morning Task Manager showed memory usage at 63.1 / 63.7 GB (99%). The machine was very sluggish and I had to force restart it to recover.

Screenshot attached shows

<img width="1080" height="1920" alt="Image" src="https://github.com/user-attachments/assets/eeadfc5a-fd3e-4268-95a7-e75b379f161c" />

Task Manager at 63.1 / 63.7 GB (99%) memory usage.

Current post-restart observations

After rebooting, the system returned to normal memory usage. A later snapshot showed Codex and related helper processes using much less memory, but Codex still spawned multiple helper/MCP processes:

Codex: 8 processes, ~1.4 GB private memory
node: 16 processes, ~1.3 GB private memory
node_repl: 5 processes
msedgewebview2: 19 processes
Figma: 14 processes, ~3.8 GB private memory
Feishu and a few small apps were also running

Because the machine had to be force restarted, I could not capture the full process tree at the exact 63 GB moment.

Expected behavior

Leaving Codex Desktop open overnight with a Figma MCP connection should not cause total system memory usage to grow from ~19 GB to nearly all 64 GB RAM.

Codex should either:

• clean up stale MCP/helper processes,
• release idle thread/app-server/renderer memory,
• or provide diagnostics showing which Codex thread or MCP process is consuming memory.

Actual behavior

System memory grew to 63.1 / 63.7 GB (99%) overnight, causing severe system slowdown and requiring a forced restart.

Steps to reproduce

1. Start Codex Desktop on Windows.
2. Use Codex with Figma MCP connected.
3. Leave Codex running overnight without closing the app.
4. Wake the machine the next morning.
5. Observe Task Manager memory usage.

Additional context

This looks related to existing reports around MCP/helper process accumulation and Codex Desktop memory/process growth, especially when MCP-backed tools are enabled.

Please let me know what diagnostics would be most useful to collect if this happens again.