* ci: migrate SDK publish workflows to repo root Move publish-cli.yaml, publish-sdk.yaml, and test.yml (renamed to sdk-test.yml) from sdk/.github/workflows/ to the repo root so GitHub Actions actually picks them up. Adapt them to run with cwd sdk/ via workflow-level defaults.run.working-directory, repoint repo guards from cline/sdk to cline/cline, switch publish-sdk's nested test call to sdk-test.yml, add path filters on sdk-test.yml so it doesn't fire on extension-only PRs, and re-enable NPM_CONFIG_PROVENANCE now that cline/cline is public. Update the publish-cli skill with a cwd note so the documented release commands keep working from sdk/. * ci: remove legacy CLI publish workflows The legacy publish chain (publish-cli-trusted.yaml dispatching into npm-main.yaml + npm-nightly.yaml) publishes the old cli/ folder to the same cline npm package the new SDK CLI is taking over. Leave both wired up and a maintainer could accidentally publish an old build over the handoff. Remove the dispatcher, the two callees, the PR-preview tarball workflow (pack-cli.yml + build-cli-artifact.sh), the TUI test workflow that only fed into them, and the npm packaging script those workflows shared. The cli/ source itself is left in place for a separate removal PR. * chore: remove legacy CLI dev and eval helpers With the legacy CLI publish workflows gone, the surrounding dev and eval glue that only existed to feed those workflows is also dead. Delete tests/e2e/cli/ (TUI tests), evals/smoke-tests/ (CLI smoke evals), and the cline-evals-regression.yml workflow that drove them. Trim the root package.json scripts that pointed at this infra: - cli:link, cli:build, cli:run, cli:build:production, cli:watch, cli:test, cli:dev, cli:unlink (all delegated into cli/) - compile-standalone-npm and postcompile-standalone-npm (only the removed npm-main/npm-nightly workflows called them) - test:e2e:cli:tui (only the removed cli-tui-tests.yml called it) - eval:smoke:*, which chained through cli:build + cli:link Drop the trailing `cd ../cli && npx tsc --noEmit` segment from check-types so the root typecheck stops walking into cli/. The cli/ source itself stays in place for a separate removal PR. * docs(evals): note removed smoke-tests layer The evals/README.md and evals/ARCHITECTURE.md were structured around smoke-tests as Layer 2 of the pyramid. With evals/smoke-tests/ and the eval:smoke scripts gone, those references are stale. Add a top- of-doc banner pointing at the removal rather than gutting both files in this PR; a follow-up can scrub the structure when the framework is updated for the new SDK CLI. * chore(evals): restore smoke-tests, disable workflow pending rewire The smoke-test scenarios in evals/smoke-tests/ are CLI-agnostic — each scenario is just a config.json prompt plus optional template files — so they're worth preserving across the legacy CLI sunset. Restore the directory and the cline-evals-regression.yml workflow, but reduce the workflow's triggers to workflow_dispatch only so it doesn't auto-run in its current legacy-CLI-coupled form. Add a header comment pointing at the rewire work. Update the evals/README.md and evals/ARCHITECTURE.md banners from "removed" to "temporarily disabled" to match reality. Wiring the workflow at the new SDK CLI (and restoring the eval:smoke root scripts) is left for whoever picks up the eval framework refresh. * chore(evals): restore eval:smoke:run for ad-hoc smoke checks The runner (`evals/smoke-tests/run-smoke-tests.ts`) shells out to whichever `cline` is on $PATH, so it already works against the new SDK CLI once `npm i -g cline` installs it. Add back just the single `eval:smoke:run` script so docs and manual validation have a working entrypoint. The build-and-link chain (`eval:smoke:build`, `eval:smoke`, `eval:smoke:ci`) stays out — those need rewiring before they function. Update the README/ARCHITECTURE banners accordingly. * fix(ci): update SDK npm repository metadata * fix(ci): tighten SDK publish workflows
Cline
Meet Cline, an AI assistant that can use your CLI aNd Editor.
Thanks to Claude 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.
- 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
Follow this guide to open Cline on the right side of your editor. This lets you use Cline side-by-side with your file explorer, and see how he changes your workspace more clearly.
Use any API and Model
Cline supports API providers like OpenRouter, Anthropic, OpenAI, Google Gemini, AWS Bedrock, Azure, GCP Vertex, Cerebras and Groq. 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.
Run Commands in Terminal
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.
Create and Edit 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.
Use the Browser
With Claude 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.
"add a tool that..."
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.
- "add a tool that fetches Jira tickets": Retrieve ticket ACs and put Cline to work
- "add a tool that manages AWS EC2s": Check server metrics and scale instances up or down
- "add a tool that pulls the latest PagerDuty incidents": Fetch details and ask Cline to fix bugs
Add Context
@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
Checkpoints: Compare and Restore
As Cline works through a task, the extension takes a snapshot of your workspace at each step. You can use the 'Compare' button to see a diff between the snapshot and your current workspace, and the 'Restore' button to roll back to that point.
For example, when working with a local web server, you can use 'Restore Workspace Only' to quickly test different versions of your app, then use 'Restore Task and Workspace' when you find the version you want to continue building from. This lets you safely explore different approaches without losing progress.
Contributing
To contribute to the project, start with our Contributing Guide to learn the basics. You can also join our Discord to chat with other contributors in the #contributors channel. If you're looking for full-time work, check out our open positions on our careers page!
Enterprise
Get the same Cline experience with enterprise-grade controls: SSO (SAML/OIDC), global policies and configuration, observability with audit trails, private networking (VPC/private link), and self-hosted or on-prem deployments, and enterprise support. Learn more at our enterprise page or talk to us.