Codex spawned 1000s of Zombies even after not being used for several days

Resolved 💬 3 comments Opened Feb 23, 2026 by avishj Closed Feb 23, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.104.0

What subscription do you have?

None

Which model were you using?

_No response_

What platform is your computer?

Darwin 24.6.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Terminal.app

What issue are you seeing?

^ Title codex has spawned 1000s of Zombie processes that essentially crashed my computer as no other process could be spawned. You can see the count by the scroll indicator of the attached screenshot, it's tiny even after filtering by codex!

<img width="955" height="633" alt="Image" src="https://github.com/user-attachments/assets/7dc8e349-96eb-4564-9c19-60e373ddd43b" />

What steps can reproduce the bug?

N/A. Unsure. I have not used Codex in several days.

What is the expected behavior?

Not create or leave behind so many processes, especially when not being used?

Additional information

_No response_

Edit: I checked the exact count -

<img width="226" height="86" alt="Image" src="https://github.com/user-attachments/assets/1a677ba7-df41-403a-9e11-d6a20500bccc" />

This 2256 process is after I manually killed 100s. So indeed, there were 1000s of these zombie processes.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 6 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #12491

Powered by Codex Action

avishj · 6 months ago

Even after killing all of them via sudo pkill -f codex, I'm still getting non stop codex instances spawning. This is despite not opening codex once.

<img width="417" height="45" alt="Image" src="https://github.com/user-attachments/assets/bf51047c-31d5-449c-918f-7a54981b342e" />

163 new instances in 2.5 hrs, roughly 1 instance per minute. There is probably some cron setup within codex that is auto launching codex in the background?

avishj · 6 months ago

Nevermind, on debugging this further, this seems to be a bug in tddworks/ClaudeBar.

<img width="741" height="314" alt="Image" src="https://github.com/user-attachments/assets/bfb31300-212b-4c3a-b7ac-3e5adb7bdec1" />

I will raise an issue there, but is it possible for codex to not spawn if it detects a certain number of existing instances? There could probably be some reasonable limit even considering power users?