This is a very simple fork from Cline (prev. Claude Dev).
Warning
This is under active development, untested, unstable, and not ready for production. Use at your own risk.
Cline is amazing - the experince within the IDE, the robustness when keeping conversation threads consistent, the feedback loop, etc. However, my experience on using it in "real life" projects, has been less then ideal. It's main approach to interact with existing code is full file rewrites. That means:
(1) Slow: for anything over 100-200 lines, you need to wait for the LLM to rewrite the whole file when all it needed was adding a line. You are also stuck with reading full files (which is also slow) or not reading them at all.
(2) Expensive: because it always needs to rewrite the whole file, you are paying for all tokens within the file, when all you needed was one. Same thing goes when reading files, you are paying for all tokens, when all you needed was a small part of it for the LLM to understand the context.
(3) Error Prone: when it handles existing production code, most of the code already works, and Cline was constantly breaking things, requiring manual intervention. Some custom instructions helped, but at the end, I wasn't to prevent it from changing things
At the end of the day, I wasn't able to be productive with it, my Anthropic bill sky rocketed, was constantly reaching API limits, and wasn't getting much done.
The fork is very simple. Apart from some small refactoring, adjustments, renaming, etc, it adds a few things:
(1) SEARCH & REPLACE tool: which means that the LLM doesn't need to rewrite the file, but rather give a search block and a replace block, and this will be exactly like VSCode merge conflict UI, in which you are going to approve/reject the changes.
(2) INSERT CODE BLOCK tool: in which the LLM would give the position (eg. starting line) to where to add a piece of code, and the file, and only that part would be added, without needing to rewrite the whole thing
(3) READ FILE (WITH RANGE) tool: an adjustment of Cline's current read file approach that adds a new parameter allowing the LLM to select a specific range of lines to read.
Some other changes:
- Moves tools to a dedicated class/module
- Reorganize prompt formation and build
- Adds options for the user to set a threshold of what a "big" file is - if a file is too big, Codey returns only the topline definitions and some other small params
- Adds line numbers when reading files and definitions
- Better management on what to add to the environment details
- Refactor classes and methods into smaller pieces, hopefully making the codebase easier to understand and change
- (In Progress) Adds tests - Cline's interaction is fairly complex, and it can be challenging to understand all interactions and handling, idea is to make the codebase tested for easier changes and improvements in the future
I'm obviously biased, and I haven't made proper benchmarks and so this is just me sharing impressions. My experience has been very positive: changes are signifcantly faster, Claude 3.5 is very smart when navigating the project files, knowing what to read, and where to add stuff. It's increadibly cheaper, I'm almost back at normal spending levels, since that are signifcantly less tokens moving around, which also means I haven't been rate limited at all since I started using this. All in all, I happy with it's performance. I ran into a couple of scenarios where a full file rewrite was being done, and it shouldn't, and this is where polishing the prompt comes in, and only testing and time is going to solve that, but I'm ok with it so far. It's not as polished when it comes to the interactions, some restrictions:
- Insert code block fake streams: it doesn't stream in real time, only after all the chunks are processed
- Search and replace sometimes uses too large blocks
- Search and replace sometimes get a wrong line break making formatting weird
- If you have multiple rounds of changes, the last ones are tricky to get right, since Codey depends a lot more on positioning (eg. which line to insert the code block)
- Have seen bugs where multiple tools were being called, and none of them were being executed (fxied in 0.1.8 i think)
Anyways, I'm happy with it, and it will continue to be my daily driver. Still need to spend more time with other models both closed and open ones to see how it performs.
At this point, the code base is just too different, so won't be able to merge back to Cline, or merge from Cline, I'd be happy to share changes and contribute if anyone think it would be worth it. I haven't added anything related to the computer use capabilities, since I don't use it, but I'm happy to add it if someone wants to use it.
I had to change the name and the logo to be able to have this and Cline at the same time, the idea is not to build a parallel project, and I'd still encourage everyone to keep using Cline, so I won't be publishing this to the marketplace. However, if you want to test it locally you just need to clone the repo, build the package and install the VSIX:
# Clone the repo
git clone https://github.com/ccrvlh/codey
# Cd into the folder
cd codey
# Install deps
npm install
# Build the package
vsce packageOnce you do that, you'll have a codey-x.x.x.vsix file on the root of the project. You just right click and "Install VSIX" and the little rocket will appear.
vsce is usually global, so you might need to install it:
npm install -g @vscode/vsceIf you want to run tests:
npm run testFor now I just added a couple of tests for the message parser, and not for the tools, which is the most important part. I'll be adding more tests as I go.
If you want to fork this and make it your own and manage your own versions, there's a make target to make deployment and versioning easier:
make deployThis will increment the version (asking you whether to increase patch/minor/major) and build the project, and then you can just install the VSIX again, it will understand it is a new version and just ask you to refresh the extension.
Leaving the original Cline README below for reference.
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. 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.
- Enter your task and add images to convert mockups into functional apps or fix bugs with screenshots.
- Cline starts by analyzing your file structure & source code ASTs, running regex searches, and reading relevant files to get up to speed in existing projects. By carefully managing what information is added to context, Cline can provide valuable assistance even for large, complex projects without overwhelming the context window.
- Once Cline has the information he needs, he can:
- Create and edit files + monitor linter/compiler errors along the way, letting him proactively fix issues like missing imports and syntax errors on his own.
- Execute commands directly in your terminal and monitor their output as he works, letting him e.g., react to dev server issues after editing a file.
- For web development tasks, Cline can launch the site in a headless browser, click, type, scroll, and capture screenshots + console logs, allowing him to fix runtime errors and visual bugs.
- When a task is completed, Cline will present the result to you with a terminal command like
open -a "Google Chrome" index.html, which you run with a click of a button.
Tip
Use the CMD/CTRL + Shift + P shortcut 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, 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.
@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.
Local Development Instructions
- Clone the repository (Requires git-lfs):
git clone https://github.com/cline/cline.git
- Open the project in VSCode:
code cline
- Install the necessary dependencies for the extension and webview-gui:
npm run install:all
- Launch by pressing
F5(orRun->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.)