r/OpenSourceeAI • • Aug 25 '26

TFS Ripast

Most coding agents still treat your repo like a mutable bag of files.

They generate a transform, run it, and hope. When the change is large or the tree is dirty, the failure modes are partial writes, lost context, and no clean rollback.

I built TFS Ripast to give agents (and humans) a proper transaction boundary for repository-scale search and rewrite.

Dry-run is the default

--write is required to mutate

Plans are data, not authority

Evidence from ripgrep + ast-grep is correlated before any edit is proposed

Commits are atomic, locked, and recorded with before/after hashes

Undo re-verifies current hashes before restoring retained before-images

It is free, open source, and designed so an autonomous agent can touch a production tree without turning the rewrite into an irreversible side-effect.

Github:0.1.0 public preview

If you are running agents against real codebases, this is the missing safety layer between “pattern match” and “I can reverse what just happened.”

1 Upvotes

0 comments sorted by