the repo acts as a source of truth for agents. think memory, data & code. If an agent decides to change any of those, version control allows:

1. to have a human in the loop to approve certain changes 2. rollback changes that end up being incorrect 3. allow reviewing the timeline and history to figure out what changed and how

▲

esafak 3 hours ago | parent | next [-]

2. is false. You can't roll back everything an agent does. If you told it to place a trade in the stock market, for example, you can not undo that. That is what I mean by external state. Everything else is covered by existing version control, is it not? What does this buy over that?

	▲	ozkatz 3 hours ago \| parent [-]
		indeed - this only applies to the filesystem managed by tilde. Existing version control is fine if you're only managing code. For data (Think large parquet files, millions json files, images and videos, etc), git doesn't scale well for that.

▲

bossyTeacher 3 hours ago | parent | prev [-]

Re 2: how do you rollback the (erroneous) action of removing a db table column and the subsequent data loss from the removed column?