Provider matrix
Which model providers each Cordy product supports, and how they connect.
Every Cordy client is provider-neutral, but each ships a slightly different built-in set. This page is the quick reference. In all cases you can also add a custom OpenAI-compatible endpoint — including self-hosted and local model servers.
Built-in providers by product
| Provider | Chrome | Desktop | Mobile | Gateway |
|---|---|---|---|---|
| OpenAI | ✅ | via agent | ✅ | ✅ |
| Anthropic | ✅ | via agent | ✅ | ✅ |
| Google / Gemini | ✅ | via agent | — | ✅ |
| OpenRouter | ✅ | via agent | ✅ (default) | ✅ |
| xAI | ✅ | via agent | — | ✅ |
| Vercel AI Gateway | ✅ | via agent | ✅ | — |
| Volcengine Ark (火山方舟) | ✅ | via agent | ✅ | ✅ (channel) |
| Any OpenAI-compatible / self-hosted | ✅ | via agent | ✅ | ✅ |
| Local runtimes (Ollama, LM Studio, vLLM…) | ✅ | via agent | ✅ (LAN) | ✅ (channel) |
| On-device (Chrome built-in AI, in-browser Gemma, Kokoro TTS) | ✅ | — | — | — |
"via agent" — Cordy Desktop does not configure model providers itself. It launches your external CLI coding agents (Claude Code, Codex, Cursor, Gemini CLI…), and each agent uses its own provider configuration. Cordy holds no keys and reads no prompts.
How they connect
- Chrome and Mobile talk directly to the provider from the device, using the key you stored locally.
- Gateway aggregates 100+ providers (via LiteLLM plus a direct OpenAI-compatible path) behind one endpoint; clients then point at the gateway instead of individual providers.
- Desktop's agents make their own network calls; Cordy is not in that path.
The unifying contract
The common denominator is the OpenAI Chat Completions API shape. Anything that speaks it — a hosted cloud, an aggregator, your own Cordy Gateway, or a local llama.cpp/vLLM server — plugs in via a base URL + key. That is what makes the whole family provider-neutral. Learn more in BYOK.