engineering
Provider Agnostic: How CVC Frees You From Vendor Lock-In
Jai Kumar MeenaMarch 6, 20265 min read
ProvidersVendor Lock-InMulti-ProviderFlexibility
Provider Agnostic: How CVC Frees You From Vendor Lock-In
The Lock-In Problem
Most AI coding tools lock you into a single provider. Claude Code works only with Anthropic. Copilot works primarily with OpenAI. Gemini CLI works only with Google. If a provider raises prices, changes terms, or degrades quality — you're stuck.
CVC's Provider Abstraction
CVC supports four providers through a clean adapter architecture:
| Provider | Models | Notes |
|---|---|---|
| Anthropic | Claude Opus 4.6, 4.5, Sonnet 4.5, Haiku 4.5 | Prompt caching, extended thinking |
| OpenAI | GPT-5.2, 5.2-Codex, 5-mini, 4.1 | Structured outputs |
| Gemini 3.1 Pro, 3 Pro, 3 Flash | Configurable thinking levels | |
| Ollama | Any local model | 100% free, 100% offline |
Switch providers with one command: /provider inside the agent, or --provider on launch.
Your cognitive state persists across switches. The memory, branches, commits, and search history don't care which provider generated them. The same CVC database serves Claude today and GPT tomorrow.