multi-adapter llm abstraction with provider-agnostic chat interface
CodeCompanion abstracts multiple LLM providers (OpenAI, Anthropic, Ollama, DeepSeek, Google Gemini) behind a unified adapter interface, allowing users to swap providers without changing chat logic. The adapter system decouples HTTP-based API communication from interaction handling via a modular architecture where each adapter implements schema negotiation, request/response transformation, and streaming token handling. Users configure adapters per interaction type (chat, inline, cmd, background) independently, enabling different providers for different tasks.
Unique: Uses a modular adapter registry pattern where each provider (OpenAI, Anthropic, Ollama, etc.) is a self-contained Lua module implementing schema negotiation and request transformation, allowing runtime provider swapping without recompiling. Supports both HTTP-based APIs and stateful Agent Client Protocol (ACP) agents in the same abstraction layer.
vs alternatives: More flexible than Copilot (single provider) or LangChain (Python-only); enables Vim users to mix local and cloud LLMs in a single editor session with zero context switching.
conversational chat buffer with context-aware message lifecycle
CodeCompanion provides a dedicated chat buffer (filetype: codecompanion) that manages a full conversation history with context injection via three mechanisms: editor variables (#), slash commands (/), and tool references (@). Messages flow through a lifecycle (creation → context assembly → submission → streaming response → buffer rendering) where context is resolved at submission time, allowing dynamic file/selection changes mid-conversation. The buffer supports multi-turn conversations with role-based message formatting (user/assistant) and maintains state across Neovim sessions via optional persistence.
Unique: Implements a deferred context resolution pattern where # variables, / slash commands, and @ tool references are evaluated at message submission time (not insertion time), enabling dynamic context binding. Chat buffer is a native Neovim buffer with full editing capabilities, allowing users to refine prompts in-place before submission.
vs alternatives: Tighter Vim integration than web-based chat (no context switching); supports agentic workflows (ACP/MCP) natively, unlike basic LLM chat plugins that only handle text generation.
rules system for prompt customization and behavior modification
CodeCompanion provides a rules system that allows users to define custom system prompts and behavior modifications without editing core plugin code. Rules are Lua-based and can be applied globally or per-interaction, enabling fine-grained control over LLM behavior. The system supports rule composition (multiple rules applied in sequence) and conditional rule application based on context (file type, buffer state, etc.).
Unique: Implements a composable Lua-based rules system that allows per-interaction and context-aware prompt customization without modifying core plugin code. Rules can be applied conditionally based on file type, buffer state, or other context.
vs alternatives: More flexible than static system prompts; rules enable dynamic behavior modification based on context and project-specific requirements.
mcp (model context protocol) integration for external tool and knowledge base access
CodeCompanion integrates with the Model Context Protocol (MCP) to expose external tools and knowledge bases to LLMs. MCP servers (e.g., for file systems, databases, APIs) are registered as tool providers, and their capabilities are automatically exposed to the LLM via the tool-calling system. This enables LLMs to access external resources (files, databases, APIs) without CodeCompanion implementing provider-specific logic.
Unique: Implements native MCP support, allowing external tools and knowledge bases to be exposed to LLMs via a standardized protocol. MCP servers are registered as tool providers and automatically integrated into the tool-calling system.
vs alternatives: More extensible than built-in tools; MCP enables integration with arbitrary external resources without CodeCompanion implementing provider-specific logic.
inline assistant for code-adjacent tasks (documentation, comments, type hints)
CodeCompanion provides an inline assistant interaction that generates code-adjacent content (documentation, comments, type hints) without full code generation. This interaction is optimized for smaller, focused tasks that enhance existing code. The inline assistant uses a dedicated prompt template and adapter configuration, enabling different behavior from full code generation.
Unique: Provides a dedicated inline assistant interaction optimized for code-adjacent tasks (documentation, comments, type hints) with a specialized prompt template. Separate from full code generation, enabling different behavior and performance characteristics.
vs alternatives: More focused than general code generation; optimized for smaller, documentation-focused tasks without the overhead of full code refactoring.
action palette and command discovery with fuzzy search
CodeCompanion provides an action palette (accessible via :CodeCompanionActions or keybinding) that enables fuzzy-searchable discovery of available commands, interactions, and workflows. The palette displays all registered actions (chat, inline, cmd, etc.) with descriptions, allowing users to discover functionality without memorizing commands. Actions are extensible via Lua, enabling custom actions to appear in the palette.
Unique: Implements a centralized action palette with fuzzy search for discovering CodeCompanion commands and custom actions. Actions are extensible via Lua, enabling plugins to register custom actions in the palette.
vs alternatives: More discoverable than keybinding-based commands; fuzzy search reduces memorization overhead compared to static command lists.
inline code generation and diff-based editing with visual approval
The inline interaction enables direct code generation/modification in the current buffer via the :CodeCompanion command on visual selections or full buffer context. Generated code is presented as a unified diff in a preview buffer, allowing users to review changes before applying them. The system uses tree-sitter AST parsing (where available) to identify code boundaries and preserve formatting, then applies diffs via a custom diff engine that handles merge conflicts and partial application.
Unique: Uses a custom diff engine with tree-sitter AST awareness to preserve code structure and formatting during inline edits. Diff preview is rendered in a native Neovim buffer with syntax highlighting, allowing users to review changes before applying them via a single keypress.
vs alternatives: Faster iteration than chat-based code generation because changes are applied directly to the buffer; diff preview provides more control than Copilot's inline suggestions (which auto-apply or require rejection).
agent client protocol (acp) integration for stateful agentic workflows
CodeCompanion implements native support for the Agent Client Protocol (ACP), enabling integration with stateful AI agents like Claude Code, Cline, and Kilocode. Unlike HTTP-based LLM adapters that are stateless, ACP adapters maintain agent state across multiple interactions, allowing agents to perform multi-step tasks (file reading, execution, iteration) without user intervention. The plugin communicates with ACP agents via stdio or HTTP, marshaling tool calls and responses through the ACP schema.
Unique: Implements full ACP protocol support with stdio and HTTP transport, allowing Neovim to act as a client for stateful agents. Agents maintain their own state and tool execution context, enabling multi-step workflows without CodeCompanion managing intermediate state.
vs alternatives: Enables autonomous agent workflows in Vim (Claude Code, Cline) that are not possible with stateless LLM APIs; agents can iterate and refine solutions without user prompting.
+6 more capabilities