My immediate hesitance with a tool like this (which sounds awesome) is that I don't actually trust tools like Claude Code unless I have them running in a git directory where I can see exactly what changed, and easily revert when needed.

Do y'all have a solution for this here? Some kind of safety layer of some kind to easily review and optionally revert actions the agent has taken across my entire file system?

The search part of this is cool, but if the write side is solved, shut up and take my money.

▲

aabhay 7 hours ago | parent [-]

We're adding that feature to be able to manually approve agentic actions! You can already revert things, as our file system is fully version controlled.

▲

lumirth 4 hours ago | parent [-]

Genuine question: why is that a feature that you have to add, instead of something foundational? Most folks, I'd wager, are sloppy about backups, so a level of manual control and oversight seems vital!

	▲	aabhay 4 hours ago \| parent [-]
		Hm.. I think because the requirement for approval adds additional arms to the state machine. And the approval step is a message you send to the server that you don't want passed straight to the agent so it doesn't follow the rest of our pattern. Stupid, not good, unsatisfying reasons I agree!