Look first
I want a coding agent to understand the part of a project it is about to change. That usually means reading the surrounding code and checking how the behaviour is used before starting an edit.
For a small fix, this can be quick. For something that touches several parts of the app, a short plan helps me see whether we agree about the problem.
Give each task a shape
A question about the code should end with an explanation. A repair should end with a change and a check that it works. Keeping those expectations clear helps avoid the familiar situation where a simple question turns into an unexpected rewrite.
I also try to keep changes small enough to read. If I cannot explain why a file changed, I need to go back and understand it before moving on.
Break up the long jobs
When a task sprawls, I write down what has been found and divide the remaining work. It takes a little organisation, but it is easier than trying to remember every decision in one enormous conversation.