Roo Code shut down: move your API provider to Cline.

Choose what to use now

• Keep an open-source VS Code coding extension: Roo Code recommended Cline as an alternative. Cline has its own provider settings and behavior; it is not the same extension or an automatic replacement for every Roo feature.
• Follow the Roo team's next product: Roo's notice points to Roomote. Check its current product and API-provider support before moving a workflow.
• Continue using a locally installed Roo build: an installed copy can be separate from Roo Cloud and Router, but the project is archived and no longer receives official fixes. Do not rely on a retired Roo-hosted route.

Recreate an OpenAI-compatible provider in Cline

If your Roo setup used a separate provider or gateway, the provider's endpoint and account are independent of Roo Router. Recreate the connection in Cline using the current provider documentation:

1. Record the provider name, documented API base URL and exact model ID. Keep the base URL at the API root; do not append /chat/completions unless that provider explicitly requires it.
2. Open Cline settings and choose OpenAI Compatible as the API provider.
3. Enter the provider's API base URL, the key issued by that provider and its exact model ID. Use the provider's own current region and protocol instructions.
4. Save the profile and try a short request. Then check tool calling, images, streaming and context separately; a matching endpoint format does not guarantee every feature works.

For the current Cline fields and provider setup, see the Cline OpenAI Compatible documentation. For the distinction between a custom Chat Completions endpoint and other API protocols, use the API protocol guide.

Protect an exported Roo settings file

Roo's settings-management documentation says a settings export includes API keys in plaintext. Do not upload or post an unredacted export, and do not paste it into a support request or chat. For a manual migration, carry over non-secret values such as the provider, base URL and model ID, then enter the existing provider key directly into Cline. If you already exposed an export, follow that provider's key-revocation process.

The sources do not promise that Roo profiles, conversation history, custom modes, MCP configuration or permissions import into Cline. Move and verify those items separately using the destination app's own current instructions; this guide covers the model-provider connection only.

Check the model before a coding task

Roo Code's archived provider guide says its OpenAI-compatible adapter requires native tool calling. Cline's compatible-provider guide likewise asks you to configure the provider's base URL, key and model ID, but feature support still depends on the selected provider and model. Confirm tool-calling support and enough context/output for your task before giving an agent access to a repository.

Compare the provider's documented API route and feature limits in the connection guide or route comparison. If you already have an API response, inspect it locally with the response checker.

Official sources and scope

• Roo Code sunset notice — shutdown date, products affected, Cline recommendation and Roomote link.
• Roo Code OpenAI-compatible provider guide — archived connection fields and native tool-calling requirement.
• Roo Code settings export documentation — warns that exported API keys are plaintext.
• Cline OpenAI-compatible provider guide — current destination settings and provider-specific model IDs.

Checked 2 November 2026 against Roo Code's shutdown and archived setup documentation and Cline's current provider guide. This is a documentation-based migration guide; no Roo or Cline account, API key or model request was used.