What changed and why? | June 8, 2026

I just pushed an update that removes the right-click context menu integration and adds SHA-256 post-copy verification.

Why remove the context menu?
The context menu worked by spawning a short-lived process on right-click that queried Explorer's COM interface to find out what you'd selected. The problem: that process raced against Explorer's own foreground state. Most of the time it was fine. Sometimes — especially if the menu opened quickly or the system was under load — it grabbed the previous selection instead of the current one. You'd right-click a folder, hit Quick Copy, and it would silently queue the wrong folder for copy. I can't ship a file operation tool that fails silently like that. So I pulled it until I can make it reliable.

What was added instead: SHA-256 verification
After a copy finishes, RoboExtension can optionally re-read every destination file and compare SHA-256 hashes against the source. Any file with a mismatched hash is flagged in a results dialog, listed with its error, and offered a one-click re-copy. Enable it in Settings → "Verify files after copy (SHA-256)". It's off by default because it roughly doubles elapsed time on large jobs — but when you're archiving irreplaceable files, migrating drives, or copying over a network you don't fully trust, it's the only real confirmation that your copy actually worked.

What's unchanged
All keyboard shortcuts — Ctrl+C, Ctrl+X, Ctrl+V, Delete, Shift+Delete — work exactly as before. The tray process owns the entire keyboard flow with no cross-process races, so it's never had this problem.

The context menu will come back. Just not until it works correctly every time.