LEMON AGENT Interactive example · from Start here: Choose a safe first task
The first task
First real session. I have an hour, a project I care about, and I want to come out of this trusting the agent more, not less.
Which is the best first task for a new agent user?
Done. One file changed, the build passes, and here is the diff: the old headline out, your new one in. Nothing else touched.
I can read the whole change in ten seconds, and undoing it would be one step. Next time I’ll hand over something bigger.
The scope is narrow, the change is reversible, and both the build and the diff give you something concrete to inspect.
I updated 43 files: newer syntax, two library upgrades, some renamed components, and formatting cleanup along the way.
The site looks different and I can’t tell which of the 43 files mattered. If something broke, I wouldn’t know where to start looking.
The agent must invent the scope and the taste standard. “Anything else” also gives a small task permission to spread everywhere.
That touches your live accounts. If a step goes wrong, real users are locked out immediately, and there is no simple undo. I’d save this until we have a recovery plan.
Right. That one stays with me until I know how we’d recover.
It is concrete, but the cost of a mistake is too high for a first session. Start where recovery is cheap. AF-09