Is CodeCompanion.nvim worth it for Neovim power users?

If Neovim is your editor, yes — it is the broadest way to get chat, inline edits and CLI agents into buffers. The ACP list covers Claude Code, Codex, Gemini CLI, Copilot CLI, Cursor CLI, OpenCode, Kimi CLI, Kiro, Goose, Cline, Auggie, Cagent, Kilo Code and Mistral Vibe, and each interaction can use a different adapter. The trade is Lua configuration and your own API keys.

Does CodeCompanion.nvim work with Claude Code and Codex?

Yes, both via ACP adapters that run in the chat buffer. The ACP agent runs its own tools, so CodeCompanion's @{files} and other tools are not offered in that mode, and each agent must be installed and authenticated first. ACP adapters also do not work for inline, cmd or background interactions — those need an HTTP adapter.

How does CodeCompanion.nvim compare to GitHub Copilot Chat?

The project describes itself as Copilot Chat meets Zed AI, in Neovim. Copilot is the plugin's default adapter and reads the token copilot.vim or copilot.lua already saved, so a Copilot plan including Free or Student works with no extra setup. Unlike Copilot Chat, CodeCompanion lets each interaction point at Anthropic, OpenAI, Gemini, Ollama or an ACP agent.

What are CodeCompanion.nvim's biggest limitations?

It is Neovim-only, and the default adapter is GitHub Copilot, which is useless without a Copilot plan. The openai_compatible endpoint has no preset, so you extend it with your own URL. ACP agents work only in the chat buffer and don't get CodeCompanion's own tools, and the docs warn that small local models are slower and weaker at tool calling.

Can CodeCompanion.nvim run models locally?

Yes. The ollama adapter connects to http://localhost:11434, or OLLAMA_HOST if set, and openai_compatible covers a self-hosted llama.cpp or vLLM server. The docs caution that small local models are slower and weaker at tool calling than hosted ones, so @{agent} tasks on Ollama are less reliable.

How long does CodeCompanion.nvim take to set up?

Fastest path is the copilot adapter, which needs only a Copilot plan and a signed-in copilot.vim or copilot.lua. Using a provider like Anthropic means setting interactions.chat.adapter and interactions.inline.adapter in your Lua setup with a key in the environment. Expect longer if you write a custom openai_compatible URL or define a CLI agent.

Can CodeCompanion.nvim replace a separate AI terminal?

Largely, if the agent speaks ACP — Claude Code, Codex, Gemini CLI, Copilot CLI, Cursor CLI, OpenCode, Goose, Cline, Kimi CLI, Kiro, Auggie, Cagent, Kilo Code and Mistral Vibe all run under a chat buffer. If you prefer the agent's own interface, the CLI interaction runs it in a terminal buffer while CodeCompanion sends prompts and buffer context.

Is CodeCompanion.nvim good for reviewing agent-generated code?

Yes. The code review flow lets you comment on an agent's changes and accept or revert them before they land in your codebase, so agent output doesn't arrive unreviewed. Combined with ACP agents running their own tools in a chat buffer, you get diffs you can walk hunk by hunk without leaving Neovim.

Is Codecompanion.Nvim still active in 2026?

Codecompanion.Nvim is active in 2026 but worth monitoring — liveness 68/100. Its weakest signal is how little the vendor publishes (no docs, changelog or pricing detail).

Codecompanion.Nvim is live · free · last verified 14 Nov 2026 · viability monitor

Code & Development

Codecompanion.Nvim

Q: Is CodeCompanion.nvim free?

The plugin is released under Apache-2.0 and there is no charge for it. What you pay for is model access: most HTTP adapters read a key from an environment variable like ANTHROPIC_API_KEY or OPENAI_API_KEY and the provider bills you, while Ollama runs locally and an ACP agent can bill against a subscription such as Claude Pro.

CodeCompanion.nvim brings LLM chat, inline edits and CLI agents like Claude Code and Codex into Neovim buffers.

