For people using AI coding in fucking VSCode — is there any way to prevent it from occasionally corrupting open files? I’m usually diligent about staging and committing to Git often, but sometimes it catches us off guard and good work gets lost. Sonnet 4 is the model in use.
#asknostr
use zed
it's infinitely better
you'll like it
If it connects to my fiat mine's AI provider (GitHub), then I'm sold. Let me check...
it does!
OK, true! 40min+ later (largest thing I've compiled in Rust in life), here we are. Is GitHub MCP Server v0.0.3 what you use as well? Take a poor man's zap, for that. Ty, sir.
zed is amazing, switched 6 months ago from vscode and havent looked back
I use Cline in VSCode and I am not aware of it corrupting files.
But I also use git extensively and revert often.
Best pattern I found recently was to get it to document the feature as an issue in GH CLI, then create and build on a feature branch.
If it fails too badly, delete the branch and try again. If you need to reboot it, bootstrap the next session from the issue and the diff.
My problem is when I get too deep in the flow and forget to close the last feature window before jumping into the next goodness. Anyway, high hopes with zed, let's see.
If you’re losing work with Sonnet, try Cursor first. it’s VSCode, but smarter about ai changes
Tried Claude Sonnet too, but it really got on my nerves. Now I've been playing around with Gemini CLI for hours, it's so much better.
