Roo Code Shut Down: Alternatives (Cline, Zoo Code, Kilo Code) and Relay Setup

As of October 2026, the Roo Code extension is shut down according to its official README. If you used it with an AI API relay, this guide shows how to point alternatives at the same relay: Cline, Zoo Code (a community fork of Roo Code), and Kilo Code.

Status notice (as of October 2026)

The Roo Code README says: "The Roo Code Extension was shut down on May 15th." The official documentation carries the same notice, and GitHub shows the repository as archived. Both pages name ZooCode (a fork started by the Roo Code community) and Cline as alternatives. We no longer cover Roo Code setup here. Settings below come from each project's own current documentation; check those pages if a screen looks different from what is described.

Roo Code vs Cline vs Zoo Code: which one to pick

Cline

The project Roo Code originated from, per Roo's README. Its README lists a VS Code extension, a JetBrains plugin, a CLI, a desktop app and an SDK. Pick it if you want a tool that is not tied to the Roo workflow.

Zoo Code

A community fork of Roo Code, and the lowest-friction move for existing Roo Code users: its docs describe a settings export from Roo Code and an import into Zoo Code. It is not published by the Roo Code team. See its README.

Both showed active development in October 2026 (a Cline desktop release on October 13 and a Zoo Code v3.88.0 release on October 10, per their GitHub release pages). We make no promise about how long either will keep being maintained.

Why point these tools at a relay

Both tools are model-agnostic: they need an LLM provider and work with many of them, so a relay is one more provider choice. People pick one for payment methods the official provider does not accept in their region, per-token prices that differ between channels, and one key that reaches several model families. The trade-off is that the relay sits between you and the model, so read what an API relay is and the common pitfalls before you fund an account.

Cline: connect it to a relay

Cline's OpenAI Compatible page and Anthropic page describe the settings. The VS Code extension is the "Install from VS Marketplace" link in the Cline README.

Option A: OpenAI Compatible provider

Click the settings icon (gear) in the Cline panel.
Choose "OpenAI Compatible" from the API Provider dropdown.
Enter your relay's address in Base URL, your relay key in API Key, and the model ID your relay lists in Model.

API Provider: OpenAI Compatible
Base URL:     https://your-relay-domain/v1     (use exactly what your relay documents)
API Key:      your-relay-key
Model:        the-model-id-from-your-relay

Cline's docs say the Base URL is the provider's own endpoint, not the official OpenAI address. The page also lists a Model Configuration section (Max Output Tokens, Context Window size, Image Support, Computer Use, Input Price, Output Price) and an Azure Identity Authentication checkbox, which a relay does not need.

Option B: Anthropic provider with a custom base URL

Click the settings icon (gear) in the Cline panel.
Choose "Anthropic" from the API Provider dropdown.
Paste your key into the "Anthropic API Key" field and select a model from the Model dropdown.
Check "Use custom base URL" and enter the relay's Anthropic-format address.

Cline's docs say most users do not need the custom base URL option, but a relay is exactly the case where you do. They do not say whether the URL should include a path such as /v1, so follow your relay's instructions for Anthropic-format clients. We only checked the settings panel described in the docs; the CLI, desktop app and JetBrains plugin may differ.

Zoo Code: migrate from Roo Code and connect it to a relay

Zoo Code is a community fork of Roo Code, not an official Roo Code release. Per its install page, search for "Zoo Code" in the VS Code Extensions view and select the one by ZooCodeOrg. Its OpenAI Compatible and Anthropic pages describe the provider settings.

Bring your Roo Code settings over (optional)

The Roo to Zoo migration page gives these steps:

In Roo Code, open the settings and click Export, then save the file when the save dialog opens.
Open Zoo Code and click Import Settings.
Select the file you exported from Roo Code. Zoo Code merges the settings into your current setup.

That page warns the exported file can include sensitive settings, including API keys, so store it carefully and do not share it. After importing, check the result in Zoo Code's settings before relying on it.

Option A: OpenAI Compatible provider

Click the settings (gear) icon in the Zoo Code panel and set:

API Provider: OpenAI Compatible
Base URL:     https://your-relay-domain/v1     (use exactly what your relay documents)
API Key:      your-relay-key
Model:        the-model-id-from-your-relay

Zoo Code's docs list the same Model Configuration items (Max Output Tokens, Context Window, Image Support, Computer Use, Input Price, Output Price). They also state that Zoo Code uses native tool calling exclusively, so the model you pick must support OpenAI-compatible tool calling.

Option B: Anthropic provider with a custom base URL

Open the settings with the gear icon, choose "Anthropic" from the API Provider dropdown, paste the key into the "Anthropic API Key" field, pick a model from the Model dropdown, then check "Use custom base URL" and enter the relay's Anthropic-format address. As with Cline, the docs do not say whether that URL should include /v1, so follow your relay's instructions.

Kilo Code: another maintained alternative

Roo Code's shutdown notice names ZooCode and Cline only. We add Kilo Code here because its documentation describes a custom provider that accepts any OpenAI-compatible endpoint, which is what most relays offer. Its README describes it as an open source coding agent for VS Code, JetBrains and the CLI, and the repository is licensed under the MIT license. We did not find any statement in that README about a relationship to Roo Code or Cline, so we do not claim one.

Maintenance status, as of October 2026: GitHub's API shows the Kilo-Org/kilocode repository as not archived, and its latest commit on the main branch is dated October 15, 2026. We make no promise about how long it will keep being maintained.

OpenAI Compatible custom provider (VS Code)

