Summary: Cline is an open-source AI coding agent that runs inside VS Code (and Cursor, Windsurf, JetBrains and the terminal). It can read your project, edit files and run commands, but only after you approve each step. This how-to walks through installing it, choosing how to pay for the model behind it, and using the three features that make it safe to hand real work to: Plan and Act modes, checkpoints, and carefully limited auto-approve.
What Cline is, and what it isn't
Cline is an agent rather than an autocomplete tool. You describe a task in a chat panel, and Cline decides which files to read, proposes edits as diffs, and asks to run terminal commands. According to its documentation, every file creation, file edit and terminal command needs your explicit approval unless you change that yourself. The extension's source code is published on GitHub under the Apache 2.0 licence, so the tool itself costs nothing.
What you do pay for (or not) is the AI model that does the thinking. Cline doesn't ship with one model. You connect a "provider", which can be Cline's own pay-as-you-go service, its ClinePass subscription, your own API key from a company like Anthropic, OpenAI, Google, DeepSeek or OpenRouter, or a model running locally on your machine. That choice decides your costs far more than anything else, so it gets its own section below.
Cline is also not a sandbox. It works on the real files in the folder you open, and the commands it runs are real commands on your computer. The habits in this guide exist because of that.
Step 1: Install Cline in VS Code
- Open the Extensions view with Ctrl+Shift+X (Windows/Linux) or Cmd+Shift+X (Mac).
- Search for Cline and click Install. The official listing on the VS Code Marketplace, linked from Cline's docs, has the ID
saoudrizwan.claude-dev, so check for that ID rather than installing a lookalike. - Click the Cline icon (a small robot) in the Activity Bar to open the panel. If you can't find it, open the Command Palette and run Cline: Open In New Tab.
The same steps work in Cursor, Windsurf, VSCodium and Antigravity. Windsurf and VSCodium pull the extension from Open VSX, but the flow is identical. For JetBrains IDEs, install Cline from Settings → Plugins → Marketplace, restart, and open it from View → Tool Windows → Cline. If you live in the terminal, the CLI needs Node.js 20 or later (22 is recommended) and installs with npm install -g cline, followed by cline auth.
One optional tweak from the official tutorial is worth doing on day one: by default the Cline panel replaces your file explorer on the left. Drag the Cline icon into VS Code's secondary sidebar on the right (toggle it with Option/Alt + Cmd/Ctrl + B) so you can watch files change while you chat.
Step 2: Choose how you'll pay for the model
Open Cline's settings with the gear icon, pick an option in the API Provider dropdown, sign in or paste a key, and choose a model from the Model dropdown. Here is how the three main routes compare, using only what Cline's documentation states as of today:
| Option | Price | Free use and limits | Key features |
|---|---|---|---|
| Cline (usage-billing) | Pay as you go with Cline credits, added from the Cline dashboard | Models tagged FREE in the selector are part of rotating, limited-time promotions with a usage quota; they work only in the IDE extension and CLI, not through the Cline API, and that usage may be used to improve models | One sign-in with Google, GitHub or email; no API keys to manage; 100+ models on one balance; usage shown under Settings → View Usage |
| ClinePass | $9.99 per month flat | Usage is measured against a rolling 5-hour window, a weekly limit and a monthly limit; free promo models can also appear here during promotions | A curated set of open coding models (GLM, Kimi, DeepSeek, MiMo, MiniMax, Qwen and others) with 2–5x the usage you'd get at standard API rates; optional and usable alongside other providers |
| Bring your own key / local | Whatever your provider charges; local models have no per-request cost | Depends on your provider's own free tier, if any; local models depend on your hardware (Cline suggests 16–32 GB RAM for small quantized models, 64 GB+ for larger ones) | Use an existing Anthropic, OpenAI, Gemini, DeepSeek, Bedrock or OpenRouter account, a Claude Pro/Max subscription via Claude Code, or Ollama / LM Studio running on your machine |
A sensible starting order for a newcomer: try a FREE-tagged model under the Cline provider to learn the workflow, then decide. If you already pay for an API, BYOK keeps everything on one bill. If you want predictable spending on open models, ClinePass is the flat-fee option. If privacy matters most, run a local model, and in that case Cline's docs recommend turning on Use Compact Prompt under Settings → Features and keeping tasks small.
For local setups, the Ollama provider expects http://localhost:11434 and LM Studio expects http://localhost:1234, with LM Studio's server started from its Developer tab. Our LM Studio tutorial covers getting a model loaded first. If you'd rather use one API key for many cloud models, our OpenRouter free models breakdown explains its daily caps, which apply when Cline talks to OpenRouter too.
Step 3: Open a folder and plan before you build
Always open a project folder first (File → Open Folder). The docs warn that without one, Cline doesn't know where to create files. For practice, an empty folder is ideal.
At the bottom of the Cline panel there's a toggle that reads Plan or Act. The difference matters:
- Plan mode lets Cline read your code, run searches and discuss an approach, but it cannot change files or run commands.
- Act mode lets Cline edit files and run commands, still asking for approval, and it keeps the whole conversation from Plan mode, so you don't have to repeat yourself.
The workflow Cline's docs recommend scales with task size:
- Small, obvious fixes (a typo, a missing import, a config value): go straight to Act.
- Medium tasks (a new endpoint, a UI component, a bug that needs investigating): describe the goal in Plan mode, point Cline at the relevant files with
@/path/to/filementions (a trailing slash, as in@/src/components/, pulls in a folder), agree on the approach, then flip to Act. - Large, multi-file work: type
/deep-planning. Cline investigates the codebase, asks clarifying questions, writes animplementation_plan.md, and then creates a task to carry it out.
A cost tip that is easy to miss: in settings you can enable Use different models for Plan and Act, pairing a stronger reasoning model for planning with a cheaper or faster one for the edits. Cline switches models automatically when you switch modes.
A first prompt to try, adapted from the official tutorial: ask Cline, in Act mode, to build a todo app in a single HTML file with an input field, a list, checkboxes with strikethrough, delete buttons and inline CSS and JavaScript. You'll see the proposed file as a diff with green additions and an Approve / Reject pair underneath. Approve it, open index.html in a browser, then ask for a follow-up change in the same chat, such as saving tasks to local storage, and watch Cline edit the existing file instead of starting over.
Step 4: Use checkpoints as your undo button
Checkpoints are on by default. After every tool use, Cline commits a snapshot of your files to a separate "shadow" Git repository, so your own Git history stays untouched and even files Git doesn't track are captured. In the chat you'll see a Checkpoint marker with two buttons:
- Compare opens your editor's diff view for that step.
- Restore offers three choices: Restore Files (undo the code, keep the conversation), Restore Task Only (keep the code, delete later messages so you can re-prompt), and Restore Files & Task (go back completely).
The practical rule: if the conversation was useful but the code broke, restore files and ask for a different approach. If the code is fine but the chat went off course, restore the task only. Checkpoints are a safety net, not a replacement for your own commits, so commit whenever you reach a version you like.
Step 5: Teach it your rules and manage long tasks
If you keep typing the same instructions ("use TypeScript", "don't touch /legacy"), put them in a rules file. Click the scale icon at the bottom of the Cline panel, choose New rule file..., and write plain markdown. Workspace rules live in .clinerules/ (or .cline/rules/) and can be committed for your team. Cline also detects existing .cursorrules, .windsurfrules and AGENTS.md files, and each rule can be toggled on or off. The /newrule command can draft one for you.
Long sessions fill the model's context window, which makes responses slower and costlier. Two commands help: /smol (alias /compact) condenses the current conversation so you can continue, and /newtask starts a fresh task carrying over only the plan, progress, relevant files and next steps.
Step 6: Loosen auto-approve gradually
Clicking Approve on every file read gets tedious, and Auto Approve lets you skip prompts per category: reading project files, editing project files, running "safe" commands, using the browser and using MCP servers. Two details from the docs are worth knowing. First, the "all files" variants extend access outside your workspace and only work if the matching base toggle is on. Second, there is no fixed allowlist of safe commands: the model itself flags each command as needing approval or not, so "safe" is a judgement, not a guarantee.
Cline's own recommended default is to auto-approve Read project files only, and to leave edits, commands, browser and MCP off until you have a reason. If you do allow edits, keep checkpoints on. YOLO mode, under Settings → Features, approves everything, including destructive commands and Git pushes, with no confirmation. Keep it for throwaway folders.
Editor's note
Who it's for: developers and technical hobbyists who want an agent that can work across many files but still asks before acting, and anyone who wants to choose (or switch) the model and the bill behind their coding assistant. Not ideal for: people who only want inline autocomplete while typing, or anyone unwilling to review diffs and commands before approving them.
Gotchas I verified in the docs: FREE-tagged models are limited-time promotions with a quota, not a permanent free plan, and their usage may be used to improve models. .clineignore is being deprecated because it never stopped Cline reading files through shell commands, so it was never a security boundary; keep secrets out of the workspace instead. Checkpoints can use a lot of storage and slow Cline down in very large repositories; the docs suggest turning them off if you notice that. Using a local model with the default prompt may struggle, which is why the docs recommend Compact Prompt.
Common errors and fixes: "Unauthorized: Please sign in" means your session expired, so click Sign In again. The sign-in browser doesn't open: copy the URL from the Cline output panel by hand. Local model won't connect: make sure Ollama or the LM Studio server is running, check the base URL, and confirm the model is pulled or loaded. Can't reach providers at work: the VS Code extension uses VS Code's own proxy settings, while the CLI reads the standard https_proxy/http_proxy variables (and NODE_EXTRA_CA_CERTS for a custom certificate).
FAQ
Is Cline free?
The extension is free and open source. Model usage is what costs money: FREE-tagged promotional models cost nothing until their quota runs out, local models cost nothing per request, and everything else is billed by Cline credits, ClinePass ($9.99/month) or your own provider.
Can I use Cline with my Claude or ChatGPT subscription?
Cline's provider list includes Claude Code for Claude Pro/Max subscribers and an OpenAI option that supports either an API key or OpenAI Codex sign-in. Check the provider page for your plan before relying on it, since what each subscription allows is set by that company.
How is Cline different from GitHub Copilot's free tier?
Copilot is tied to a GitHub account and GitHub's plans, while Cline lets you pick any supported provider and puts an approval step in front of every action. If you want to compare, our GitHub Copilot Free in VS Code guide covers that setup.
Start in Plan mode on a small, committed project, keep checkpoints on, and only widen auto-approve once you trust what you're seeing.
See the official screenshots at the end of this post. Image credit: Cline Docs (docs.cline.bot) and our own screenshot of the public Cline checkpoints documentation page.
Last verified: 2026-10-27
Sources:
Cline Docs: Overview
Cline Docs: Installing Cline
Cline Docs: Authorization
Cline Docs: Cline (usage-billing)
Cline Docs: ClinePass
Cline Docs: Free Models
Cline Docs: IDE tutorial
Cline Docs: Plan & Act Mode
Cline Docs: Checkpoints
Cline Docs: Auto Approve & YOLO Mode
Cline Docs: Rules
Cline Docs: Using Commands
Cline Docs: Local models
Cline Docs: Networking and Proxies
Cline Docs: Deprecations
Cline on GitHub
댓글
댓글 쓰기