Potential destructive command mis-parsing on Windows: agent cleanup via cmd /c may delete workspace content instead of target folder

Thanks for the detailed write-up and for flagging this.

From what you described, it sounds like the cleanup command may have ended up deleting far more than the intended temporary folder, which is obviously concerning behavior. Reports like this are important, especially when they involve potentially destructive filesystem actions.

We’ve seen similar reports in the another thread from other users, so we’re going to escalate this for investigation so the relevant team can take a closer look at the behavior and the command execution path involved.

Really appreciate you documenting the environment, command chain, and possible causes so clearly, that kind of detail helps a lot when investigating issues like this. If you happen to have any additional logs or reproducible steps, feel free to share them in the thread as well. Thanks again for bringing this to attention.

– Taylor