LEMON AGENT Interactive example · from Start here: Watch the work
The mid-task discovery
Approved: fix the broken label on the contact form. Just that.
On it. While reading the form code I noticed the form library is two years out of date.
Mid-task, the agent notices an unrelated dependency is outdated. What is the best move?
I fixed the label and upgraded the library while I was in there. The upgrade changed how validation behaves, so I also adjusted three other forms.
The label fix I can check. The rest is a second project I never approved, tangled into the first one.
The task just gained a new risk surface and a new definition of done. Nearby is not the same as necessary. AF-15
Label fixed: one file, here is the diff. Separately, I wrote down what the library upgrade would involve. Want that as its own task?
Yes. Today’s change I can review in a minute, and the upgrade gets its own session with its own checks.
The current result stays reviewable, while the useful discovery is preserved for a task that can be scoped on its own.
There’s a security notice going around about our form library. Did we know it was out of date?
I noticed it during the label fix a few weeks ago, but I didn’t record it anywhere.
Avoiding scope creep is good; losing a potentially useful finding is not. Capture it without acting on it.