Cursor
A VS Code-based editor with deep AI integration: chat, multi-file edits, codebase-aware completions, and agent mode.
Visit CursorExternal link — opens cursor.com in a new tab. Cursor is a third-party product; we are not affiliated with it.
Link checked 19 September 2026: this site responded and still names the product.
About Cursor
What it is
Cursor is a code editor with an AI assistant built into it rather than bolted on. It is a fork of VS Code, so your extensions, keybindings and themes mostly carry over. You can ask it questions about the open file, have it edit across several files at once, or describe a change and review what it proposes as a diff before accepting.
Why it's different
The useful part is that it reads your actual codebase, not just the file in front of you, so it suggests changes that match how the rest of the project is written. That is also its risk: it is confident enough that accepting a multi-file edit without reading it is easy, and doing that a few times produces a codebase nobody understands. It is a full editor, so switching means moving your whole setup, which is a real cost if you are happy where you are.
How people use it
Working in an unfamiliar codebase, where asking "where does this get called" beats grepping. Refactors that touch many files at once. Writing tests for code that already exists. The people who get the most out of it treat every suggestion as a draft from a fast colleague who has not read the ticket, and review the diff properly.
Step by step
- Open the whole repository rather than a single file, because its advantage over a plain assistant is seeing the rest of your code.
- Use the inline edit shortcut on a selection for small changes, and the chat panel only when the change spans files. Mixing them up is why people find it slow.
- Add a rules file describing your conventions once. Without it you will correct the same style mistakes in every session.
- Reference files explicitly with @ instead of hoping it finds them. Its context is large but not automatic.
- Read every diff before accepting. The failure mode is a confident change to a file you were not thinking about.
- Keep the repository committed and clean before a long agent run, so throwing the result away costs nothing.
Written by the n3os team. We are not affiliated with Cursor.
This listing was written from public information, without Cursor’s involvement. If you own it and something here is wrong — or you would rather not be listed at all — email us and we will correct or remove it.
Get the ones worth knowing about
We write one of these for every tool worth the trouble. Get the new ones, plus what we have found genuinely useful lately.
Your address goes to Buttondown, who send the emails on our behalf. One click unsubscribes, and the list is never sold or shared.