Built-in code editor

A built-in code editor means the tool comes with its own screen for writing and reviewing code, with files, a text editor and usually a terminal, rather than only a chat window or a command line. Some tools build this as a new product and others adapt an existing editor. Cursor is listed with this feature.

If you read and change code yourself, an editor that includes the AI means you can see what it proposes, accept or reject each change and keep working in one place. Without it, you copy code between the assistant and a separate editor. You need this when someone on your team reviews code regularly. If you never look at the code and only describe what you want built, the editor matters less than how easy the tool is to use.

• Ask whether your existing settings, extensions and shortcuts carry over from the editor you use now.
• Test the way changes are shown, such as whether you see each proposed edit side by side before accepting it.
• Check whether you can still use your own editor with the tool if your team prefers it.
• Find out which programming languages and project types work well.