The Four-Hour Session Treadmill
Claude Code, "just one more prompt," and work-life balance. 300 words, 90 seconds reading time.
Claude Code can erode your work-life balance if you’re not careful. I’m generally pretty good about turning off and not working at home in the evenings.1 But Claude Code has opened up a loophole in my own discipline. Typing a few prompts and walking away doesn’t feel like working. It’s not like sitting down to write code for an hour. You fire off a planning prompt, go do something else, come back in 20 minutes to review the output, nudge it in a new direction, and walk away again.2
The problem is that you can do this indefinitely. I’ve caught myself kicking off plan-and-implement cycles in the evenings, trying to squeeze everything I can out of my four-hour session window.3 A prompt or follow-up takes 30 seconds. Each response might take 30 minutes. In between I’m technically not at my desk. But my laptop is open, my attention drifts back to it, and my evening has become an extension of my workday with the “just one more prompt.”
Claude Code genuinely does make me more drastically more productive. It’s a helpful tool, and I’ll continue to use it. But I’m starting to think the ease of it is what makes it hard to put down.
Early mornings are a different story entirely. I’m at my sharpest, have zero distractions, and not eating into time with the family. Hence why this newsletter is coming to you at around 5am ET today.
Another thing this has encouraged me to do is use the --dangerously-skip-permissions flag, which stops CC from asking me if it’s okay to do what it’s suggesting. Sure, it can create, overwrite, or delete all the files in a project. That’s what version control is for. #YOLO.
This is made worse by a “promotion” Anthropic is running March 13-27, doubling your session usage and not counting it toward your weekly usage, when you’re using Claude outside peak work hours.