Skip to main content
Configure an existing Roo Code installation to use NoMask’s Chat Completions API.
Roo Code’s original extension was shut down on May 15, 2026, and its repository is archived. This guide is for existing installations and official archived releases.

​
Before you start

  • Create a key on the API Keys page and add funds to your API balance.
  • Choose a text model with Function calling and streaming on the Models page. Copy its exact model ID.
  • Use the connection values below. Replace key placeholders locally; keep secrets out of project files and source control.
Replace your-model-id throughout the examples with the exact ID of a text model that supports function calling and streaming. Check the Models page for current availability and limits.
Examples use your selected model. If you change it, also update context, output and image settings to match that model. These guides cover text models; Image Studio models use separate image endpoints.

​
Configure Roo Code

Open Roo Code from VS Code’s Activity Bar. For an archived installation, use the official release instructions linked below, then reload the editor if requested and open a workspace folder.
  1. Open Roo Code’s settings and create or select an API configuration.
  2. Set API Provider to OpenAI Compatible. Enter the base URL, API key and exact Model ID below.
  3. Set the context window and maximum output to the selected model’s limits. Keep streaming enabled for the initial test.
  4. Save the configuration. Select it again after switching modes if Roo restores a different model.
Roo requires native function calling. Choose a text model marked Function calling on the Models page. Text-only replies from a model do not prove that it can run Roo’s tools.
This connection uses /chat/completions. Leave the endpoint suffix off the Base URL and avoid Responses or Anthropic Messages connections.

​
Connection reference

This JSON summarizes the values to enter in the settings UI. It is not an import file for the extension.

​
Test chat and tools

Open a small test folder in the editor and add a file named hello.txt containing Hello. Start a new task with the NoMask connection selected.
  1. Ask for a short text reply first: Reply with the word ready.
  2. Ask Read hello.txt and tell me what it contains. Approve the file-read action if prompted.
  3. Choose Code mode, then ask Change hello.txt to say Hello from NoMask. Do not change any other file.
  4. Review the proposed diff, approve it, and check the saved file. A reply alone does not verify that file editing works.
Text, a file-read tool action and an applied edit confirm the complete connection. These tasks make billable API requests; inspect their usage on your API overview. Roo’s Ask mode can read but cannot edit. Code mode supports editing, and each mode can remember a different model. Check the active configuration before troubleshooting an edit failure.

​
Troubleshooting

  • 401: check that your key is active and available to the process running the tool. Restart the tool after changing environment variables.
  • 402: add funds to your API balance or reduce the requested output.
  • 404: check the exact model ID and base URL. Direct connections use Chat Completions, not Responses or Anthropic Messages.
  • 429: wait for Retry-After. API keys share account limits; creating another key does not reset usage. Check the key’s monthly spending cap too.
  • Context or tool errors: start a shorter task, lower the output limit and confirm the model supports function calling. A plain text reply alone does not confirm file-editing tools work.
Check API Overview for usage and recent errors. Include the request ID when contacting support; never send your key. See Errors and Rate Limits.

​
Official references

Setup checked against the documentation below. Tool versions may change their settings or configuration format.