Users are reporting that Codex may be causing excessive I/O operations, leading to lag on Mac devices, even after the application is closed. This issue necessitates a device restart to restore normal performance and is not explained by CPU or memory overuse. Previously, an incident claimed Codex caused unnecessary inflation of writing to SSDs, accelerating wear, though it was reportedly resolved. These recent observations suggest a potential ongoing problem with the application's performance impact and safety for device hardware.

Concerns have been raised about whether Codex is harmful to SSDs and Mac devices overall, questioning its safety for continued use. Users are seeking an explanation for these performance degradation issues, which have been corroborated by others on platforms like Reddit. The community is asking for clarity on the potential risks to device longevity and functionality associated with running the Codex application, especially given the previous concerns about SSD wear and the current observed lag.

This situation highlights a need for transparency and a thorough investigation into Codex's resource management and its impact on hardware. The reported lag and the echo of past SSD wear concerns warrant attention from the developers to ensure user devices are not being negatively affected. The community awaits a definitive explanation regarding the safety and operational impact of Codex on their systems, particularly concerning the excessive I/O and graphics work mentioned.