[iansinnott]

- copilot would only predict after the cursor, whereas Cursor predicts nearby edits, which is quite helpful

- copilot-chat was just a chat sidebar last time I used it, you still had to manually apply any code suggestions. cursor will apply changes for you. It's very helpful to have a diff of what the AI wants to change.

It's been a while since i've used copilot though, so copilot chat might be more advanced then i'm remembering.

edit: formatting

[divan]

Thanks! "Nearby edits" mean edits in the same file or the whole workspace?

I test Copilot Workspace from time to time, it's still far from perfect, but it already can make large-scale codebase changes across multiple files in a repository. Ultimately that's what I want from an AI assistant on my machine - give a prompt and see changes in all repo, not just current file.

[IanCal]

> Thanks! "Nearby edits" mean edits in the same file or the whole workspace?

For the autocomplete, in the same file. So proposing adding more logging when you add a few statements, changing an error check, adding something to the class def or constructor.

They do have a multi-file editing thing called "composer" I think, which I used to make larger changes to an app (e.g. add a new page that lists all the X, and it creates that and the links to it in the other pages).

You might also be interested in aider https://github.com/paul-gauthier/aider for larger changes.

[divan]

Thanks! Yes, Aider is a good attempt. I tried it a couple of times, ran into a number of issues, but should give it another try. Integration with an editor (I use nvim) is crucial though.

[worldsayshi]

> It's been a while since i've used copilot though, so copilot chat might be more advanced then i'm remembering.

Copilot is still surprisingly basic but I've heard rumours that they are working on a version with a lot more features?