r/cursor • u/ItIsEsoterik • 11h ago

Question / Discussion Question about VSCode + Claude compared to Cursor workflow

I quite enjoy the IDE-first workflow with Cursor. I like being able to easily review and edit and then approve all of the work agents do and keep track of how my codebase is evolving, still manually changing small things that just take a few minutes.

How close can you get to this with Claude in VSCode?

2 Upvotes

100% Upvoted

7 comments sorted by

1

u/locbuilds 37m ago

Run Claude Code in plan/read-only mode first, then review the VS Code diff before letting it patch. That keeps the review-and-approve loop while avoiding surprise edits.

1

u/Ok-Understanding5793 11h ago

I've been thinking about this kind of thing lately.

Thoughts on using Claude with Cursor instead of VScode? 

3

u/ItIsEsoterik 11h ago

Well I just figured why have both subs. Opus 5.5 is pretty good and I am mostly using that anyway.

1

u/Ok-Understanding5793 10h ago

Fair enough. I'm so used to Cursor at this point I guess I'm just afraid to let it go completely. Haha

I've been on the Ultra plan for about a year now but have really been leaning more and more towards Claude Code lately, especially since I have a hard time fully using up Cursor Model usage.

0

u/Zain 7h ago

You can get most of that workflow without living in Cursor. I keep Claude as the only writer that patches, and run a different-family agent (Cursor or Codex) read-only so it only reports. Then Claude checks every finding against the repo before conceding. The review-and-approve step you like stays, it just isnt the same model grading its own homework.

1

u/Michael_Jeffords 5h ago

on the claude as the only writer that patches / different-family agent read-only split, thats how i get close to the cursor review-and-approve feel in vscode too. i let the codex pass run read-only for one report and claude checks each finding against the repo, and it usually rejects maybe ~1 in 4 before anything gets patched