LEMON AGENT Interactive example · from Start here: From answers to actions
The first request
Connected to your project. I can read the files, edit them, and run commands like the build. What would you like to do?
Which request makes good use of an agent without giving away the important decisions?
Done. I scaffolded a new app with a landing page, a pricing page, and a blog, picked a color scheme, and rewrote your homepage copy to match.
Wait. This doesn’t look like my site anymore. Which of these decisions were mine to make?
This delegates the product decisions as well as the typing. There is no shared picture of done, so a confident result can still be the wrong product.
It’s a template site with three pages. The homepage text lives in one file, the styles in another, and `npm run build` checks that everything still compiles. Two things stood out: one image is oversized, and a link on the About page is broken. I haven’t changed anything.
Now I can see two small, safe tasks worth trying, and I know how to check them.
This uses the agent’s access to the project while keeping the first move read-only. You get orientation before authorizing change.
In general: HTML holds the content, CSS controls the appearance, and JavaScript adds behavior. Want me to look at how your project does these things specifically?
Good explanation, and I could have gotten it from any chat. I still haven’t learned anything about my own site.
That is a useful chat question, but it does not use the agent’s ability to inspect your actual project.