68/100MonitorFreeFree

If Neovim is where you actually work, this is the most complete way to get chat, inline edits and CLI agents into buffers without a second window. ACP coverage is the reason to install: Claude Code, Codex, Gemini CLI, Kimi CLI and Kiro all run under a chat buffer, and agents can lean on a subscription you already hold instead of a fresh API meter. The catch: ACP agents run their own tools, so inline and chat flows want an HTTP adapter, and you'll write Lua to wire it all up.

Verdict generated Oct 26, 2026

Verified 4h ago · liveness 68/100 · cite: rightaichoice.com/tools/codecompanion-nvim

Best for

Neovim users who want LLM chat, inline edits and code review without leaving the editor
Developers already paying for Claude Code, Codex or Gemini CLI who want it driven from a chat buffer
Teams needing provider freedom across Anthropic, OpenAI, Gemini, Kimi and local Ollama
Power users comfortable writing Lua adapters, prompts and workflows

Not ideal for

Developers who work primarily in VS Code, Cursor or JetBrains IDEs
Vim beginners who do not want to write Lua configuration by hand
Users who want a managed assistant with bundled billing and no API key handling

Visit Website

AdvancedExpect 15-30 minutes if you already have a key or Copilot sign-in: install the plugin, then set the chat and inline adapters in your Lua setup. Add roughly an hour to write a custom openai_compatible URL, a CLI agent definition, or your own slash commands and prompts.PluginNo public APIVerified 4h ago

Pricing

Free

FreeFree tier3 hidden costs

Learning curve

Advanced

Expect 15-30 minutes if you already have a key or Copilot sign-in: install the plugin, then set the chat and inline adapters in your Lua setup. Add roughly an hour to write a custom openai_compatible URL, a CLI agent definition, or your own slash commands and prompts.

Runs on

Plugin

No public API · 15 integrations

Who it's for

Neovim developer already on a Claude Code subscriptionEngineer at a company where source cannot leave the networkTeam lead reviewing agent-generated changes

Live sentiment

Is Codecompanion.Nvim actually worth it?

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

Run a free scan

3 free scans · no card needed

Skip it if

Skip CodeCompanion.nvim if you work in VS Code, Cursor or JetBrains and want an assistant that ships with its own settings UI, or if you're not prepared to write Lua for adapters and keymaps.

Skip-it-if note generated Oct 26, 2026

The 30-second take

Biggest gripe

The plugin is free, but every API adapter bills through your provider account — heavy chat and inline use on Anthropic or OpenAI shows up on their invoice, not CodeCompanion's.

Price reality

CodeCompanion itself is an Apache-2.0 plugin, so the real cost is your model bill. A solo Neovim dev on Ollama or Copilot Free/Student pays nothing for inference; a team routing inline edits through Anthropic or OpenAI pays per token on those accounts. Against a bundled copilot subscription the plugin wins on provider freedom and loses on having one predictable line item.

Generated Oct 26, 2026

In short

Codecompanion.Nvim — CodeCompanion.nvim brings LLM chat, inline edits and CLI agents like Claude Code and Codex into Neovim buffers. Best for Neovim users who want LLM chat, inline edits and code review without leaving the editor, Developers already paying for Claude Code, Codex or Gemini CLI who want it driven from a chat buffer, Teams needing provider freedom across Anthropic, OpenAI, Gemini, Kimi and local Ollama. Free to use.

Compared withvs Bito

Claim this listing

What is Codecompanion.Nvim?

FreeAdvancedNo APIPlugin

