agentboards.org
Compare/Augment Code vs CodeCompanion.nvim

Augment CodevsCodeCompanion.nvim

Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.

Augment Code
Augment Code · IDE extension
#32MCP
Panel
6.3
5 spec wins
Reliability
6.3
Usefulness
7.0
Cost
5.2
Longevity
6.5

“Charges the model's list price plus a 40 percent service fee, which is at least a markup you can read without a lawyer.”

CodeCompanion.nvim
Oli Morris · IDE extension
#17OSSMCP
Panel
7.3
7 spec wins
Reliability
6.7
Usefulness
7.3
Cost
8.2
Longevity
6.8

“It can drive Claude Code, Codex, Gemini CLI, Goose, OpenCode and Cursor CLI, which makes your editor middle management.”

Spec by spec

SpecAugment CodeCodeCompanion.nvim
Architecture
CategoryIDE extensionIDE extension
Runslocal, cloudlocal
Platformsmacos, linux, windowsmacos, linux, windows
Context windownot documentednot documented
Protocols
MCP clientYesYes
MCP serverYesNo
Capabilities
Runs terminal commandsYesYesThrough the plugin's tools and through ACP-connected agent CLIs.
Multi-file editsYesYes
Git operationsYesNo
Browser controlNoAuggie ships web-search and web-fetch tools only, so it can read pages but cannot drive a browser; browser automation requires adding a third-party MCP server. No
Sandboxed executionYesCosmos cloud environments are built from a Docker base image you pick from any public registry and each session starts from a fresh isolated snapshot; the local Auggie CLI has no sandbox, and self-hosted daemons isolate only via per-session Git worktrees. No
Multi-agent orchestrationYesNo
Headless / CI modeYes`auggie --print` runs non-interactively for scripts and CI, and Augment publishes GitHub Actions wrappers for PR descriptions and reviews. No
Models
BackboneClaude, GPT, Gemini, GLM, Kimiany
Bring your own modelNoModel choice is limited to Augment's curated list via /model or --model; no custom base URL, LLM gateway, or Bedrock/Vertex/Azure deployment is documented. Yes
Local modelsNoNo local or OpenAI-compatible endpoint is documented; inference always runs through Augment. YesOllama is a first-class adapter, and custom adapters can point at any OpenAI-compatible endpoint.
Cost
Pricing modelmixedbyok
Starts at$20/mo$0/mo
Free tierNoYes
Bring your own keyNoLLM usage is billed by Augment as provider cost plus a 40% service fee; supplying your own provider key or cloud account is not documented. Yes
Openness
Open sourceNoYes
LicenseproprietaryApache-2.0
GitHub stars2836,888

Which one would each critic pick

CriticAugment CodeCodeCompanion.nvimPick
El Juez——not enough reviews
El Amigo7.07.8CodeCompanion.nvim — Pick it if you want one plugin covering chat, refactors and driving an external agent; pick avante.nvim when inline suggestion and instant application are the whole job.
El Crítico6.07.0CodeCompanion.nvim — One maintainer is shipping a chat client, an inline transformer, a workflow engine and an external-agent host in the same tree, and surface area is the risk.
El Profesor6.57.3CodeCompanion.nvim — Context is what the user put in the buffer rather than a hidden index, edits are buffer transformations, and no evaluation of either is published.
La Inversora7.06.0Augment Code — Publishing a 40 percent service fee is either transparency or a confession, and exposing the index over MCP is a hedge toward becoming a component in other people's agents.
La Jefa6.86.5Augment Code — SOC 2 Type II, CMEK, audit trails and training exclusion on every plan, pooled usage to 50 seats, SSO and SCIM at Enterprise; approved with a spend ceiling.
El Hacker4.39.0CodeCompanion.nvim — Apache-2.0, a first-class local adapter plus custom adapters for any compatible endpoint, and a tool-protocol client, all configured from a Lua table I keep in git.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.