thanks for that 
I think copilot is quite a bit more than ‘quick edits’, it does these days have plans/todos etc.
but certainly, my experience is long session, more involved tasks even with ‘plans’ are where it starts to struggle. the context window is the main issue.
that said, a useful way to understand where co-pilot scope ends, and claude starts.
interesting, it’ll probably suit by general dev strategy then, as Ive always been a dev that evolves code - every bug/issues or feature request is a opportunity for improvement for my code 
absolutely, even with copilot, time investment into prompts is the big investment 
its the bit I have to be careful, as sometimes Ive spent longer trying to get copilot to code something, than it would take me to do by hand, and get a better job.
Im still finding it a bit of a struggle to find this balance.
yeah, Im slightly concerned for some of the larger projects I work on, but we will see.
that said, I don’t need AI to do my coding, I love coding by hand…
hopefully, I can juggle tasks , so that I do the AI bits when I have tokens/time on copilot/claude.
and, I suspect Claude Pro will take over a bit of copilot work, so free some tokens up there.
guess, my next task is to setup Claude 
thanks again, very insightful.