Claude Code now resumes after a usage limit — unless your Mac fell asleep Claude Code v2.1.234+ now automatically resumes a session after a usage limit resets, but the auto-continue fails if the Mac slept for more than about 30 minutes during the wait, leaving the session stalled on a "Press enter to continue" prompt. A developer who builds Lidnight, a menu bar app that keeps a MacBook awake with the lid closed while AI agents work, documented the behavior along with Claude Code hooks — StopFailure with error "rate_limit" and Notification types quota_auto_resume_fired, quota_auto_resume_stale and quota_auto_resume_disabled — that signal when a wait starts and ends. If you're on a Claude subscription, recent versions of Claude Code v2.1.234+ do something quietly great: when a usage limit stops Claude mid-task, the session waits and continues the task on its own after the limit resets. Usage limit reached · limit resets 3:45pm Continuing automatically at 3:45pm · esc to cancel That's exactly what you want for a long refactor you start before bed. There's one catch, straight from the docs: If it slept for more than about 30 minutes and the limit reset while it slept, the first line reads Your usage limit has reset and the second reads Press enter to continue . So if your MacBook goes to sleep during the wait — lid closed, or just idle sleep — you wake up to a prompt asking you to press Enter, and the work hasn't moved. The 5-hour window means the wait can easily be a few hours. The wait itself uses almost no CPU, which is the problem: from the outside, a session waiting for a reset looks idle. DIY: if you're at a desk on power, caffeinate -i in another terminal or caffeinate -w