CodeCompanion.nvim is a free, Apache-2.0 Neovim plugin for coding with LLMs and agents without leaving the editor. It is built around interactions: a chat buffer for talking to a model or an agent, an inline interaction that writes the model's answer straight into your buffer, and a CLI interaction that runs an agent's own terminal interface beside your code. An adapter connects each interaction to a provider and sets its model and parameters, and each interaction or prompt-library item can use a different adapter. HTTP adapters ship for Anthropic, DeepSeek, Gemini, GitHub Copilot, Hugging Face, Kimi, Mistral, Novita, Ollama, OpenAI, Azure OpenAI, OpenRouter and xAI, plus an openai_compatible route for llama.cpp, vLLM or a company gateway. ACP adapters hand the conversation to an agent with its own toolset: Auggie, Cagent, Claude Code, Cline, Codex, Copilot CLI, Cursor CLI, Gemini CLI, Goose, Kilo Code, Kimi CLI, Kiro, Mistral Vibe and OpenCode. Community-contributed adapters cover the long tail. Day to day you get editor context, slash commands, tools and workflows, image and PDF input, several chats open at once, a code review flow for commenting on and accepting or reverting an agent's changes, MCP servers, and a built-in prompt library for tasks such as explaining code or LSP errors. Skills and rules files including CLAUDE.md and .cursor/rules are read directly, and execution is async so long conversations keep Neovim responsive. The audience is developers already fluent in Neovim who want provider freedom and don't mind writing Lua for adapters, prompts and keymaps. Everything is configuration: the docs cover installation and adapter setup, not a GUI settings panel. The project bills itself as Copilot Chat meets Zed AI, in Neovim, which is accurate, because the draw is agent access inside buffers rather than another terminal pane.

Key features

Chat buffer for conversational LLM and agent interaction in Neovim
Inline interaction writes model output straight into the current buffer
CLI interaction runs an agent's own terminal UI inside Neovim
ACP adapters for Claude Code, Codex, Gemini CLI, Copilot CLI, Cursor CLI and OpenCode
ACP adapters for Auggie, Cagent, Cline, Goose, Kilo Code, Kimi CLI, Kiro and Mistral Vibe
HTTP adapters for Anthropic, OpenAI, Azure OpenAI, Gemini, DeepSeek, Mistral and xAI
HTTP adapters for GitHub Copilot, Hugging Face, Novita, Kimi, OpenRouter and Ollama
openai_compatible adapter for llama.cpp, vLLM or a company gateway
Community-contributed and custom Lua adapters
Model Context Protocol (MCP) server support
Editor context to enrich prompts with buffer and cursor state
Slash commands, tools and workflows to shape LLM output
Code review flow to comment on, accept or revert agent changes
Skills and rules files including CLAUDE.md and .cursor/rules
Images and PDFs as model input

Behind the verdict

CodeCompanion solves a problem that terminal-first AI tooling creates for Neovim users: the assistant lives in a different window and loses sight of your buffers. Here the chat, the inline edit and the agent all sit inside the editor you never left. That's the whole pitch, and for a certain kind of developer it's enough. Pick it if you already run Neovim as your main editor and can read Lua without flinching. The ACP side is what tips the decision. Claude Code, Codex, Gemini CLI, Copilot CLI, Cursor CLI and a dozen others plug in as adapters, so agent work happens in a chat buffer rather than a separate pane, and the code-review flow lets you comment on, accept or revert an agent's changes line by line instead of eyeballing a diff in the terminal. Pick it too if provider freedom matters. Switching between Anthropic, OpenAI, Gemini, Kimi, Mistral and a local Ollama box is an adapter swap, and an openai_compatible route covers llama.cpp, vLLM or a company gateway. Teams that can't standardize on one vendor get a real path here rather than a plugin locked to one API. Pass if you work mainly in VS Code, Cursor or JetBrains, where the native assistants already have the editor context wired in. Pass as well if you want a managed assistant with bundled billing and no key handling: CodeCompanion hands you adapters and leaves credentials and configuration to you. Vim beginners who haven't written a keymap will spend their first evening in the docs rather than coding. One caveat we'd flag up front, and it isn't obvious from a feature list: ACP mode means the agent brings its own tools, so editor context like @{files} isn't available while an agent is driving. Inline and background interactions, meanwhile, want an HTTP adapter. So most serious setups run both adapter types

Limitations

