I didn’t manually edit that setting when you asked, so it should have always been using cmd, unless something automatically changed that setting at some point. I have noticed that the chats frequently try to use commands that work in powershell but not in cmd. After that chat tries that and gets the error message, it usually doesn’t make that mistake again, but new chats tend to have the same issue. But that’s still an extra erroneous tool call, with the associated real time and cache read token waste.
The chat hasn’t tried to perform a sleep command for me recently, but I’m not doing quite the same things that I was doing when I first had that issue. Although here’s a link to another person reporting a similar issue: