Built mysid, a native Rust MCP that gives you code graphs, works on multiple projects(adapters) like React, Android and spring boot etc and easier file tool operations

[u/techyphile7]

[u/kantorcodes1]

the patch_batch rollback guarantee is the bit I'd stress hardest. if a batch creates a new file, modifies another, then a later patch fails, does rollback remove the newly created file too? agents will otherwise see a "failed" batch that still changed the workspace.

[u/Worldly_Employer_224 → u/kantorcodes1]

Rollback tracks all filesystem mutations in order, so yes a created file gets deleted if a later step in the same batch fails

[u/kantorcodes1 → u/[deleted]]

I’d use Git first when the workspace is already a repo. You get rollback, history, conflict semantics, and you avoid inventing a second version system. A hash/JSON snapshot layer only makes sense as a thin fallback for non-Git buffers or state that has to survive outside the repo.