> That, by itself, would obliterate the entire value of Windsurf or Cursor or whatever.
Have used Cursor and I know that there is quite a bit of value between the model and the chat input box and it will be similar to Claude Code or Codex, it's what makes this agentic, it's just accessed through a different interface. So from that perspective, Cursor makes sense for folks that are already in the VSCode environment.
On the contrary, I'm already in the VSCode environment and I would hate to have to switch to Cursor. Doesn't matter that it is a fork, I don't want a fork for every extension of my workflow. I used Cline and now Claude code integrated to VSCode, and I don't think I'm missing much by not switching to Cursor.
I symlinked my vscode settings into the cursor config directory and the transition was strictly additive; everything worked exactly the same as before, with two exceptions so far: a .NET extension wasn't supported, and Cursor recently forced a switch to their own version of Pyright (but that seemed like an improvement once the type checker diagnostics were tamed a little).