I use normal VIM.

I let the AI implement features on its own, then look at the commit diffs and then use VIM to finetune them.

I wrote my own tool for it. But I guess it is similar to cursor, aider and many other tools that do this. Also what Microsoft offers via the AI "edit" tool I have seen in GitHub codespaces. Maybe that is part of VScode?

The trick is to have a terrible baseline

The past month or so I've been largely using Claude Code (similar to aider, which I haven't used in 6+ months, and OpenAI Codex I gather), from the CLI, for the "vibe coding" portion, and then hop into vim for regular coding when I need to "take the stick". I don't have any AI tools integrated into vim (though I do have LSP, etc). This method has been pretty effective, though I would like to have some AI built into the editor as well, my experiences with Cursor and Zed haven't been as rewarding as I'd like so I've iterated towards my current Claude Code. My first serious project, a fastapi-based replacement for an ancient Ruby on Rails project is just in "dev test" mode and going out to production probably in 2.5 weeks.