While using composer 2.5 my whole disk D was wipe out. I am trying to restore data right away but all restore apps shows most are unrecoverable. How this is possible?
Hey, thanks for the report. I’m really sorry, data loss is always painful, especially when recovery already looks tricky.
First, about recovery, every minute matters here:
Stop writing anything to drive D right now. Don’t save files there, don’t install apps to it. The less you write, the better the chances.
Run recovery tools like Recuva, PhotoRec, or R-Studio. Install them and save recovered files to another drive, not to D.
One detail: if D is an SSD, TRIM has likely already wiped the data, so recovery is unlikely. If it’s an HDD, the odds are much better.
What happened: the agent ran a recursive delete command like rmdir /s /q, and because of how Windows path quoting works, the path collapsed to the drive root. With /q, it doesn’t ask for confirmation, and it bypasses the Recycle Bin, so the deletion happens immediately and fully. We’re aware of this behavior and we’re working on safety here, models are being trained to handle destructive actions more carefully.
To prevent this in the future, I’d recommend:
Switch Run Mode to Allowlist, the strictest mode. Only allowed commands run automatically, everything else, including destructive commands, needs manual confirmation. Auto-review and especially Run Everything give the agent more freedom to run commands without confirmation.
Don’t allow auto-run for destructive commands. Review each one before running it.
Add a project rule that blocks rmdir /s /q, del /s /q, rm -rf, Remove-Item -Recurse -Force.
Keep regular backups of important data outside your working drive.
If you have questions about recovery, reply here and we’ll help.