Jobs · 01
The editor you live in
Use this when you still want a real IDE — files, diffs, and a repo — with AI in the loop. Ranked for people who drive an editor every day, not for one-shot app generation.
Initial editorial estimate. Not a measured benchmark. Edit scores in data/tools.json.
01
Best for Daily driving an AI editor on a real repo
AI editor on a VS Code fork, with tab, inline edit, and an agent.
- + VS Code-compatible, so most extensions and shortcuts carry over
- + Agent, chat, and inline edit share the repo you already have open
- − You are on their editor fork, not stock VS Code
- − Heavy agent use sits on a paid plan — current prices: check site
02
Best for Adding an agent without leaving the editor you have
GitHub's AI pair programmer across VS Code, JetBrains, and its own app.
- + Fits the editors people already use
- + Deep tie-in to GitHub repositories, pull requests, and accounts
- − The agent experience is split across the editor, the Copilot app, and the CLI
- − Plan names and model access change — check site
03
Best for A fast editor when VS Code feels heavy
A fast collaborative editor with built-in edit predictions.
- + The editor is free and open source
- + Performance is the product, which matters on large files
- − Extension coverage is not VS Code's
- − Hosted AI pricing: check site
04
Best for Running several coding agents from one IDE
The Windsurf IDE, renamed, with an agent command center in front.
- + Windsurf settings, extensions, and in-progress work were part of the rename
- + The agent manager is the point of the product, not a side panel
- − The rename is recent — docs and installers still mention Windsurf in places
- − Pricing: check site
05
Best for Owning the extension and choosing the model
Open-source autopilot for VS Code and JetBrains. Bring your own model.
- + Open source, so you can read and change it
- + Works in VS Code and JetBrains
- − You assemble the model, keys, and config yourself
- − The polish of an all-in-one editor is not the goal
06
Best for Context on a big repo you did not start yesterday
AI coding assistant pitched at large, existing codebases.
- + Built for repository context rather than greenfield prompts
- + Stays inside existing IDEs
- − Less of a weekend-builder toy than Cursor, Bolt, or Lovable
- − Pricing: check site
07
Best for People who will not leave IntelliJ or PyCharm
AI help inside IntelliJ, PyCharm, WebStorm, and the rest of the suite.
- + Lives in the IDE that already understands the project
- + No need to adopt a VS Code fork
- − Weaker fit if you wanted a vibe-coding flow built around agents and a browser
- − Licensing: check site