What is Roo Code?
Roo Code is an open-source VS Code coding agent that can use OpenAI-compatible providers, edit files, and run approved tools.
This Roo Code guide adds TokenHub through its OpenAI Compatible provider settings. Test a read-only task first, then validate native tool calling before enabling file edits or terminal commands. Roo Code can read files, propose edits, and run terminal tools from VS Code, so provider connectivity and agent capability must be tested separately. Keep auto-approval off for the first run, use a disposable repository, and review each requested action until the selected model proves reliable with native tool calls.
Roo Code can route model requests through TokenHub's OpenAI compatible API gateway. Keep the official installation flow, then replace only the API key, Base URL, and model ID.
The TokenHub endpoint used by this guide is https://us-api.tokenhub.com/v1/chat/completions.
When to use it
Start in a small repository or test project. First ask the tool to read files, explain code, or produce a plan; only then enable edits, terminal commands, or agent automation.
Install or open the tool
Follow the official Roo Code documentation to install or open the tool. If menus or command names differ, prefer the current official documentation.
For CLI tools, confirm the executable works before adding TokenHub credentials:
# open the tool, then open its model or provider settingsPrepare TokenHub credentials
Create a TokenHub API key and choose a model from the TokenHub model list that fits this tool.
export TOKENHUB_API_KEY="sk-..."Keep the key in your local shell, IDE secret storage, or the secure API key field of the tool. Do not commit it to the repository.
Configure TokenHub persistently
Use the tool configuration file or settings page first. This avoids the common problem where a terminal sees the environment variable but the IDE, plugin, or new window does not.
Provider values
| Field | Value |
|---|---|
| Provider | OpenAI Compatible or Custom |
| Base URL | https://us-api.tokenhub.com/v1 |
| API Key | The value of TOKENHUB_API_KEY |
| Model | gpt-4.1 or another TokenHub model ID |
Settings file locations
| Field | Value |
|---|---|
| Provider settings | Roo Code provider settings or configuration profile |
| Provider mode | OpenAI Compatible |
| Required fields | Base URL, API Key, Model ID |
Use the settings UI first when the extension owns the schema. It stores the same values in a user-level settings file and avoids guessing private keys that may change between releases.
Use a model that supports OpenAI tool calling for Code mode tasks.
If the tool separates chat, edit, apply, and fast models, use the same TokenHub model for the first test. Split models later by cost, latency, and reasoning strength.
Temporary environment variables for debugging
Use the settings UI first when the extension owns the schema. It stores the same values in a user-level settings file and avoids guessing private keys that may change between releases.
Use temporary variables only to confirm the key, network, and model name. After validation, move the same values into the persistent configuration above.
Verify the connection
Test with a read-only prompt first, confirming that the model can read context without changing files. Then test edits, Apply, or agent tasks.
Read the project README and summarize it in three sentences. Do not modify any files.After a successful prompt, check TokenHub request logs for model name, endpoint, token usage, and billing group.
Troubleshooting
| Symptom | Fix |
|---|---|
| 401 or authentication failure | Confirm TOKENHUB_API_KEY is valid and saved in the same terminal, IDE, or client profile. |
| 404 or model not found | Use a model ID that exists in your TokenHub workspace and matches the selected protocol. |
| Wrong endpoint | Keep the Base URL exactly as shown. OpenAI-compatible tools usually need /v1; Claude-compatible tools usually do not. |
| Request timeout | Check network access to https://us-api.tokenhub.com, proxy settings, and workspace allowlists. |
| Tool uses another model | Recheck every chat, edit, apply, fast, and autocomplete model slot. |
Choose a compatible Roo Code model
Roo Code API provider FAQ
Which API Provider should I choose in Roo Code?
Choose OpenAI Compatible, then enter the TokenHub Base URL, API key, and exact model ID.
What if chat works but tool calls fail?
First switch to a Coding or Agent model that explicitly supports native tool calling, then check Roo Code permissions and approval mode.
How can I reduce risk during the first Roo Code test?
Use a test repository, begin with a read-only explanation, keep auto-approval off, then verify edits and terminal commands gradually.
How do I troubleshoot a Roo Code 401?
Check the API key for missing characters or spaces and confirm it is saved in the active profile. Retry a short request and inspect TokenHub logs.
How do I troubleshoot a Roo Code 404?
Use the TokenHub API root ending in /v1, avoid a duplicated /chat/completions path, and confirm that the model ID exists.
References
This setup is based on TokenHub and official documentation, last verified on 2026-09-04.
