Why My Love for Cursor AI Clashed with JetBrains and How a Plugin Could Fix It
June 19, 2025Why My AI Development Kept Stalling at 25 Tool Calls and How I Fixed It
June 19, 2025
I’ve used Neovim for years, so I was bummed when I couldn’t use Cursor IDE’s AI chat without switching editors. But after some digging, I found a way to keep my Neovim setup and still get Cursor’s features. Here’s my step-by-step guide to making it work.
Why This Matters for Neovim Fans
Neovim is my go-to for speed and customization. But when it comes to understanding large codebases, Cursor’s AI chat is a lifesaver.
Switching to VSCode just for Cursor felt like too much. I didn’t want to abandon my custom Lua setup. And I knew other developers felt the same—we’d all pay for a good integration.
The Simple Fix: VSCode Neovim Extension
Enter the ‘VSCode Neovim’ extension by asvetliakov. It lets you run Neovim right inside Cursor. Best part? My keybindings and plugins worked right away. The real trick was tweaking my Lua config to avoid crashes.
Getting It Running: Your Setup Guide
- Grab the extension: Head to Cursor’s extensions and install ‘VSCode Neovim’. This links Neovim to Cursor’s environment.
- Fix your Lua config: Replace
vim.cmd(...)withpcall(vim.cmd, ...)to catch errors. For example:
Changevim.cmd("command")→pcall(vim.cmd, "command").
This saved me from random crashes. - Use Cursor’s AI to help: Seriously handy—paste your config into Cursor’s chat and ask: “Make this Lua safe with pcall?” It did most of my heavy lifting.
When Things Get Sticky: Quick Fixes
Most of my setup worked, but a few keybindings—like gc for commenting—needed extra attention. I fixed them by checking the extension settings and testing one by one.
Even with these tweaks, this setup has made me way more productive. Fingers crossed for an official plugin someday!
