vim-ai VS cursor

I’ve been happy with vim-ai plugin: https://github.com/madox2/vim-ai

I use https://github.com/aduros/ai.vim. But my use case is mostly for generating stub code documentation and improving my writing so it might not apply for your use case. I also have my eye on https://github.com/madox2/vim-ai but I really like the workflow of ai.vim.

I would also like to announce a Community Wiki and invite you all to contribute. You might find useful especially a collection of prompts that can be used (not only) with the vim-ai plugin, or custom commands section that contains commands extending basic functionality such as suggesting a git commit message :GitCommitMessage.

I am working on integrating OpenAI and ChatGPT into Vim: https://github.com/madox2/vim-ai

vim-ai - 70, generate + refactor, again, offers the cursor.so functionality but in limited, will just replace all your selected text fashion.

You might find useful vim-ai plugin: https://github.com/madox2/vim-ai

Cursor is a fork of VS Code with AI woven into its core. Its agent mode accepts high-level goals, generates and edits files, runs code, and iterates until it succeeds. It supports multi-line edits, smart rewrites and targeted command execution, and allows you to choose between models from OpenAI, Anthropic and Gemini. Cursor also provides background agents and unlimited completions on higher plans.

In early 2025, I tried to adopt Cursor IDE (https://cursor.com/) for my workflow. It's built on top of VS Code. The disadvantage of working in an unfamiliar IDE outweighed all the benefits I gained from Cursor. I'm a big fan of JetBrains products and have been using IntelliJ IDEA for a decade. I tried using both IDEs—IntelliJ IDEA for regular work and Cursor for delegating tasks to the LLM—but this approach led to constant context switching and loss of focus. Eventually, I stopped using Cursor entirely.

BugBot is deeply integrated with the Cursor IDE. When it flags an issue, you can jump directly to the problematic code in your editor and apply the suggested fix with one click. The tight IDE integration makes the review-fix-verify cycle extremely fast.

This is different from having Cursor write Terraform or Pulumi. Those tools let you define infrastructure explicitly, which means Cursor would need to generate proper Terraform configurations, understand AWS resource dependencies, and manage state correctly. AI-generated infrastructure code risks hallucinations that create security vulnerabilities, resource misconfigurations, and version conflicts - meaning you need to carefully review thousands of lines of generated IaC before deploying.

Keep a reusable prompt structure : Build templates for feature development, bug fixes, refactoring, testing, and documentation. If you’re using Cursor, keep them inside your .cursor folder for quick access. The same structure can be shared with your team so everyone works with the same clarity.

Cursor is my IDE of choice.

That’s where automation changes the game. By pairing Cursor, an AI-powered coding assistant, with Requestly's local-first API testing and mocking platform, you can offload the grunt work of writing tests to AI while keeping execution secure and reproducible on your own system. In this article, we’ll walk through how to set up Cursor with Requestly, generate test cases automatically, and run them end-to-end so that you can focus less on boilerplate and more on shipping features.

Cursor

AI tools like GitHub Copilot, Cursor, and ChatGPT excel at the syntax-heavy, pattern-recognition tasks that tutorials teach. Need a React component? AI can generate it. Need to implement a common pattern? AI knows dozens of approaches.