> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/gateway-api/integrations/roo-code.md).

# Roo Code Integration

Install and configure the Roo Code extension in VS Code, then point it at the nexos.ai API Gateway using your API key to start coding with any model.

**Roo Code** is an AI-powered **autonomous coding agent** that seamlessly integrates into Visual Studio Code editor.

It can leverage the OpenAI compliant nexos.ai API gateway to provide responses.

{% hint style="info" %}
**Note**: Roo Code was **discontinued on May 15, 2026**, and is no longer maintained. [**Zoo Code**](/gateway-api/integrations/zoo-code.md) is the community continuation of the same codebase, so the nexos.ai setup is almost identical. 
{% endhint %}

## How to connect nexos.ai API and Roo Code?

To connect your nexos.ai API and Roo Code go through the following steps:

{% stepper %}
{% step %}

### Generate your personal API key

Log in to your nexos.ai account and head over to the User profile section by clicking on the profile bubble in top right corner of the UI.

{% hint style="danger" %}
Make sure to store your API key safely and securely. Never share it with anyone. 
{% endhint %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2F0LGvNLlyqKw42xaiWCWB%2F1_nexos_roocode_API00000000.mp4?alt=media&token=4699eed3-4720-464c-9a70-b960aa573c68>" %}
How to generate a personal API key
{% endembed %}
{% endstep %}

{% step %}

### Install Roo Code extension in your Visual Studio Code

You can install Roo Code in multiple ways:&#x20;

* **VSC extensions tab** - Open the extensions tab in Visual Studio Code and search for "Roo Code", once results appear select Roo Code from the list and click "Install"

{% hint style="warning" %}
You might be asked if you trust the publisher of the extension. Make sure you familiarize yourself with the risks of using extensions.
{% endhint %}

* **VSC CLI** - Use the following command within Visual Studio Code command line interface to download and install the Roo Code extension<br>

  ```
  code --install-extension RooVeterinaryInc.roo-cline
  ```

* **VSC Marketplace website** - Head over to the Visual Studio Code marketplace website to download and install the extension\
  <https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline>

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2FW31KmmRtX4nCzJKDOnsE%2F2_nexos_roocode_install00000128.mp4?alt=media&token=8508c76d-3b6b-4242-a62d-471e5f6d0470>" %}
Installing Roo Code through the built-in extensions marketplace
{% endembed %}
{% endstep %}

{% step %}

### Configure the Roo Code extension

Finally, configure Roo Code to take advantage of your nexos.ai API Gateway access.

* Head over to the new Roo Code tab in the left navigation bar
* Select "OpenAI Compatible" as your API Provider
* Provide "`https://api.nexos.ai/v1` " as the Base URL
* Paste the API key generated in step 1 in the API Key section
* Click the "Let's go!" button at the bottom of the configuration screen

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2FcvQSR3obkXRXXBtl1F2H%2F3_nexos_roocode_config.mp4_00000000.mp4?alt=media&token=9357c616-4487-4f6c-85b4-9524fa237358>" %}
Configuring Roo Code with nexos.ai API Gateway
{% endembed %}

{% hint style="info" %}
If you want to find all available models and their names you can use the `/models` endpoint. Learn more here -  <https://docs.nexos.ai/gateway-api/models>
{% endhint %}
{% endstep %}

{% step %}

### Send first message

Make sure everything is working correctly by sending the first message.
{% endstep %}
{% endstepper %}

## FAQ

### Which other integrations are available in nexos.ai Gateway?

nexos.ai Gateway supports integrations with the following coding tools:

* [CrewAI](https://docs.nexos.ai/gateway-api/integrations/crewai)
* [Codex CLI](https://docs.nexos.ai/gateway-api/integrations/codex-cli)
* [OpenCode](https://docs.nexos.ai/gateway-api/integrations/opencode)
* [Claude Code](https://docs.nexos.ai/gateway-api/integrations/claude-code)
* [Claude Cowork](https://docs.nexos.ai/gateway-api/integrations/claude-cowork)
* [Bubble](https://docs.nexos.ai/gateway-api/integrations/bubble)
* [GitLab CI](https://docs.nexos.ai/gateway-api/integrations/gitlab-ci)
* [OpenAI Agents SDK](https://docs.nexos.ai/gateway-api/integrations/openai-agents-sdk)
* [Vercel AI SDK](https://docs.nexos.ai/gateway-api/integrations/vercel-ai-sdk)
* [Streamlit](https://docs.nexos.ai/gateway-api/integrations/streamlit)
* [ProxyAI](https://docs.nexos.ai/gateway-api/integrations/proxyai)
* [Langfuse](https://docs.nexos.ai/gateway-api/integrations/langfuse)
* [LangGraph](https://docs.nexos.ai/gateway-api/integrations/langgraph)
* [LangChain](https://docs.nexos.ai/gateway-api/integrations/langchain)
* [n8n](https://docs.nexos.ai/gateway-api/integrations/n8n)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexos.ai/gateway-api/integrations/roo-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.