Codecompanion.Nvim
CodeCompanion.nvim brings AI coding, chat, agents and MCP into Neovim.
For Neovim users who want AI chat, inline edits, and ACP agents in one free plugin, CodeCompanion.nvim is the one to install. The provider list and ACP coverage are unusually broad for an open-source plugin, and the approve/reject code review flow makes agent output safer to accept. The cost is real: expect to spend an evening in Lua config before it feels right.
Verified 6d ago · liveness 70/100 · cite: rightaichoice.com/tools/codecompanion-nvim
- Neovim users who want AI chat and inline edits without leaving the editor
- Developers running CLI agents like Claude Code or Gemini CLI inside Neovim
- Teams that need provider freedom across Anthropic, OpenAI, Gemini, and local Ollama models
- Power users who want custom Lua adapters, prompts, and multi-step workflows
- Developers who work primarily in VS Code, Cursor, or JetBrains IDEs
- Vim beginners uncomfortable writing Lua configuration
- Anyone wanting a managed, no-setup AI assistant with built-in billing
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip CodeCompanion.nvim if you are not comfortable with Neovim's keybindings and Lua configuration, or if you prefer a managed, no-setup AI coding tool without the need to manage API keys.
You need to provide your own API keys for most LLM providers, which can incur usage costs depending on the provider's pricing.
CodeCompanion.nvim is free and open-source, making it ideal for individual developers and small teams who want maximum control without recurring subscription fees. Compared to managed tools like GitHub Copilot ($10/mo) or Cursor ($20/mo), you save money but assume the cost of API usage and configuration effort.
In short
Codecompanion.Nvim — CodeCompanion.nvim brings AI coding, chat, agents and MCP into Neovim. Best for Neovim users who want AI chat and inline edits without leaving the editor, Developers running CLI agents like Claude Code or Gemini CLI inside Neovim, Teams that need provider freedom across Anthropic, OpenAI, Gemini, and local Ollama models. Free to use.
What's new in Codecompanion.Nvim
Checked 4 days agoAcross the latest 1 update: 1 feature update.
What people actually say about Codecompanion.Nvim — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
47 mentions across 4 sources (Hacker News, YouTube, Bluesky, GitHub) · researched Jul 6, 2026.
Average across the 4 sources that answered — each source counts once, not each post.
- +Native Neovim experience with Vim keybindings and feel.
- +Supports multiple LLM providers: OpenAI, Anthropic, Ollama, GitHub Copilot, etc.
- +Free and open-source with no usage limits or subscription.
- +Chat buffer, inline transformations, and ACP agent support.
- +Editor context improves LLM output accuracy for code tasks.
- −Agentic workflows are limited compared to Cursor or Aider.
- −Memory leak reported in long conversations (still open issue).
- −Anthropic adapter errors with long prompts, breaking some workflows.
- −Requires manual API key setup; not beginner-friendly for newcomers.
- −No native diff view for AI edits; users request better review tools.
- • API usage costs from third-party providers (Anthropic, OpenAI, etc.)
- • Time spent on configuration and troubleshooting
Viability Score
How well maintained and how widely used is Codecompanion.Nvim? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- Chat buffer for conversational LLM interactions inside Neovim
- Inline transformations that write model output directly into your buffer
- Agent Client Protocol (ACP) support for Claude Code, Codex, Gemini CLI and more
- Model Context Protocol (MCP) support for external tools
- Adapters for Anthropic, OpenAI, Gemini, GitHub Copilot, Ollama and others
- Custom Lua adapters to connect any LLM or agent
- Editor Context to enrich prompts with buffer and cursor state
- Slash Commands and a built-in prompt library for LSP errors and explanations
- Rules and skills support including CLAUDE.md and .cursor/rules
- Code review workflow to comment on and approve/reject agent output
- Multiple simultaneous chat buffers
- Image and PDF input for multimodal prompts
- Async execution for fast performance in long conversations
- Local model support via Ollama
- Workflows and tools to chain multi-step agentic tasks
About Codecompanion.Nvim
CodeCompanion.nvim is a free, open-source Neovim plugin that puts LLM chat, inline code transformations, and full agentic coding inside your editor buffer. It's built for people who already live in Neovim and don't want to alt-tab into a browser or a separate GUI app to talk to a model or run an agent. The plugin is provider-agnostic by design. Adapters ship out of the box for Anthropic, DeepSeek, Google Gemini, GitHub Copilot, GitHub Models, Kimi, Mistral, Novita, Ollama, OpenAI, Azure OpenAI, OpenRouter, HuggingFace and xAI, and you can write your own adapter in Lua for any LLM or agent. That means local models through Ollama and frontier APIs from the same chat buffer. Agent support runs through the Agent Client Protocol (ACP), covering agents like Claude Code, Codex, Copilot CLI, Cursor CLI, Gemini CLI, Goose, Augment Code, Cline CLI, Kilo Code, OpenCode, Mistral Vibe, Cagent from Docker, Kimi CLI and Kiro. Beyond chat, it offers an inline interaction that writes model output straight into an existing buffer, Editor Context and Slash Commands to improve prompts, a built-in prompt library for LSP errors and code explanations, rules files like CLAUDE.md and .cursor/rules, tools and workflows, MCP support, image and PDF input, multiple simultaneous chat buffers, and a code review flow where you comment on agent output and approve or reject it. Execution is async, so long conversations don't freeze the editor. Configuration is all Lua, which is both the selling point and the entry fee. Full control over models, hyperparameters, adapters, prompts and UI versus a setup curve that assumes you're comfortable in Neovim. If you want a managed copilot with a one-click install, look elsewhere; if you want provider freedom and agent support inside your terminal editor, this is one of the few options that does it without a subscription.
Behind the Verdict
Pick CodeCompanion.nvim if Neovim is where you actually work and you want AI there rather than in a browser tab. The ACP layer is the reason we keep coming back — you can drive Claude Code, Codex, Gemini CLI, Copilot CLI, Goose, Cursor CLI or Kiro inside the editor, and switch between them without leaving your keybindings. Same story on models: Ollama for local work, Anthropic or OpenAI for heavier tasks, one adapter config away. Where it earns its keep is the unglamorous stuff. Editor Context pulls buffer and cursor state into the prompt so you stop pasting code. Slash Commands and the prompt library cover LSP errors and explanations without writing a prompt from scratch. The code review interaction matters more than it sounds: commenting on agent-written code and approving or rejecting it piecewise is the difference between trusting an agent and nervously diffing afterward. Pass on this if you're new to Vim or you want something that just works after an install command. Setup means adapters, API keys, and Lua that you'll actually have to read. There's no managed account, no billing dashboard — you bring keys and pay providers directly, which is cheaper but is on you to manage. Users who prefer VS Code, Cursor, or JetBrains will get more mileage from tools built natively for those editors. Against the closest alternative, GitHub Copilot in Neovim, CodeCompanion is less turnkey but far more flexible. Copilot gives you completions and chat with near-zero config; CodeCompanion gives you agent orchestration, MCP tools, custom prompts, and any provider you want. Many people run both — Copilot for tab completion, CodeCompanion for everything conversational and agentic. Practical caveats: it's an open-source plugin maintained by Oli Morris with a community adapter
Researching Codecompanion.Nvim? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Codecompanion.Nvim actually fits — and what changes day-one when you adopt it.
Refactoring a legacy codebase
Outcome: Use inline transformations to get AI suggestions directly in the buffer, then apply changes with a single keybinding.
Comparing responses from different LLMs
Outcome: Switch between adapters for Anthropic, OpenAI, and local Ollama to compare outputs without leaving Neovim.
Running Claude Code for a complex task
Outcome: Launch Claude Code via ACP, review its generated code using the code review feature, and approve or reject changes inline.
Use Cases
- Refactor code inline with AI suggestions directly in your buffer.
- Chat with an AI about code issues using multiple conversation buffers.
- Create custom slash commands to automate repetitive coding tasks.
- Integrate with MCP tools to extend AI capabilities with external data.
- Leverage agent protocols to run Claude Code or Cline CLI within Neovim.
- Use rules files like CLAUDE.md to guide AI behavior across projects.
Models Under the Hood
as of 2026-09-23
Limitations
- CodeCompanion.nvim is a Neovim plugin, so it is limited to the Neovim editor ecosystem.
- Users must provide their own API keys for most LLM providers, which may incur costs.
- The plugin does not have built-in rate limiting or context window management; it depends on the underlying model's capabilities.
as of 2026-08-31
Verification history
We have re-verified Codecompanion.Nvim 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Codecompanion.Nvim tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Individual developers who are comfortable with Neovim and want a zero-cost AI coding assistant with full control over providers and agents.
What this tier adds
Starting and only tier: free forever, with full access to all features, no paywalls.
Where the pricing makes sense
The company stage and team size where Codecompanion.Nvim's pricing actually pencils out — and where peers do it cheaper.
CodeCompanion.nvim is free and open-source, making it ideal for individual developers and small teams who want maximum control without recurring subscription fees. Compared to managed tools like GitHub Copilot ($10/mo) or Cursor ($20/mo), you save money but assume the cost of API usage and configuration effort.
Setup time & first value
How long it actually takes to get something useful out of Codecompanion.Nvim — broken out by persona, not the marketing-page minute.
For a Neovim user familiar with Lua, setup is under 30 minutes: install via your plugin manager, configure an adapter with an API key, and start using chat. Beginners may take a few hours to learn the keybindings and configuration.
Switching to or from Codecompanion.Nvim
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From ChatGPT web: Switch to CodeCompanion for in-editor context and multiple LLM providers.
- →From GitHub Copilot in VS Code: Learn Neovim basics, then install CodeCompanion for more flexible provider choices.
- ↗To VS Code with Copilot: If you prefer a GUI editor with less configuration, migrate your workflows to VS Code extensions.
Integrations
Resources & Guides
Tutorials & Learning
Neovim + CodeCompanion
Bruno Adele
IT Man - Bringing Zed AI Experience to Neovim with codecompanion.nvim
IT Man
YouTube returned 6 videos for “Codecompanion.Nvim”, and we withheld 4: 4 did not mention Codecompanion.Nvim. Showing the 2 we can prove are about Codecompanion.Nvim.
Official links
Tools that pair well with Codecompanion.Nvim
Common stack mates teams adopt alongside Codecompanion.Nvim, with the specific reason each pairing earns its keep.
Claude
Claude is Anthropic's AI assistant for long-document analysis, coding, and agentic work in chat and Cowork.
Sourcegraph Cody
Sourcegraph Cody is an AI coding assistant that grounds chat, completions, and agent workflows in your entire multi-repo codebase.
JetBrains AI
JetBrains AI puts agent-driven coding assistance, multi-agent choice, and enterprise governance inside the JetBrains IDE family
Featured Head-to-Head Comparisons
Codecompanion Nvim vs Poolside Ai
Choose CodeCompanion.nvim if you're a Neovim power user who wants a free, flexible plugin that connects to any LLM you already use. Choose Poolside AI if you're in a regulated industry needing air-gapped, auditable AI agents with custom models and enterprise governance. For most solo devs or small teams, CodeCompanion is the practical pick; Poolside is a premium solution for high-consequence environments.
Codecompanion Nvim vs Cognition Ai
If you're a Neovim expert who wants flexible, free AI assistance with multiple LLMs, CodeCompanion.nvim is the clear choice. For enterprise teams needing autonomous, end-to-end engineering work with a money-back guarantee, Cognition's Devin is the only option—but it's not for individuals or small projects.
Codecompanion Nvim vs Bito
CodeCompanion.nvim is the go-to for Neovim die-hards who want a free, flexible AI coding assistant that plugs into multiple LLMs directly. Bito is the winner for engineering teams using modern AI coding agents (Cursor, Claude Code, Codex) across multi-repo projects, offering system-wide context, cross-repo impact analysis, and Slack/Jira integrations that CodeCompanion.nvim cannot match. If you live in Neovim and work solo or on a single repo, choose CodeCompanion.nvim; if you need enterprise-grade architectural analysis and agent orchestration, pick Bito.
Alternatives to Codecompanion.Nvim
View allClaude
Claude is Anthropic's AI assistant for long-document analysis, coding, and agentic work in chat and Cowork.
Sourcegraph Cody
Sourcegraph Cody is an AI coding assistant that grounds chat, completions, and agent workflows in your entire multi-repo codebase.
JetBrains AI
JetBrains AI puts agent-driven coding assistance, multi-agent choice, and enterprise governance inside the JetBrains IDE family
Frequently Asked Questions
Categories
Best-of guides
Used Codecompanion.Nvim? Help shape our editorial sentiment research.