VS Code and JetBrains extension
How to Use Ruvicode with Continue
Continue reads its models from config.yaml. This guide adds Ruvicode models with the openai provider and apiBase, and sets the tool_use capability that Agent mode needs for models Continue does not recognize.
Checked on November 3, 2026. Config checked against Continue's config.yaml reference and OpenAI provider page. Streamed tool calls, which Agent mode uses, completed through api.ruvicode.com with the models below.
Set up Continue
Base URL
https://api.ruvicode.com/v1
API key
rvcd_...
- 1Open the config dropdown at the top right of the Continue chat input and click the cog next to Local Config. This opens config.yaml (~/.continue/config.yaml, or %USERPROFILE%\.continue\config.yaml on Windows).
- 2Add the Ruvicode models below under models.
- 3Save the file and pick the model in the Continue model selector.
name: My Config
version: 0.0.1
schema: v1
models:
- name: GLM 5.3 Flash (Ruvicode)
provider: openai
model: glm-5.3-flash
apiBase: https://api.ruvicode.com/v1
apiKey: rvcd_...
roles: [chat, edit, apply]
capabilities: [tool_use]
- name: Claude Sonnet 5.5 (Ruvicode)
provider: openai
model: claude-sonnet-5.5
apiBase: https://api.ruvicode.com/v1
apiKey: rvcd_...
roles: [chat, edit, apply]
capabilities: [tool_use, image_input]Good to know
- Continue detects capabilities for models it knows. For Ruvicode model ids, set capabilities yourself: tool_use for Agent mode, image_input for vision models.
- Leave autocomplete on a small, fast model. A large reasoning model makes tab completion slow and costs more per keystroke.
Models for coding agents
These models completed streamed tool calls through Ruvicode on November 3, 2026. Every model in the catalog works with the same base URL and key; each model page shows its live rate, context window and max output.
- GLM 5.3 Flash
glm-5.3-flash - Claude Sonnet 5.5
claude-sonnet-5.5 - Kimi K2.7 Code
kimi-k2.7-code
Common errors
- 401 Invalid API key
- The key is mistyped, revoked or not a Ruvicode key. Copy it again from the dashboard; it starts with rvcd_.
- 404 Model not found
- The model id is not in the catalog. Use an id exactly as listed on the models page or by GET /v1/models. A plain 404 page instead of a JSON error means the base URL is missing /v1.
- 402 insufficient_balance
- The wallet cannot cover the request. Top up in the dashboard; the balance never expires.
- 429 rate limit
- Too many requests per minute, on the key or across the account. Agents that fire many calls in parallel can hit it; most tools retry on their own after a short wait.
Continue with Ruvicode: FAQ
- Agent mode does not use tools with my Ruvicode model. Why?
- Continue needs the tool_use capability for Agent mode, and it cannot detect capabilities for model ids it does not know. Add capabilities: [tool_use] to the model entry in config.yaml.
- Does Continue work in JetBrains IDEs with Ruvicode?
- Yes. The JetBrains plugin reads the same ~/.continue/config.yaml.
- Where do I get a Ruvicode API key?
- Create an account, top up your wallet with QRIS or USDC, then open API Keys in the dashboard and create a key. Keys start with rvcd_. You can set a daily or monthly spend limit per key and restrict a key to a list of models.
Guides for other tools
The same base URL and key work everywhere. Setup for each tool: