I have observed that many devs in companies are no t using Background coding agents available in either github copilot or cursor, they prefer IN-IDE agent even though the company is providing them with background agents.
I can think of 2 reasons:
1. People don't want to experiment, as background agents seems to be something people cannot control
2. People are doubtful that the agent will be able to complete the task properly.
what do you say?
Otherwise you'd always have to context switch, consider which git state it's actually working from, etc. - rather than just letting the code directly before you change in your IDE.
It's significantly lower cognitive load and has a higher success rate, in my experience.
But, of course: Highly depends on the software being written and the general code infrastructure.