CodeCompanion.nvim is a Neovim plugin, so it lives entirely inside the Neovim ecosystem and is configured in Lua.
It is a client: LLM access comes through adapters that connect to providers (Anthropic, OpenAI, Azure OpenAI, Gemini, DeepSeek, Mistral, xAI, GitHub Copilot, Hugging Face, Novita, Kimi, OpenRouter, Ollama) or through ACP/CLI agents like Claude Code and Codex, so any model must be supplied by those external services rather than by the plugin itself.

as of 2026-10-26

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.

Is Codecompanion.Nvim still active?

Codecompanion.Nvim is live · free · last verified 14 Nov 2026 · viability monitor.

Viability score

68/100

Monitor

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

Recent activity

not measured

Traction

100

Site health

User sentiment

What the vendor publishes

Last calculated: November 2026

How we score →

What do users say about Codecompanion.Nvim?

What people actually say about Codecompanion.Nvim — is it worth it?

Our community sentiment research written Jul 6, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.

How we verified this

Every listed fact about Codecompanion.Nvim — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 14 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.

Verification history

We have re-verified Codecompanion.Nvim 12 times since Jul 4, 2026. 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.

Nov 14, 2026 — changed pricing tiers, our verdict, summary, description, features
Nov 8, 2026 — changed pricing page
Nov 4, 2026 — changed pricing tiers, who should skip it, description, features, summary, our verdict
Nov 1, 2026 — changed limitations, models
Oct 26, 2026 — changed switching out, limitations, hidden costs, description, use cases, who should skip it, setup time, pricing fit, our verdict, pricing tiers, features, switching in, SSL certificate
Oct 23, 2026 — changed pricing page

Showing the 6 most recent of 12 verification passes.

Free to cite with attribution — this page re-verifies continuously.

Claim this listing

How much does Codecompanion.Nvim cost in 2026?

Codecompanion.Nvim: Free to use. Pricing last verified 14 Nov 2026.

Plans compared

Every published Codecompanion.Nvim tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.

Codecompanion.Nvim pricing plans compared
Plan	Price	Billing	Who it's for
Free	Free	—	Any Neovim user with a provider API key, a Copilot plan (including Free or Student), a local Ollama server, or an ACP agent already installed and signed in.Adds: Starting tier: the plugin itself is Apache-2.0 and costs nothing; you supply the model access, whether a provider key, Copilot sign-in, local Ollama or an ACP agent subscription.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Plan

Annual total

Free

Over 12 months

Effective monthly

—

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

The plugin is free, but every API adapter bills through your provider account — heavy chat and inline use on Anthropic or OpenAI shows up on their invoice, not CodeCompanion's.
Running an ACP agent like Claude Code can bill against an existing subscription such as Claude Pro, so agentic sessions draw down that plan's limits alongside whatever else you use it for.
Agentic tasks on local Ollama models avoid per-request fees but cost you time: the docs warn small local models are slower and weaker at tool calling than hosted ones.

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.

Hidden-cost and price-fit notes generated Oct 26, 2026

Has Codecompanion.Nvim's pricing changed?

No plan price for Codecompanion.Nvim has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.

Who should pick Codecompanion.Nvim?

Pick Codecompanion.Nvim if you are Neovim users who want LLM chat, inline edits and code review without leaving the editor, Developers already paying for Claude Code, Codex or Gemini CLI who want it driven from a chat buffer, Teams needing provider freedom across Anthropic, OpenAI, Gemini, Kimi and local Ollama, Power users comfortable writing Lua adapters, prompts and workflows.

Look elsewhere if you are Developers who work primarily in VS Code, Cursor or JetBrains IDEs, Vim beginners who do not want to write Lua configuration by hand, Users who want a managed assistant with bundled billing and no API key handling, Anyone expecting a GUI settings panel or one-click installer for their AI assistant.

Skip it if Skip CodeCompanion.nvim if you work in VS Code, Cursor or JetBrains and want an assistant that ships with its own settings UI, or if you're not prepared to write Lua for adapters and keymaps.

