alt Hacker News> The only other notable setback was an accidental use of the word "revert" which Codex took literally, and ran git revert on a file where 1-2 hours of progress had been accumulating.
Replies
_flux • yesterday at 5:26 PM
Amazing that these tools don't maintain a replayable log of everything they've done.
Although git revert is not a destructive operation, so it's surprising that it caused any loss of data. Maybe they meant git reset --hard or something like that. Wild if Codec would run that.
➕ show 6 replies
esafak • yesterday at 6:18 PM
Does Codex not let you set command permissions?
Filligree • yesterday at 5:19 PM
Yet another reason to use Jujutsu. And put a `jj status` wrapper in your PS1. ;-)
➕ show 3 replies
If I tell Claude to "revert that last change, it isn't right, try this instead" and Claude hasn't committed recently it will happily `git checkout ...` and blow away all recent changes instead of reverting the "last change".
(Which, it's not wrong or anything -- I did say "revert that change" -- it's just annoying. And telling `CLAUDE.md` to commit more often doesn't work consistently, because Claude is a dummy sometimes).