If you are choosing between Roo Code and Cline today, start with the status: Roo Code’s maintainers say the extension, cloud service, and router shut down on May 15, 2026, and recommend Cline as an open-source extension alternative. The Roo extension repository is archived. This is therefore a migration and workflow comparison for existing Roo users, not a choice between two actively maintained extensions. Official documentation checked November 3, 2026.

Is Roo Code still available as a supported extension?

No. Roo Code’s official sunset notice says its products were shut down on May 15, 2026, and its extension repository was archived. The archived repository is read-only. The maintainers recommend Cline for users seeking a model-agnostic open-source extension. Existing local files may still be useful as references, but do not treat the archived docs or releases as a current support commitment.

How did Roo Code and Cline organize approvals?

Roo Code’s archived custom-mode guide describes global modes and project modes, including a project-level .roomodes file. A mode could define available tool groups and file restrictions, alongside role instructions. Those are historical Roo configuration details, not a guarantee that old settings still work with a running service.

Cline’s current overview describes human approval for agent actions. Its Plan and Act documentation says Plan mode can inspect and discuss without modifying files or running commands; Act mode can make changes. Cline also documents per-category Auto Approve settings for file reads, edits, commands, browser use, and MCP. Its separate YOLO option approves all listed actions. Check the live setting descriptions in the app you install: the modes and controls should not be assumed to map one-to-one from Roo.

Where do configuration and instructions go in Cline?

Cline documents global configuration under ~/.cline/ and project configuration under .cline/. Its current configuration guide lists project rules, workflows, skills, hooks, agents, and plugins under the project directory, and says project files can be committed when they are intended for teammates. Keep provider secrets out of the repository.

Roo’s archived guide describes project modes in .roomodes, global mode settings, and mode-specific rule directories such as .roo/rules-{slug}/. Treat these as source material when migrating. Cline documents project rules and Plan/Act workflows, but its docs do not establish an automatic import or exact equivalent for every Roo mode, file restriction, or tool permission. Rebuild and test those behaviors explicitly.

How can I move a Roo workflow to Cline without widening access?

1. Keep a backup of the repository’s .roomodes and relevant .roo/ rule files. Review them for credentials or private paths before sharing them.
2. Write down what each mode was allowed to read, edit, or run, and which prompts or rules it applied. A mode name alone does not preserve those boundaries.
3. Install Cline from its current official source and set up the model provider separately. Start with Plan mode for exploration; use Act only when ready to make changes.
4. Recreate reusable project guidance in the appropriate .cline/ project files after checking the current Cline configuration guide. Keep approval controls conservative while validating the setup.
5. On a disposable branch, test one harmless read, one intended edit, one command that should prompt, and one nearby action that should remain blocked or require approval. Inspect the diff and run the project’s checks.

Cline documents per-action Auto Approve controls, and warns that YOLO mode approves file operations, commands, browser actions, MCP tools, and mode transitions. Avoid enabling broad approval settings just to imitate a former Roo mode. A Git checkpoint helps review or restore changes, but it does not replace access controls.

Which should a new user install?

For a currently documented open-source extension path, the Roo maintainers’ sunset notice points users to Cline. If you are maintaining an existing Roo installation or preserved configuration, treat Roo documentation as historical and verify what still runs locally; support and hosted services ended on the announced date. Compare the exact editor support, provider setup, approval preferences, and organization policies you need before moving a team workflow.

What does the evidence say about the comparison?

Public Reddit discussions directly ask how Roo Code and Cline differ and describe users choosing between them. These older posts are qualitative examples of the choice question only. They predate Roo’s shutdown and say nothing about current demand, current product quality, or how most users work. This page compares official documented behavior and status; it is not a coding benchmark or a claim that one tool produces better results.

Related: Cline vs Aider workflow comparison and Claude Code permission decision tree.