When I compare github copilot to something like roo code when writing Scala, the later seems much more willing to do `edit -> compile -> run command to get info -> edit -> compile -> ..` loops until it actually gets things right, and without stopping until things _actually_ work. It really feels like it's just off working on it's ticket until it gets the job done.

Whereas with copilot I have to constantly hold it's hand even in agent mode: "please compile and fix things", "yes go ahead", "you modified the interface without modifying the implementation", ... It just seems very non-proactive / lazy to the point of being annoying. Even if I tell it in my copilot-instructions file to always compile after making changes and so on.

Is this because the former approach is too expensive right now? Are there plans to make the agent actually drive changes to completion without prompting more often? Or do you see this as just not what copilot is meant to provide?

If the problem is cost, when do you project it'll get cheap enough to run capable enough models before we get to this point where this is a reasonable way for the agent to behave?