A few nights ago, I was working on a local service.
Once the tests were up and running, Claude Code naturally executed npm run dev &, then started doing sleep 30, tail, and taking another look. No errors, so it did another sleep 30.
I almost lost it right there: this didn’t look like writing code. It looked like a night watchman making his rounds of the building with a flashlight every half hour.
Later I changed my wording and told it to stop waiting around and just use Monitor to watch the logs. Only then did it finally quiet down and move on to other things; the moment an error showed up in the logs, it came back to deal with it.
This tool isn’t exactly new, but Claude Code v2.1.310 recently filled in its availability across environments like Bedrock, Vertex, and Foundry. I noticed it again while going through the changelog, and after trying it out, my takeaway was a single sentence: when Claude needs to wait, don’t make it tough it out with sleep.
