Hey Abhinav Sharma here...
One thing that keeps bothering me when using AI coding agents
I’ve been using AI coding agents more seriously lately, not just for small snippets but for actual project work. There’s one thing that keeps bothering me.
When an AI agent edits a file, you only see the final version of that file.
But in reality, that file might have been changed many times:
- maybe the agent rewrote it
- then fixed something
- then adjusted it again
- maybe I tweaked it in between
All of that history is gone. ( now agents do ask for permission to write but not talking about after permission )
At the end, you’re left with one file and a vague feeling that “a lot happened here.”
Why this feels like a problem
If something breaks later, it’s hard to answer simple questions like:
- How many times was this file changed?
- When did it start going wrong?
- Can I go back to an earlier version, not all the way back?
Most of the time, you can’t.
You only have the final result.
This becomes more painful with long agent runs
This is why I integrated a file timeline directly into CrewBench.
For every file, I wanted:
- visibility into how many times it was changed
- access to older versions
- the ability to roll back to a specific change (for example, the 5th edit)
So in CrewBench, each file now has a simple timeline:
- every edit (by you or an AI agent) is recorded
- previous versions are kept
- diffs are visible
- you can roll back to any earlier version
If a file was changed 10 times, all 10 changes are visible, and you can go back to any one of them when needed.
See the CrewBench Issue here
Implementation here
CrewBench UI
This doesn’t replace Git.
It just gives visibility into something Git doesn’t really show well.
Top comments (1)
how's this ?