Roo Code gives you a whole dev team of AI agents in your code editor.
|
|
vor 11 Monaten | |
|---|---|---|
| .changeset | vor 11 Monaten | |
| .github | vor 11 Monaten | |
| .husky | vor 1 Jahr | |
| .vscode | vor 1 Jahr | |
| assets | vor 1 Jahr | |
| audio | vor 1 Jahr | |
| cline_docs | vor 11 Monaten | |
| src | vor 11 Monaten | |
| webview-ui | vor 11 Monaten | |
| .clinerules | vor 11 Monaten | |
| .eslintrc.json | vor 1 Jahr | |
| .gitattributes | vor 1 Jahr | |
| .gitignore | vor 11 Monaten | |
| .npmrc | vor 1 Jahr | |
| .nvmrc | vor 1 Jahr | |
| .prettierignore | vor 1 Jahr | |
| .prettierrc.json | vor 1 Jahr | |
| .vscode-test.mjs | vor 1 Jahr | |
| .vscodeignore | vor 1 Jahr | |
| CHANGELOG.md | vor 11 Monaten | |
| LICENSE | vor 1 Jahr | |
| README.md | vor 11 Monaten | |
| ellipsis.yaml | vor 1 Jahr | |
| esbuild.js | vor 1 Jahr | |
| jest.config.js | vor 11 Monaten | |
| package-lock.json | vor 11 Monaten | |
| package.json | vor 11 Monaten | |
| tsconfig.json | vor 1 Jahr |
A fork of Cline, an autonomous coding agent, with some additional experimental features. It’s been mainly writing itself recently, with a light touch of human guidance here and there.
You can track what's new at our CHANGELOG, with some highlights below.
Hot off the heels of v3.0 introducing Code, Architect, and Ask chat modes, one of the most requested features has arrived: customizable prompts for each mode! 🎉
You can now tailor the role definition and custom instructions for every chat mode to perfectly fit your workflow. Want to adjust Architect mode to focus more on system scalability? Or tweak Ask mode for deeper research queries? Done. Plus, you can define these via mode-specific .clinerules-[mode] files. You’ll find all of this in the new Prompts tab in the top menu.
The second big feature in this release is a complete revamp of prompt enhancements. This feature helps you craft messages to get even better results from Cline. Here’s what’s new:
Whether you’re using GPT-4, other APIs, or switching configurations, this gives you total control over how your prompts are optimized.
As always, we’d love to hear your thoughts and ideas! What features do you want to see in v3.2? Drop by https://www.reddit.com/r/roocline and join the discussion - we're building Roo Cline together. 🚀
You can now choose between different prompts for Roo Cline to better suit your workflow. Here’s what’s available:
Code: (existing behavior) The default mode where Cline helps you write code and execute tasks.
Architect: "You are Cline, a software architecture expert..." Ideal for thinking through high-level technical design and system architecture. Can’t write code or run commands.
Ask: "You are Cline, a knowledgeable technical assistant..." Perfect for asking questions about the codebase or digging into concepts. Also can’t write code or run commands.
Switching Modes: It’s super simple! There’s a dropdown in the bottom left of the chat input to switch modes. Right next to it, you’ll find a way to switch between the API configuration profiles associated with the current mode (configured on the settings screen).
Why Add This?
Right now, switching modes is a manual process. In the future, we’d love to give Cline the ability to suggest mode switches based on context. For now, we’d really appreciate your feedback on this feature.
Please note that Roo Veterinary, Inc does not make any representations or warranties regarding any code, models, or other tools provided or made available in connection with Roo-Cline, any associated third-party tools, or any resulting outputs. You assume all risks associated with the use of any such tools or outputs; such tools are provided on an "AS IS" and "AS AVAILABLE" basis. Such risks may include, without limitation, intellectual property infringement, cyber vulnerabilities or attacks, bias, inaccuracies, errors, defects, viruses, downtime, property loss or damage, and/or personal injury. You are solely responsible for your use of any such tools or outputs (including, without limitation, the legality, appropriateness, and results thereof).
Here's an example of Roo-Cline autonomously creating a snake game with "Always approve write operations" and "Always approve browser actions" turned on:
https://github.com/user-attachments/assets/c2bb31dc-e9b2-4d73-885d-17f1471a4987
To contribute to the project, start by exploring open issues or checking our feature request board. We'd also love to have you join the Roo Cline Reddit to share ideas and connect with other contributors.
Install dependencies:
npm run install:all
Build the VSIX file:
npm run build
The new VSIX file will be created in the bin/ directory
Install the extension from the VSIX file as described below:
Option 1: Drag and drop the .vsix file into your VSCode-compatible editor's Extensions panel (Cmd/Ctrl+Shift+X).
Option 2: Install the plugin using the CLI, make sure you have your VSCode-compatible CLI installed and in your PATH variable. Cursor example: export PATH="$PATH:/Applications/Cursor.app/Contents/MacOS"
# Ex: cursor --install-extension bin/roo-cline-2.0.1.vsix
# Ex: code --install-extension bin/roo-cline-2.0.1.vsix
Launch by pressing F5 (or Run->Start Debugging) to open a new VSCode window with the extension loaded. (You may need to install the esbuild problem matchers extension if you run into issues building the project.)
We use changesets for versioning and publishing this package. To make changes:
npm run changeset
patch for bug fixes, minor for new features, or major for breaking changesOnce your merge is successful:
CHANGELOG.md file
Meet Cline, an AI assistant that can use your CLI aNd Editor.
Thanks to Claude 3.5 Sonnet's agentic coding capabilities, Cline can handle complex software development tasks step-by-step. With tools that let him create & edit files, explore large projects, use the browser, and execute terminal commands (after you grant permission), he can assist you in ways that go beyond code completion or tech support. Cline can even use the Model Context Protocol (MCP) to create new tools and extend his own capabilities. While autonomous AI scripts traditionally run in sandboxed environments, this extension provides a human-in-the-loop GUI to approve every file change and terminal command, providing a safe and accessible way to explore the potential of agentic AI.
open -a "Google Chrome" index.html, which you run with a click of a button.[!TIP] Use the
CMD/CTRL + Shift + Pshortcut to open the command palette and type "Cline: Open In New Tab" to open the extension as a tab in your editor. This lets you use Cline side-by-side with your file explorer, and see how he changes your workspace more clearly.
Cline supports API providers like OpenRouter, Anthropic, Glama, OpenAI, Google Gemini, AWS Bedrock, Azure, and GCP Vertex. You can also configure any OpenAI compatible API, or use a local model through LM Studio/Ollama. If you're using OpenRouter, the extension fetches their latest model list, allowing you to use the newest models as soon as they're available.
The extension also keeps track of total tokens and API usage cost for the entire task loop and individual requests, keeping you informed of spend every step of the way.
Thanks to the new shell integration updates in VSCode v1.93, Cline can execute commands directly in your terminal and receive the output. This allows him to perform a wide range of tasks, from installing packages and running build scripts to deploying applications, managing databases, and executing tests, all while adapting to your dev environment & toolchain to get the job done right.
For long running processes like dev servers, use the "Proceed While Running" button to let Cline continue in the task while the command runs in the background. As Cline works he’ll be notified of any new terminal output along the way, letting him react to issues that may come up, such as compile-time errors when editing files.
Cline can create and edit files directly in your editor, presenting you a diff view of the changes. You can edit or revert Cline's changes directly in the diff view editor, or provide feedback in chat until you're satisfied with the result. Cline also monitors linter/compiler errors (missing imports, syntax errors, etc.) so he can fix issues that come up along the way on his own.
All changes made by Cline are recorded in your file's Timeline, providing an easy way to track and revert modifications if needed.
With Claude 3.5 Sonnet's new Computer Use capability, Cline can launch a browser, click elements, type text, and scroll, capturing screenshots and console logs at each step. This allows for interactive debugging, end-to-end testing, and even general web use! This gives him autonomy to fixing visual bugs and runtime issues without you needing to handhold and copy-pasting error logs yourself.
Try asking Cline to "test the app", and watch as he runs a command like npm run dev, launches your locally running dev server in a browser, and performs a series of tests to confirm that everything works. See a demo here.
Thanks to the Model Context Protocol, Cline can extend his capabilities through custom tools. While you can use community-made servers, Cline can instead create and install tools tailored to your specific workflow. Just ask Cline to "add a tool" and he will handle everything, from creating a new MCP server to installing it into the extension. These custom tools then become part of Cline's toolkit, ready to use in future tasks.
@url: Paste in a URL for the extension to fetch and convert to markdown, useful when you want to give Cline the latest docs
@problems: Add workspace errors and warnings ('Problems' panel) for Cline to fix
@file: Adds a file's contents so you don't have to waste API requests approving read file (+ type to search files)
@folder: Adds folder's files all at once to speed up your workflow even more
To contribute to the project, start by exploring open issues or checking our feature request board. We'd also love to have you join our Discord to share ideas and connect with other contributors. If you're interested in joining the team, check out our careers page!