The OpenAI Compatible page of the Kilo Code docs gives these steps for the VS Code extension: open Settings (gear icon), go to the Providers tab, scroll to the bottom and click Custom provider, then fill in the dialog and click Submit.

Provider ID:    a unique identifier you choose (the docs' example is my-provider)
Display name:   a human-readable name shown in the UI
Provider API:   OpenAI Compatible
Base URL:       https://your-relay-domain/v1     (use exactly what your relay documents)
API key:        your-relay-key
Models:         add model IDs from your relay's list, or pick from the fetched list
Headers:        optional, custom HTTP headers as key-value pairs

Per the same page, Kilo Code tries to fetch the available models from the provider's /v1/models endpoint once a valid Base URL and API key are entered, and you can enter model IDs manually if that fails. The page also says the Base URL field accepts a full endpoint URL such as one ending in /chat/completions, so use exactly the form your relay documents.

Anthropic-format relay

The same dialog has a Provider API field with three choices listed in the docs: OpenAI Compatible, OpenAI Responses and Anthropic Messages. The docs say to use Anthropic Messages for Anthropic and MiniMax models, so for a relay that serves Claude in Anthropic format, choose Anthropic Messages there. The docs do not say whether the Base URL should include a path such as /v1 for that choice, so follow your relay's instructions. Kilo Code's separate Anthropic page only describes adding Anthropic in the Providers tab with an API key; it does not mention a custom base URL.

CLI and other surfaces

For the CLI, the OpenAI Compatible page describes defining the provider in a kilo.json file instead; see that page for the file format. We only read the documentation and did not test Kilo Code ourselves, and the JetBrains plugin may differ. If a screen looks different, see Kilo Code's provider docs.

Confirm the connection works

Open the tool's panel and give it a small, safe task, such as asking it to read and summarize one file in your project. A normal reply means the Base URL, key and model ID are all accepted. Keep any auto-approve option off while you test, since these agents can run commands and edit files.

A reply only proves the endpoint answers, not that the model is the one you chose. To check that, run the relay through our relay verification tool.

Troubleshooting

401 or "Invalid API Key"

Both Cline's and Zoo Code's docs list "Invalid API Key" first: re-enter the key and make sure it is the relay's key, not one from the upstream provider. Also check the relay dashboard to see whether the key is enabled, restricted to certain groups, or out of balance.

404 or connection errors

Both docs say to verify the Base URL is correct and the provider's API is reachable. A 404 almost always means the path is wrong. The official OpenAI address both docs mention ends in /v1, and many relays follow the same pattern, but use the exact value in your relay's own docs, with or without /v1 as they specify.

"Model Not Found"

Both docs say to use a valid model ID for your provider. Relays sometimes rename models or split them into groups, so copy the ID from the relay's model list rather than from an official provider page.

Tool-calling errors (Zoo Code)

Zoo Code's docs say it uses native tool calling only, so the model must support OpenAI-compatible tool calling, and some providers only partially implement it. If tasks fail when it tries to read or edit files, try another model or channel group on the same relay, and ask the relay whether that group supports function calling.

Replies feel wrong or off-quality

Both docs suggest trying a different model when results are unexpected. If you suspect the relay is serving a different model than the one you picked, run it through our verification tool below.

Official sources used

FAQ

Can I still use Roo Code?

Roo Code's own README and documentation say the extension was shut down on May 15th (2026), and GitHub shows its repository as archived. An existing installation may still be on your machine, but it is no longer being developed, so this guide covers alternatives instead of Roo Code setup. Facts here were checked against the official pages as of October 2026.

Which should I switch to, Cline or Zoo Code?

If you already use Roo Code, Zoo Code is the lowest-friction move: it is a community fork of Roo Code, and its docs describe exporting your settings from Roo Code and importing them into Zoo Code. If you do not care about keeping the Roo workflow, Cline, the project Roo Code originated from per Roo's README, is also available as a CLI, desktop app and JetBrains plugin besides the VS Code extension. Both were actively maintained as of October 2026.

What is the difference between Cline and Zoo Code?

Zoo Code describes itself as continuing the Roo Code project, and its provider pages read almost the same as Roo's old ones. Cline is a separate project that Roo Code originated from. The provider settings you need for a relay (OpenAI Compatible or Anthropic, with a base URL, key and model) are documented in both, as shown above.

Roo Code vs Cline: what changed after Roo Code shut down?

Roo Code's own README and documentation say the extension was shut down on May 15th (2026), and GitHub shows its repository as archived, so it is no longer being developed. That README points to two alternatives: Cline, described as the project Roo Code originated from, and ZooCode, described as a fork started by the Roo Code community. Cline is a separate project with its own documentation; Zoo Code is the community fork. Facts here were checked against the official pages as of October 2026.

Kilo Code vs Claude Code?

They are different products from different publishers. Kilo Code's README describes an open source coding agent for VS Code, JetBrains and a CLI, while Claude Code is Anthropic's agentic coding tool, which Anthropic's overview says is available in the terminal, IDE, desktop app and browser. This guide does not rank them. If you want to point Claude Code at a relay, see our Claude Code relay setup article.

How do I connect Cline or Zoo Code to an API relay?

Open the settings (gear icon), choose OpenAI Compatible, and enter the relay's Base URL, your relay key and the model ID. For a relay that serves Claude in Anthropic format, choose Anthropic and use the "Use custom base URL" option instead. Then give it a small task to confirm the connection.

How do I know the model behind the relay is the one I picked?

The coding tool only reports what the endpoint tells it. To check that a relay really serves the model it advertises, use the HowToken verification tool, or follow the manual checks in our model-check guide.

Verify a relay How to connect and use Manual model check Browse all relays