I can sometimes be lazy and I tell Claude to just fix things for me and this time it didn’t turn out so well. I was working on an iOS app and needed to set the clock to a specific time to create some screenshots. I told Claude to fix it for me as I had to do some other stuff. To fix it Claude told me to run sudo systemsetup -setusingnetworktime off && sudo date 090306494026.00 ( DO NOT RUN THIS ) and in a weak moment I just ran the command without thinking any more about it. It was stupid, but these things can happen to the best of us. The command above set my Mac to the year 4026. In seconds it froze. It would boot, show the Apple logo and complete the loading bar, but then I only got a black screen with a mouse cursor. The startup disk was gone. It felt like I had ended up in purgatory. Recovery mode behaved the same way. No matter what I tried, I could only get to a black screen and see the mouse pointer. What followed was several hours of frustrating troubleshooting. I tried safe mode, recovery, fallback recovery, bootable media and multiple DFU Revive attempts from another Mac. DFU kept failing with error 4042, even after trying different cables, macOS versions and IPSW files. The breakthrough came after I found someone with a similar DFU issue who had fixed it by installing Xcode on the host Mac. Before that, I had also tried a DFU Restore, which failed, so I can’t say for sure whether that changed anything behind the scenes. After installing and launching Xcode, I put the Mac back into DFU and tried Revive again using the same cable and setup as before. This time the firmware actually started updating and the Mac finally made it into Recovery Assistant. Any way, I think this is super weird. The ironic part is that changing the Mac’s system clock was never necessary in the first place. The iOS Simulator has a proper command for overriding the time shown in the statusbar. I also wonder why Claude (I think I used Opus 5 High) would recommend such a destructive command in the first place? Anyway, a few lessons learned I hope also can serve as a reminder and awareness to all of us busy coders: Being lazy is not always efficient. Don’t blindly run commands just because an AI tells you to. Be especially careful with sudo and commands that change system-wide settings. Take backups more often guys. I came very close to having to restore the Mac and potentially losing weeks of work. Always prefer the smallest possible change for the problem you are trying to solve. Happy coding guys! submitted by /u/deeplycuriouss
Originally posted by u/deeplycuriouss on r/ClaudeCode
