Roo Code Setup
Use QCode.cc from the Roo Code VS Code extension: pick the Anthropic provider, tick the custom base URL, and Claude works
Need an API key? Sign up →Endpoints & base URLs →
On This Page
⚠️ Project archived: the GitHub repository RooCodeInc/Roo-Code has been archived (read-only) since 2026-05-15 — no further updates or fixes from the project. The configuration below still works for existing installs and serves as reference; for an actively maintained sibling consider migrating to Kilo Code or Cline.
Last verified: 2026-10-15 · 📄 Per official docs (archive status checked via the GitHub API; Roo Code no longer ships releases)
At a glance¶
| Item | Details |
|---|---|
| Models you can use | Claude ✅ (Anthropic provider + custom base URL) · GPT ✅ · Chinese models ✅ (OpenAI Compatible) · Gemini ❌ |
| Protocol & Base URL | Anthropic: https://api.qcode.cc/api · OpenAI: https://api.qcode.cc/openai/v1 |
| Where to configure | VS Code extension settings panel (API Provider / base-URL checkbox) |
| Official docs | Roo Code repository |
Roo Code is an open-source AI coding extension for VS Code, forked from Cline; Kilo Code in turn forked from it — the three share nearly identical settings screens, so this page transfers between them.
Which protocol¶
| Model you want | API Provider | Base URL |
|---|---|---|
| Claude | Anthropic |
https://api.qcode.cc/api |
| GPT / the four Chinese families | OpenAI Compatible |
https://api.qcode.cc/openai/v1 |
🔴 Do not use OpenAI Compatible to reach Claude — QCode's OpenAI endpoint rejects Claude models with model_not_available_on_endpoint. See Endpoints & API Paths.
Install¶
Search for Roo Code in the VS Code marketplace, or follow the instructions in the project repository.
Configure Claude (Anthropic provider)¶
- Open Settings (gear icon) in the Roo Code sidebar
- Set API Provider to Anthropic
- Put your QCode key (starts with
cr_) in API Key - Tick Use custom base URL and enter
https://api.qcode.cc/api - Choose
claude-sonnet-5(or another live id) in the model dropdown - Save, then send a message in the chat box to confirm
From mainland China, swap the host for
https://asia.qcode.cc/api(Asia node, nearest of Korea / Taiwan / Hong Kong); the key is unchanged. No trailing slash on the base URL — the extension appends/v1/messagesitself, and an extra slash produces a 404.
Configure GPT and Chinese models (OpenAI Compatible)¶
- Set API Provider to OpenAI Compatible
- Base URL:
https://api.qcode.cc/openai/v1 - API Key: the same
cr_key - Model ID:
gpt-6.2-sol,gpt-5.6-terra, or a Chinese id such asglm-5.3
Verify connectivity¶
Check the endpoint and key with curl first, so you know whether to debug the extension's UI:
KEY="cr_your_qcode_key"
curl -X POST https://api.qcode.cc/api/v1/messages \
-H "x-api-key: $KEY" -H "anthropic-version: 2023-06-01" \
-H "content-type: application/json" \
-d '{"model":"claude-sonnet-5","max_tokens":32,"messages":[{"role":"user","content":"ping"}]}'
JSON containing content means the endpoint side is fine; if the extension still fails, the problem is in its settings.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
model_not_available_on_endpoint |
Reaching Claude through OpenAI Compatible | Switch to the Anthropic provider with /api |
Invalid API key |
Wrong key or stray whitespace | Check the cr_ prefix and trim spaces |
| 404 | Trailing slash on the base URL, or wrong path | Compare against the table above |
| Your model id is missing from the dropdown | Not in the extension's built-in list | Type it into the custom model id field |
Settings explained¶
| Setting (Roo Code UI) | What to enter | Notes |
|---|---|---|
| API Provider | Anthropic (Claude) or OpenAI Compatible (GPT, Chinese models) |
Decides the protocol; the wrong choice is rejected outright |
| API Key | Your QCode key starting with cr_ |
The same key works with both providers |
| Use custom base URL | Tick it and enter https://api.qcode.cc/api |
Only needed for the Anthropic provider; use asia.qcode.cc in mainland China |
| Base URL (OpenAI Compatible) | https://api.qcode.cc/openai/v1 |
No trailing slash |
| Model / Model ID | For example claude-sonnet-5, gpt-6.2-sol, glm-5.3 |
If it is not in the built-in dropdown, type it into the custom field |
Further troubleshooting¶
First decide whether the problem is on the endpoint side or in the UI configuration: if the curl command from the "Verify connectivity" section returns content, QCode is fine. Then work through these in order:
- Rule out the small things first: a space around the key or a trailing slash on the Base URL are the two most common causes; fix them, save, and send a test message.
- Anthropic and OpenAI Compatible settings are mixed up: after switching provider, recheck the Base URL and key.
- The model you want is rejected: Claude only works through the Anthropic provider, GPT and Chinese models only through OpenAI Compatible; check the source-of-truth table in Endpoints and API Formats.
- Requests do not show up on the QCode side: enter your key at probe.qcode.cc to see whether requests arrive; no records means the request was never sent, so recheck the Base URL in the extension.
FAQ¶
Roo Code is archived. Can I still use it?¶
Yes, but it will not get updates or fixes. As of 2026-10-15 the GitHub API shows the RooCodeInc/Roo-Code repository as archived (read-only), with the last push on 2026-05-15. Existing installs still connect to QCode with the settings on this page; for a tool that is still maintained, move to Kilo Code or Cline, whose setup is almost identical.
Can I use GPT in Roo Code?¶
Yes. Choose OpenAI Compatible as the API Provider, set the Base URL to https://api.qcode.cc/openai/v1, and use gpt-6.2-sol or gpt-5.6-terra as the Model ID.
Why can't Claude be used with OpenAI Compatible?¶
QCode's OpenAI endpoint does not accept Claude models and returns model_not_available_on_endpoint. That check happens before authentication, so it means the wrong protocol was chosen, not that the key is bad. Use the Anthropic provider for Claude.
Which domain should I use in mainland China?¶
asia.qcode.cc is recommended (for the Anthropic provider enter https://asia.qcode.cc/api); switch back to api.qcode.cc if it is unstable. All three domains use the same key.
How does the setup differ from Cline and Kilo Code?¶
The interfaces are very similar: Roo Code was forked from Cline, and Kilo Code was forked from Roo Code. Protocol, Base URL and key are entered the same way; only some menu labels differ.
Related¶
- Endpoints & API Paths — protocol × model-family table
- Kilo Code Setup — downstream fork, nearly identical setup
- Cline Integration — the project Roo Code originated from
- Chinese Models
Get started with QCode
One API key for Claude Code, Codex and more — billed per token, per-model prices on qcode.cc/models