Why do coding agents always try to be over helpful instead of just doing exact task you assigned?
by•
You ask for a quick script addition, and suddenly background logic, helper functions and folder structures are completely rearranged without permission.
It feels less like a coding assistant and more like a coworker who won't stop uninvited cleanups.
How do you lock down your agent workflows so they only touch what you explicitly point to?
3 views
Replies
I usually give agents clear boundaries and let them handle only the requested task. File changes, permissions and background logic should stay untouched unless explicitly approved. A review step before applying major changes also helps prevent unwanted surprises
I usually make the allowed surface explicit: which files it can touch, what it can run, and what counts as done. Then I check the diff before keeping anything. 'Don't refactor' in the prompt helps, but I don't trust that as the only boundary. Are you restricting paths and tools, or mostly reviewing after?