Neocursor brings Cursor's Tab-style next-edit prediction to Neovim

Cursor's Tab feature has a distinct feel: it doesn't just autocomplete what you're typing, it predicts your next edit and lets you jump through your codebase with a single key. Now an independent project called neocursor.nvim aims to bring that same experience to Neovim, without reimplementing any of the underlying model.

The plugin works by bridging to Cursor's existing session and backend. A small sidecar process reads your local Cursor login, speaks the same StreamCpp protocol Cursor's client uses, and streams back edit suggestions plus the next cursor-jump target. The Lua side never touches the network, and your token stays on your machine. That's a deliberate architectural boundary that keeps the plugin lightweight and avoids handling credentials itself.

How it feels

Once installed, you open a file and start typing. Pause for a moment and ghost text appears. Press <Tab> to accept the suggestion and automatically jump to the next predicted edit site. Press <Tab> again to accept that rewrite, and so on. It's a loop that matches Cursor's rhythm: one key does three jobs — accept, jump, accept again.

Dismissal is also tiered, mirroring Cursor's behavior. The first <Esc> clears the pending edit but keeps the jump target; a second dismissal clears the jump target entirely. The plugin also keeps a counter: after 20 dismissals with no accepted suggestion, it stops offering suggestions on passive triggers like entering insert mode or moving to another line. Typing still triggers suggestions, and any acceptance resets the count.

Setup and requirements

The plugin requires Neovim 0.12 or later, and you must be signed into Cursor on the same machine. There are no API keys, no model choices, and no account creation. The README notes that it works on macOS, Linux, and Windows, including portable installs, Flatpak/Snap, and WSL. If Cursor isn't found, there's a troubleshooting section that walks through platform-specific paths and environment quirks.

Installation is straightforward. With lazy.nvim, you'd add the repo and call setup() with no arguments. The README also covers vim.pack setups and coexisting with nvim-cmp or blink.cmp.

The parity scoreboard

The project is explicit about where it stands. The core loop — predict, ghost, tab, jump, chain — is complete and running on Cursor's actual backend. In-progress items are edges, like multi-cursor behavior or certain language-specific refinements. The README includes a parity matrix that lists what's ported and what's still in flight, so you can see exactly what you're getting.

Risks and caveats

The most important caveat: this is an independent, personal-use interoperability project, not affiliated with Anysphere. It uses your own Cursor account and token, but it talks to Cursor's private API, which is undocumented and may change. The README is blunt: using it may not fit Cursor's ToS, and it's between you and Cursor. No Cursor source is redistributed, and the project is MIT licensed.

That means you should expect things to break when Cursor updates. The project's own troubleshooting guide acknowledges this reality and offers debugging tools like :NeocursorDebug and :NeocursorLog to help you diagnose issues and file actionable bug reports.

Why this matters for Neovim users

If you've been envious of Cursor's Tab while staying in Neovim, this is the closest thing yet. It's not a completion engine — it's a different interaction model that makes multi-edit navigation feel fluid. The fact that it rides on Cursor's own backend means the quality is the same as what you'd get in Cursor itself, at the same latency. The tradeoff is a dependency on a private API and the ToS questions that come with it. For developers who already live in Cursor's ecosystem, though, that might be a small price for a genuinely useful workflow addition.