GILD verdict
Choose Cline if your team wants an approval-gated agent in the editors it already uses, on a model provider it already governs.
Before usage grows, fix which models engineers may pick and how much Auto Approve may run.
Cline
AI Coding Agent by Cline
+39 PositiveFit and limits
Who it fits
- Engineers want to keep VS Code, a JetBrains IDE, or a VS Code-based editor such as Cursor or Windsurf, and add an agent to it.
- Model traffic has to go to a provider you already contract with: Cline connects to Amazon Bedrock, Google Vertex AI, Azure, Anthropic, OpenAI, local runtimes such as Ollama, and any OpenAI-compatible endpoint.
- You want the agent's source open for audit: the repository is Apache 2.0, with about 71,000 GitHub stars on Oct 28, 2026.
- You want planning separated from execution: Plan mode reads and discusses without changing files, and Act mode carries the same context into edits, optionally on a different model.
Where it falls short
- There is no published team tier. The free version has no seat fees or admin console, and SSO, role-based access, and provider restrictions sit in Enterprise at a custom price.
- Organization controls for providers, MCP servers and telemetry apply in the VS Code and JetBrains extensions only. The CLI receives organization rules and workflows, and Cline Desktop receives none, so members there can pick other providers and MCP servers.
- An open GitHub bug report from October 6, 2026 says the organization telemetry switch in VS Code does not stop prompt traces on the Cline and ClinePass providers. Only each member's own reporting checkbox stops them.
- In AIMultiple's June 2026 benchmark of 10 web builds on Claude Sonnet 4.6, Cline ranked 4th of nine agents on backend checks at 69.5%. Its frontend score of 52.5% was the lowest in the field.
- The JetBrains plugin is not open-sourced, and Cline's pricing page lists it under Enterprise while JetBrains Marketplace lists it as free.
- Output quality and spend vary with each engineer's model choice until the team fixes an approved list.
Implementation reality
Pick the model path first
With your own key, requests go from the developer's environment straight to that provider, and Cline's telemetry does not record prompts. Cline credits and ClinePass route prompts through Cline to run the model. ClinePass costs US$9.99 per month at the standard rate, plus any processing fee. Cline says ClinePass buys 2 to 5 times the usage of standard API rates on popular open coding models. It publishes no numeric caps for the 5-hour, weekly and monthly windows. Decide which paths are allowed before rollout.
Set the approval policy
By default every file edit and terminal command needs approval. Auto Approve opens categories one at a time, from reading project files to running all commands. Cline keeps no fixed command allowlist; the model flags which commands need approval. YOLO mode approves everything. Cline documents a yoloModeAllowed policy for admins, but its remote configuration table lists no product that enforces it yet, so treat YOLO mode as a team rule.
Keep checkpoints on
Checkpoints are on by default and snapshot the project after each tool use into a shadow Git repository, separate from your history. Compare shows the diff for a step and Restore rolls files back. Cline's docs warn that on the largest repositories checkpoints use significant storage and slow the agent; turn them off there if sessions lag.
Check adoption and release pace
As of Oct 12, 2026 the VS Code extension shows about 5.6 million installs, Open VSX about 7.0 million downloads, and JetBrains Marketplace about 782,000 downloads; Cline reports 11M+ installs across platforms. Six extension releases shipped between Sep 22 and Oct 16, 2026 (v4.1.20 to v4.1.25). With no model pinned, the Cline provider has used Claude Sonnet 5.5 again since v4.1.26 (Oct 26), after Gemini 4 Argon in v4.1.25 (Oct 16) and Claude Sonnet 5.5 in v4.1.24 (Oct 13). OpenRouter uses Claude Sonnet 5.5, so pin the model in team settings.
What to measure in your pilot
- GILD searched Cline's docs, GitHub discussions and practitioner posts and found no Plan-first versus Act-first comparison; tag pilot tasks by starting mode and compare review rework per merged change.
- Put one engineer on ClinePass and one on your own key for two weeks; keep ClinePass only if it covers a full week of work without hitting a limit.
- Ask engineers to log which surface each pilot task ran on; if any engineer works mainly in the CLI or Cline Desktop, write a provider policy for those surfaces before rollout.
Sources
- Official documentation
- 21
- Public source
- 2
- Cline
- Cline pricing
- ClinePass
- Cline FAQ
- Cline docs: Authorization and bring your own key
- Cline docs: ClinePass
- Cline docs: Installing Cline
- Cline docs: Plan & Act mode
- Cline docs: Auto Approve & YOLO mode
- Cline docs: Checkpoints
- Cline docs: Enterprise provider configuration
- Cline docs: YOLO mode controls
- Cline docs: Telemetry
- Cline docs: Cline Enterprise
- Cline on GitHub (cline/cline)
- Cline releases on GitHub
- Cline license (Apache 2.0)
- Cline on the Visual Studio Marketplace
- Cline on Open VSX
- Cline on JetBrains Marketplace
- Cline blog: How We Migrated 11 Million Users to Cline's Biggest Harness Upgrade (Sep 2, 2026)
- AIMultiple: Agentic CLI Tools Compared: Claude Code vs Cline vs Aider (updated Jun 2026)
- GitHub issue #14863: turning telemetry off for an organization does not stop Cline-provider prompt traces (Oct 6, 2026)