Generated Oct 26, 2026

Real-world workflow fit

Concrete scenarios for the personas Codecompanion.Nvim actually fits — and what changes day-one when you adopt it.

Neovim developer already on a Claude Code subscription

Adds the claude_code ACP adapter, sets chat to use it, and keeps inline on the anthropic HTTP adapter so :CodeCompanion still rewrites buffers in place.

Outcome: Agentic multi-file work and single-buffer edits both happen inside Neovim, with the agent billing against the existing Claude subscription rather than a second API key.

Engineer at a company where source cannot leave the network

Points the ollama adapter at a local server, or extends openai_compatible with the internal gateway URL, and assigns that adapter to chat and inline interactions.

Outcome: Prompts and code stay on company infrastructure while the user keeps chat, inline edits and the prompt library — with the caveat that smaller local models are weaker at tool calling.

Team lead reviewing agent-generated changes

Has an ACP agent produce a patch, then uses the code review flow to comment on individual hunks and accept or revert them before committing.

Outcome: Nothing lands in the codebase unreviewed, and the review happens in the same editor buffer rather than a diff tool or terminal pane.

Workflow scenarios generated Oct 26, 2026

Use cases

Refactor or create code inline, with the model's output written straight into the buffer you're editing.
Chat with a model about your code across multiple simultaneous chat buffers.
Run Claude Code, Codex or Gemini CLI inside a Neovim chat buffer via ACP instead of a separate terminal.
Comment on agent output and accept or revert it before it lands in your codebase.
Feed images and PDFs into a prompt for multimodal context.
Extend prompts with MCP tools, slash commands and editor context.
Guide model behaviour project-wide with CLAUDE.md, .cursor/rules or custom rules files.
Point an interaction at local Ollama or a self-hosted OpenAI-compatible endpoint when code can't leave your machine.

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.

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.

Migrating in

→From Copilot Chat in VS Code: install the plugin and set interactions.chat.adapter = "copilot" — it reuses the token copilot.vim or copilot.lua already saved.
→From a terminal Claude Code / Codex / Gemini CLI session: add the matching ACP adapter and run it in the chat buffer instead of a separate pane.
→From another Neovim AI plugin: map your existing chat and inline keymaps to CodeCompanion's chat and inline interactions and move prompts into the prompt library.

Migrating out

↗To a standalone Claude Code, Codex or Gemini CLI session: the ACP agents run the same tools outside Neovim, so install and authenticate them directly.
↗To VS Code or Cursor: the ACP agents you already use are available there natively, though you lose per-interaction adapter mixing.

Integrations

AnthropicOpenAIAzure OpenAIGoogle GeminiGitHub Copilot DeepSeek MistralOpenRouterxAIHugging FaceNovitaOllama Claude CodeCodexGemini CLI

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

Official Website

What are the best Codecompanion.Nvim alternatives?

The closest alternatives to Codecompanion.Nvim we list are Sourcegraph Cody, CopilotForXcode and Replit's Ghostwriter Chat. Ranked by direct product-type match, not category overlap.

Closest alternatives to Codecompanion.Nvim
Alternative	Pricing	Starts at	Last verified
Sourcegraph Cody	Paid	Pricing not published	—
CopilotForXcode	Freemium	Pricing not published	—
Replit's Ghostwriter Chat	Freemium	Pricing not published	—

Alternatives to Codecompanion.Nvim

View all

Sourcegraph Cody

Sourcegraph Cody brings whole-codebase context to AI coding chat, completions, and agentic batch changes across hundreds of repos.

PaidTry

CopilotForXcode

Copilot for Xcode puts GitHub Copilot, Codeium and ChatGPT suggestions, chat and code edits inside Apple's Xcode editor.

FreemiumTry

Replit's Ghostwriter Chat

Ghostwriter Chat brings file-grounded AI coding chat into Replit's browser IDE, reading your project before it answers.