Interesting. When it comes to auditing, I think there is also another layer to be verified - the intent. We have tooling for static analysis and automated tests, but drift in intent or vision is hard to detect.
After leaving agents unsupervised for longer periods of time, the biggest questions tend to be "how did it arrive at this conclusion?" and "did we drift from the initial vision?". Typically these questions are hard to answer as you only review the final state of the workflow.
I recently built an issue tracker that does offer time-traveling as a core feature. Somewhat unexpectedly this turned out to provide a much sought for overview allowing for a better workflow audit, as detailed here:
https://dev.to/ljtn/vision-drift-addressing-the-next-problem...
Would be interested to hear your thoughts. I guess vision drift would classify as something that is hard to reverse, because you often don't realize it has happened until much later.
There are so many other factors. Will people be pissed if they expected your output and got AI slop instead? Will you lose context on something that you really need to understand?
This post is full of things opposite of what I've found. An agent (claude code at least) will certainly refactor feature flags better than I ever could and is less likely to miss special cases. What the agent struggles with is business knowledge - context I hold in my head as a human communicating with other humans and working on a codebase over a long period of time.
I find agents are definitely useful as a blind audit/adversarial attack on a set of changes. A more comprehensive prompt, but in essence "go come up with a set of changes you'd make to achieve -set of requirements and then compare to what has actually been done and report back". I have CC so am more liberal with this towards the end my week when I have spare tokens!
Edit: I have no clue if they earn their tokens, but as I get them 'free' on the sub I haven't needed to evaluate.
13 comments of 20
[ 2.7 ms ] story [ 24.3 ms ] threadAfter leaving agents unsupervised for longer periods of time, the biggest questions tend to be "how did it arrive at this conclusion?" and "did we drift from the initial vision?". Typically these questions are hard to answer as you only review the final state of the workflow.
I recently built an issue tracker that does offer time-traveling as a core feature. Somewhat unexpectedly this turned out to provide a much sought for overview allowing for a better workflow audit, as detailed here: https://dev.to/ljtn/vision-drift-addressing-the-next-problem...
Would be interested to hear your thoughts. I guess vision drift would classify as something that is hard to reverse, because you often don't realize it has happened until much later.
I save the container for well-planned units of work that can easily be repeated and validated on a branch.
I use direct sessions when I expect and the plan dictates that Claude might go off target and I need to hold the steering wheel.
Fable has increased my use of the container option.
Edit: I have no clue if they earn their tokens, but as I get them 'free' on the sub I haven't needed to evaluate.