</>macrostackBrowse all
Tool profile · AI Coding Assistants

Cline

Top pick

The open-source agent that lives in the editor you already have.

92
sovereignty

Cline (Apache-2.0, by Cline Bot Inc.) is an autonomous coding agent that installs as a VS Code extension, a JetBrains plugin or a CLI — so you keep your editor, your extensions and your keybindings and simply add the agent. It is model-agnostic: bring your own key for Anthropic, OpenAI, Google, Bedrock and 100+ others, or point it at Ollama or LM Studio and run the whole loop on your own machine. Cline sells optional prepaid credits and an enterprise tier, but nothing about the extension requires an account, and with your own key there is no Cline backend in the request path. At roughly 4.81 million VS Code installs and 65.2k GitHub stars it is the most widely adopted open-source coding agent, and because it is published on Open VSX you can also install it inside Cursor itself.

OPEN SOURCEApache-2.0SELF-HOSTLOCAL-FIRST
LicenseApache-2.0
PricingFree and open source (Apache-2.0) — you pay only your model provider. Optional prepaid Cline credits and a paid enterprise tier exist; bring-your-own-key needs no account.
Open sourceYes
Self-hostableYes
Local-first dataYes

What it does well

  • +Keeps your existing IDE, extensions and keybindings — the smallest possible change from Cursor
  • +Bring-your-own-key with no account required: 100+ providers, or fully local via Ollama / LM Studio
  • +Plan/Act split and diffs you approve before anything is written, plus MCP tool support
  • +The most-adopted open agent in the category: ~4.81M VS Code installs, 65.2k stars, commits daily

Where it falls short

  • No inline Tab-style autocomplete — Cline is an agent, not a completion engine, and this is its most-requested missing feature
  • You manage your own API billing; long agent runs on a frontier model can cost more than a $20 Cursor seat
  • Cline's own prepaid-credits path is the promoted onboarding — bring-your-own-key takes a couple of extra settings
  • Running a capable model locally is a real hardware ask (see the hardware note)

Hardware note

Cline itself runs on anything that runs VS Code — the hardware question is only about the model. Cline's own docs put local models at 16–32 GB RAM for small quantised models, 32–64 GB for mid-size coding models and 64 GB+ for larger ones with expanded context. As a concrete anchor, Ollama's default qwen3-coder tag (30B total, ~3.3B active) is a 19 GB download with a 256K context window, so roughly 24 GB of VRAM — or a 32 GB+ unified-memory machine — is a sensible floor for comfortable agentic work. Below that, a cloud API key is usually the better call, and a local model still won't match a frontier cloud model on hard multi-file tasks.

Cline as an alternative to

Where Cline shows up in our comparisons, and how it ranked.

Cline head-to-head

Straight comparisons against the tools people weigh it against.

The Macrostack brief

New swaps, worth your inbox.

A short, occasional email when we add a high-intent alternative or ship a new head-to-head. No spam, no selling your address — unsubscribe in one click.