Codex is wearing out our devices • Hacker News Board

Re: Codex is wearing out our devices

#11

Post by sokoloff » Mon, Jul 20, 2026, 2:30 PM UTC

port3000 wrote: post #9

Does writing to an SSD often really 'wear out' the device?

Yes. NAND cells can only be erased and rewritten a finite number of times.

Re: Codex is wearing out our devices

#12

Post by mirashii » Mon, Jul 20, 2026, 2:31 PM UTC

port3000 wrote: post #9

Does writing to an SSD often really 'wear out' the device?

Yes. Flash cells in SSDs are rated for a particular number of write cycles.

Re: Codex is wearing out our devices

#13

Post by [deleted] » Mon, Jul 20, 2026, 2:31 PM UTC

[deleted] wrote: post #10

jacobgold wrote: post #8

> Codex Desktop for macOS triggers a persistent macOS Gatekeeper/SystemPolicy loop after launch. As a Linux guy, I recently did some macOS development and was incredibly annoyed by the "security" features, which seem designed to shift blame for security issues from Apple to users. macOS is constantly throwing up security screens and warnings about completely normal programs the user knowingly installed and trusted. I…

[deleted]

[deleted]

Re: Codex is wearing out our devices

#14

Post by aqfamnzc » Mon, Jul 20, 2026, 2:32 PM UTC

port3000 wrote: post #9

Does writing to an SSD often really 'wear out' the device?

Yes, they have a finite number of writes. The controller keeps track of this so you can even see what % of your SSD life is remaining in that sense.

Re: Codex is wearing out our devices

#15

Post by jsmith99 » Mon, Jul 20, 2026, 2:32 PM UTC

hyperhello wrote: post #7

The GUI app does run the fan very hard and heat the laptop for something supposedly running on the cloud. If it is using my computer to cache things and assist with tasks, okay, but if it’s just revving the motor I don’t want it to.

Mine too, on windows. It seems to be some very aggressive and poorly planned rg (ripgrep) calls mostly, when running parallel sessions. Multiple simultanous Claude code sessions don't have same problem.

Re: Codex is wearing out our devices

#16

Post by arto » Mon, Jul 20, 2026, 2:32 PM UTC

A related GitHub issue: https://github.com/openai/codex/issues/25719

Re: Codex is wearing out our devices

#17

Post by recitedropper » Mon, Jul 20, 2026, 2:33 PM UTC

Vibe code giveth, vibe code taketh.

Re: Codex is wearing out our devices

#18

Post by mirashii » Mon, Jul 20, 2026, 2:34 PM UTC

spenvo wrote: post #2

OpenAI's first related fix was in 0.142.x on June 22 but apparently it wasn't sufficient and user have continued to complain. Seems like a thread with decent additional context: https://x.com/0x_kaize/status/2078872972245225586

A Github issue with actual data instead of just someone reposting info: https://github.com/openai/codex/issues/28224

Previously discussed: https://news.ycombinator.com/item?id=48626930

Re: Codex is wearing out our devices

#19

Post by port3000 » Mon, Jul 20, 2026, 2:34 PM UTC

aqfamnzc wrote: post #14

port3000 wrote: post #9

Does writing to an SSD often really 'wear out' the device?

Yes, they have a finite number of writes. The controller keeps track of this so you can even see what % of your SSD life is remaining in that sense.

Interesting, thanks, had no idea

Re: Codex is wearing out our devices

#20

Post by mirashii » Mon, Jul 20, 2026, 2:34 PM UTC

jpadkins wrote: post #6

This reddit thread is devoid of any useful information. Just fear and speculation.

A Github issue with actual data instead of just someone reposting info: https://github.com/openai/codex/issues/28224

Previously discussed: https://news.ycombinator.com/item?id=48626930