94 sources from practitioners, by month and sentiment.
Across public accounts the read is positive. Model and provider choice is the most praised capability. Spending tokens on your own API key is the most frequent concern, followed by update regressions and results that depend on the model.
Positive, mixed and negative sources
431713
The score counts them as 40 positive, 17 mixed and 13 negative votes, one per author. See How the numbers work.
Counted for All practitioners, from 94 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1Model and Provider ChoiceAll 20 sources on it praise itBringing your own key and choosing among providers and models, including frontier APIs and local runtimes.
Switched from Cursor to VSCodium with Cline and OpenRouter; zenoprax uses any model, currently Step 3.5 Flash, for pennies, with no Cline account needed.
Published Apr 2, 2026self-described: VSCodium with OpenRouter, after Cursor
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
With work access to Gemini 2.5 Pro and Claude Sonnet 4.5, syspec compares them in the same repository through Cline's model dropdown and prefers Claude's leaner code.
Published Nov 18, 2025self-described: Developer with work-provided model access
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Calls Cline and Roo Code fantastic as normal VS Code extensions, notes they occasionally lose the terminal connection, and prefers bringing a personal key over an IDE middleman.
Published Jul 11, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Gets great results from Cline with Sonnet 3.7 on AWS Bedrock for smaller projects in popular languages, but warns purely prompt-built projects degrade as context windows saturate.
Published Apr 17, 2025self-described: Individual developer with AWS Bedrock access
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Finds Cline better than Claude Code because it runs terminal commands, uses LSP and IDE diagnostics, and works with Gemini 2.5 alongside Anthropic models.
Published Apr 12, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After extensively testing Cursor, WindSurf and GitHub Copilot, Osmani finds Cline uniquely valuable for model flexibility, Plan/Act, checkpoints, MCP extensibility and cost accounting during a session, while noting token-based pricing requires attention to model selection.
Published Jan 30, 2025self-described: Engineering work on complex systems
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
Says GPT 5 in Cline reads whatever context it is given and laser-targets the required changes; on High, with enough relevant context, it usually one-shots the solution. Finds it extremely slow but still uses it on anything nuanced.
Published Oct 16, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After a couple of months on Cline, Hofmann-Wellenhof keeps Cursor for autocomplete and codebase questions but prefers Cline whenever an agent should work more freely on the codebase.
"I still use Cursor often, mainly for its autocomplete model (e.g., via the Tab key) and for asking questions about the codebase. But when it comes to letting an agent operate more freely on the codebase, I prefer Cline."
Excerpt, Lorenz Hofmann-Wellenhof
Published Jul 22, 2025self-described: Solo; a couple of months of daily coding with Cline next to Cursor
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
Moved to Cline with Gemini 2.5 Pro and a .clinerules file after Claude Code cost US$3 to US$5 per task. It runs commands and lint checks and costs little on a personal key.
Published May 8, 2025self-described: Web app, production code changes
Practitioner account, pseudonymous; direct use; counts toward Operational control
Osmani plans in Cline with Gemini or DeepSeek and executes with Sonnet in Act mode, a split he uses to keep token costs down, and recommends Cline to Cursor and Windsurf users.
"I use Plan mode with Gemini or DeepSeek and Sonnet for Act mode."
Excerpt, Addy Osmani
Published Mar 5, 2025self-described: Personal use of Cline in VS Code
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Built a Zig tool that finds lexical illusions test-first with Cline: about 30 seconds and US$0.09 to get the first tests passing, and US$6 in OpenRouter credits for five hours of continuous work with file reads, writes and commands on auto-approve.
Published Feb 1, 2025self-described: Solo, Zig command-line tool
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Used Cline in VS Code to redesign a Go SaaS side project; productivity rose sharply, but Sonnet's context limits forced task splitting and review stayed essential.
Published Jan 26, 2025self-described: Solo, Go and Python SaaS side project
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability
On the free GLM-5.3 Flash model, Cline Desktop built a small Node.js task-list CLI. It passed all 15 tests after an initial environment issue was resolved and its handling of corrupted JSON was fixed.
"After resolving an initial environment issue and fixing how the CLI handled corrupted JSON, it successfully passed all 15 tests."
Excerpt, Shivay Lamba
Published Sep 14, 2026self-described: Solo test of Cline Desktop on coding, scheduled reviews and handoffs
Practitioner account, pseudonymous; structured test; not counted, tied to the vendor
AUMOVIO's hackathon found Cline on Claude 3.7 Sonnet in Bedrock fixed a five-day bug in minutes, but general models duplicated internal libraries, so the pilot added fine-tuned models behind MCP.
Published Jan 15, 2026self-described: AUMOVIO high-performance computer software teams, hackathon and pilot build with AWS
Vendor material; ran the rollout; counts toward Delivered outcomes, Operational control
Positive
Rahul Ramesh, Consultant Developer at Thoughtworks
Ramesh migrated a Bahmni display control with Cline and Claude 3.5 Sonnet in under an hour for under US$2, with tests at about 95% coverage, against 3 to 6 days by hand. Cline read a style guide file each session, and line-by-line code review was the most significant challenge.
"Changing a single control would normally take 3 to 6 days of manual effort, but with these tools was completed in under an hour at a cost of under $2."
Excerpt, Rahul Ramesh
"This file is then read by Cline at the start of each session to ensure that all generated TypeScript code adheres to a consistent and recognized standard."
Same speaker
Published Aug 27, 2025Thoughtworks modernization of the Bahmni hospital system front end from AngularJS to React and FHIR
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability
Positive
Dharanikumar Premkumar, Tech Lead and Application Architect at Thoughtworks
With little cloud experience, Premkumar used Cline with Claude to write the Terraform for his team's AWS platform and apply it through the AWS Terraform MCP server, reviewing every plan first. The generated README became the team's deployment playbook, though he had to cut oversized default resources.
"I again used the Cline and Claude combination to generate the Terraform configuration for its specific needs…"
Excerpt, Dharanikumar Premkumar
"Before applying anything, I meticulously reviewed the terraform plan output."
Same speaker
Published Aug 21, 2025Thoughtworks team deploying a five-service event-driven platform on AWS for an automotive client
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control
Positive
Zichuan Xiong, Global Head of AIOps at Thoughtworks
Xiong and co-authors run Cline as the triage agent in an AIOps build for a LATAM bank, using Dynatrace MCP for log context. In their eval of an engineer's Cline sessions, one root cause analysis took three MCP tool calls and reported that logs and trace data were unavailable.
"…an AI agent (Cline) performs automatic triage and recommends context-aware resolutions by retrieving log context via Dynatrace MCP…"
Excerpt, Zichuan Xiong
"The agent successfully used three MCP tool calls to diagnose the issue."
Same speaker
Published Jul 31, 2025Thoughtworks Managed Services AIOps build for a Latin American bank
After a couple of months on Cline, Hofmann-Wellenhof keeps Cursor for autocomplete and codebase questions but prefers Cline whenever an agent should work more freely on the codebase.
"I still use Cursor often, mainly for its autocomplete model (e.g., via the Tab key) and for asking questions about the codebase. But when it comes to letting an agent operate more freely on the codebase, I prefer Cline."
Excerpt, Lorenz Hofmann-Wellenhof
Published Jul 22, 2025self-described: Solo; a couple of months of daily coding with Cline next to Cursor
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
Built an Android app prototype with Cline and Claude: several thousand lines with no compile errors; it debugged issues with feedback from codethief, though its fixes needed extra rounds.
Published May 15, 2025self-described: Solo, Android prototype
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Moved to Cline with Gemini 2.5 Pro and a .clinerules file after Claude Code cost US$3 to US$5 per task. It runs commands and lint checks and costs little on a personal key.
Published May 8, 2025self-described: Web app, production code changes
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
Jos van der Westhuizen, co-founder and CEO of Coplay
After a teammate's recommendation, Cline pushed through complex changes in Coplay's 60,000-line project where Cursor failed; single threads can pass US$6, which van der Westhuizen finds worth it.
Published May 6, 2025self-described: Coplay team, 60,000-line project
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits
Positive
inheritedwisdom, Hacker News commenter speaking for their team
Their team is rolling out VS Code, Cline and Sonnet 3.7 for data engineering, keeps an architecture README referenced on every task, and reports weeks taken off estimates.
Published Mar 31, 2025self-described: Data engineering team on Databricks, early rollout
Practitioner account, pseudonymous; ran the rollout; not counted, repeats a stronger account
Built a Zig tool that finds lexical illusions test-first with Cline: about 30 seconds and US$0.09 to get the first tests passing, and US$6 in OpenRouter credits for five hours of continuous work with file reads, writes and commands on auto-approve.
Published Feb 1, 2025self-described: Solo, Zig command-line tool
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Finds Cline better than Claude Code because it runs terminal commands, uses LSP and IDE diagnostics, and works with Gemini 2.5 alongside Anthropic models.
Published Apr 12, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Places Cline in Trial as a strong supervised software engineering agent, citing Plan and Act, transparent token usage and MCP, while warning about token cost and rate limits.
Published Apr 2, 2025self-described: Technology Radar blip, April 2025 edition
Practitioner account; opinion; not counted until substantiated
Mixed
Birgitta Böckeler, Distinguished Engineer and AI-assisted delivery expert at Thoughtworks
Using agentic modes in Cursor, Windsurf and Cline on existing codebases, Böckeler steered constantly and often discarded changes, listing missteps that slow teams and hurt maintainability.
Published Mar 25, 2025self-described: Changing existing codebases with Cursor, Windsurf and Cline
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability
Plan mode made Cline click for Warmerdam, who values the token and cache transparency and checkpoint restore, with gripes about leftover terminals and missing shortcuts.
Published Jul 21, 2025self-described: Personal use, trying a new tool each week
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Finds Cline works significantly better than Cursor on complex tasks because each request is paid and context is not truncated, and values seeing how it behaves.
Published May 12, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Places Cline in Trial as a strong supervised software engineering agent, citing Plan and Act, transparent token usage and MCP, while warning about token cost and rate limits.
Published Apr 2, 2025self-described: Technology Radar blip, April 2025 edition
Practitioner account; opinion; not counted until substantiated
Positive
Shivay Lamba, AI architect, Docker Captain and CNCF Ambassador
On the free GLM-5.3 Flash model, Cline Desktop built a small Node.js task-list CLI. It passed all 15 tests after an initial environment issue was resolved and its handling of corrupted JSON was fixed.
"After resolving an initial environment issue and fixing how the CLI handled corrupted JSON, it successfully passed all 15 tests."
Excerpt, Shivay Lamba
Published Sep 14, 2026self-described: Solo test of Cline Desktop on coding, scheduled reviews and handoffs
Practitioner account, pseudonymous; structured test; not counted, tied to the vendor
Torchia tried Cline's auto-approve for everything and it worked, but on any codebase with history sets autonomy by action: full auto-approve for file reads, auto-approve with later diff review for edits in a bounded folder, manual approval for config edits, and destructive commands rejected by default.
Published Sep 2, 2026self-described: Codebases with history
Practitioner account, self-described; direct use; counts toward Operational control
Likes the balance Cline strikes between autonomy and keeping the developer involved, and was surprised it worked well with local models such as Devstral.
Published May 27, 2025self-described: Local models such as Devstral
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
Jos van der Westhuizen, co-founder and CEO of Coplay
After a teammate's recommendation, Cline pushed through complex changes in Coplay's 60,000-line project where Cursor failed; single threads can pass US$6, which van der Westhuizen finds worth it.
Published May 6, 2025self-described: Coplay team, 60,000-line project
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits
After extensively testing Cursor, WindSurf and GitHub Copilot, Osmani finds Cline uniquely valuable for model flexibility, Plan/Act, checkpoints, MCP extensibility and cost accounting during a session, while noting token-based pricing requires attention to model selection.
Published Jan 30, 2025self-described: Engineering work on complex systems
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
4Plan and Act9 of 10 sources on it praise itPlanning in a mode that cannot change files before switching to execution, optionally on a different model.
Plan mode made Cline click for Warmerdam, who values the token and cache transparency and checkpoint restore, with gripes about leftover terminals and missing shortcuts.
Published Jul 21, 2025self-described: Personal use, trying a new tool each week
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Calls Cline the dark horse of AI editors and argues engineers should spend about four times as long in Plan mode as in Act mode, reviewing the plan first.
Published May 20, 2025self-described: Founder of Pocket, works on Vision Pro at Apple
Practitioner account, pseudonymous; direct use; counts toward Operational control
Osmani plans in Cline with Gemini or DeepSeek and executes with Sonnet in Act mode, a split he uses to keep token costs down, and recommends Cline to Cursor and Windsurf users.
"I use Plan mode with Gemini or DeepSeek and Sonnet for Act mode."
Excerpt, Addy Osmani
Published Mar 5, 2025self-described: Personal use of Cline in VS Code
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After extensively testing Cursor, WindSurf and GitHub Copilot, Osmani finds Cline uniquely valuable for model flexibility, Plan/Act, checkpoints, MCP extensibility and cost accounting during a session, while noting token-based pricing requires attention to model selection.
Published Jan 30, 2025self-described: Engineering work on complex systems
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
After a couple of months on Cline, Hofmann-Wellenhof keeps Cursor for autocomplete and codebase questions but prefers Cline whenever an agent should work more freely on the codebase.
"I still use Cursor often, mainly for its autocomplete model (e.g., via the Tab key) and for asking questions about the codebase. But when it comes to letting an agent operate more freely on the codebase, I prefer Cline."
Excerpt, Lorenz Hofmann-Wellenhof
Published Jul 22, 2025self-described: Solo; a couple of months of daily coding with Cline next to Cursor
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control
Places Cline in Trial as a strong supervised software engineering agent, citing Plan and Act, transparent token usage and MCP, while warning about token cost and rate limits.
Published Apr 2, 2025self-described: Technology Radar blip, April 2025 edition
Practitioner account; opinion; not counted until substantiated
Every concern practitioners raise, most raised first.
1Token Spend on Your Own Key17 of 29 sources on it raise it as a concernWhat Cline costs in API usage when every request is billed to the team's own provider or credits.
After moving to Cline 4.1.25's Next engine, prompt caching stopped advancing during tool loops, so a 70,000-token task paid the full input rate on every step; reverting to 4.0.12 restored cheap loops.
"Because of this, a 70k context task bills the full $2.00/M input rate on every single autonomous step instead of the $0.10/M cached rate."
Excerpt, nicolaspe
Published Oct 24, 2026self-described: VS Code extension on Windows with an Anthropic API key
Counted 1,156 calls across 10 Desktop sessions: failed sessions kept running for up to 23 hours, one used 112 million input tokens, and models labeled free drew the credit balance negative.
Published Sep 18, 2026self-described: Cline Desktop with ClinePass and Cline credits
Practitioner account, pseudonymous; direct use; counts toward Reliability, Cost predictability and limits
Burned US$200 in a weekend on a Rust side project with Cline and Claude, then US$30 in 30 minutes on Gemini 2.5 Pro, and moved to DeepSeek and local models.
Published May 15, 2025self-described: Solo, Rust side project
Practitioner account, pseudonymous; direct use; not counted, takes no position
Says Cline "seems to be the best thing", suspecting it does no context trimming under the hood to keep costs down. For the same reason, watching its token and dollar counter tick as it works is not exactly fun.
Says Cline gets better results than Cursor or Copilot because it does not trim context, though asaddhamani has spent US$20 of API usage in a single day.
Published May 9, 2025self-described: Compared with Cursor and Copilot, on a personal API key
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Places Cline in Trial as a strong supervised software engineering agent, citing Plan and Act, transparent token usage and MCP, while warning about token cost and rate limits.
Published Apr 2, 2025self-described: Technology Radar blip, April 2025 edition
Practitioner account; opinion; not counted until substantiated
Building with Cline and Roo, timbritt warns the tools waste time and money without a solid approach, and recommends a memory bank and strict test-first workflow to contain looping spend.
Published Apr 1, 2025self-described: Solo, building applications
Practitioner account, pseudonymous; direct use; counts toward Reliability
Provisioned the team with Claude Code subscriptions after calling API pay-per-use prohibitively costly; notes Cline's Claude Code provider but finds Claude Code as good or better.
Published Aug 8, 2025self-described: Team lead choosing tools for the team
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Used Cline and Roo with Sonnet through OpenRouter, then moved to Claude Code on the Max plan, which costs less than API credits and gives better results.
Published Jul 14, 2025self-described: Cline and Roo Code on OpenRouter, then Claude Code on the Max plan
Practitioner account, pseudonymous; direct use; not counted, takes no position
A junior developer shipped an LLVM change after Cline found the 5 places to edit across 10,000+ files, and notes Claude costs hundreds of dollars a month.
Published May 22, 2025self-described: Junior developer contributing to LLVM
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Discussed without concern, 12
Positive
Jos van der Westhuizen, co-founder and CEO of Coplay
After a teammate's recommendation, Cline pushed through complex changes in Coplay's 60,000-line project where Cursor failed; single threads can pass US$6, which van der Westhuizen finds worth it.
Published May 6, 2025self-described: Coplay team, 60,000-line project
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits
Used Cline heavily at work with over US$1,000 a month in token spend before switching to Claude Code, and says the underlying Claude model matters most.
Published Aug 22, 2025self-described: Developer at a company
Practitioner account, pseudonymous; direct use; not counted, takes no position
Finds Cline works significantly better than Cursor on complex tasks because each request is paid and context is not truncated, and values seeing how it behaves.
Published May 12, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Moved to Cline with Gemini 2.5 Pro and a .clinerules file after Claude Code cost US$3 to US$5 per task. It runs commands and lint checks and costs little on a personal key.
Published May 8, 2025self-described: Web app, production code changes
Practitioner account, pseudonymous; direct use; counts toward Operational control
Osmani plans in Cline with Gemini or DeepSeek and executes with Sonnet in Act mode, a split he uses to keep token costs down, and recommends Cline to Cursor and Windsurf users.
"I use Plan mode with Gemini or DeepSeek and Sonnet for Act mode."
Excerpt, Addy Osmani
Published Mar 5, 2025self-described: Personal use of Cline in VS Code
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Built a Zig tool that finds lexical illusions test-first with Cline: about 30 seconds and US$0.09 to get the first tests passing, and US$6 in OpenRouter credits for five hours of continuous work with file reads, writes and commands on auto-approve.
Published Feb 1, 2025self-described: Solo, Zig command-line tool
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
After extensively testing Cursor, WindSurf and GitHub Copilot, Osmani finds Cline uniquely valuable for model flexibility, Plan/Act, checkpoints, MCP extensibility and cost accounting during a session, while noting token-based pricing requires attention to model selection.
Published Jan 30, 2025self-described: Engineering work on complex systems
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Cline itself is free and shows token use and cost per task. Spend limits sit with the provider account, Cline credits, or ClinePass quotas. A report of high spend does not establish that spend cannot be capped. Authorization
2Reliability and Update Regressions12 of 15 sources on it raise it as a concernExtension bugs, hangs, failed edits, and behavior changes after updates.
After moving to Cline 4.1.25's Next engine, prompt caching stopped advancing during tool loops, so a 70,000-token task paid the full input rate on every step; reverting to 4.0.12 restored cheap loops.
"Because of this, a 70k context task bills the full $2.00/M input rate on every single autonomous step instead of the $0.10/M cached rate."
Excerpt, nicolaspe
Published Oct 24, 2026self-described: VS Code extension on Windows with an Anthropic API key
Sees no improvement since Cline's new harness reached full rollout in August 2026; agents abandon its tools after one try and fall back to raw commands.
Published Sep 4, 2026
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
On a real Linux project with auto-approve on, Cline froze twice on its first task when shell escaping and a multi-line commit message broke its terminal handling.
Published Jul 11, 2026self-described: Real project on Kubuntu Linux
Practitioner account, self-described; direct use; counts toward Reliability
Mixed
stefanCCS, Cline user filing a GitHub issue, self-described
Setting up an open-weight model trial, Scott Logic's team shortlisted three coding agents and chose OpenCode. Cline was dropped after the team hit bugs and missing features while trialling it.
"Cline had a couple of issues/omissions and bugs we ran into while trialling."
Excerpt, Robat Williams
"We shortlisted some well known ones to briefly trial: Pi, OpenCode and Cline. OpenCode was our agent of choice."
Same speaker
Published Jul 8, 2026Scott Logic engineering team running A/B trials of AI coding setups on open-source issues
Practitioner account, self-described; direct use; not counted, takes no position
Spent over an hour failing to connect an MCP server on a fresh Cline 4.0.0 install because settings went to a file it no longer read. Then lewisl reverted to 3.89.2 and wrote that the release showed the team could not be trusted.
Published Jun 27, 2026self-described: Fresh install of Cline 4.0.0 with an MCP server
Practitioner account, pseudonymous; direct use; counts toward Reliability, Adoption and upkeep
Counted 1,156 calls across 10 Desktop sessions: failed sessions kept running for up to 23 hours, one used 112 million input tokens, and models labeled free drew the credit balance negative.
Published Sep 18, 2026self-described: Cline Desktop with ClinePass and Cline credits
Practitioner account, pseudonymous; direct use; counts toward Reliability, Cost predictability and limits
Cline cuts command output at 8,000 characters and file reads at 50,000, forcing extra round trips and chunked edits; rvnlord asks for configurable limits.
Published Aug 14, 2026self-described: C# .NET developer
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Adoption and upkeep
Plan mode made Cline click for Warmerdam, who values the token and cache transparency and checkpoint restore, with gripes about leftover terminals and missing shortcuts.
Published Jul 21, 2025self-described: Personal use, trying a new tool each week
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Calls Cline and Roo Code fantastic as normal VS Code extensions, notes they occasionally lose the terminal connection, and prefers bringing a personal key over an IDE middleman.
Published Jul 11, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
With qwen2.5-coder:32b on Ollama, Cline ignored the model's JSON tool calls as plain text, so the model looped on the same call until a custom rule forced Cline's XML format.
"However, Cline's current streaming parser completely ignores this raw JSON output and treats it as plain conversational text."
Excerpt, LittleRainC
Published May 18, 2026self-described: Cline 3.83.0 in VS Code on a local Ollama model
Uses Cline with a local Qwen 3 32B at work, where cloud AI is not allowed; basic requests loop without useful output, while cloud Codex handles complex tasks.
Published Jan 9, 2026self-described: Work environment without cloud AI
Practitioner account, pseudonymous; direct use; counts toward Operational control
Running Qwen3 Coder on Cline v3.26.7, asks Cline to remove its warning that recommends Claude 4 Sonnet for less capable models, saying it made open-source LLMs impossible to use. Says they will switch tools soon if it continues.
Published Aug 31, 2025self-described: Qwen3 Coder
Practitioner account, pseudonymous; direct use; counts toward Reliability, Operational control
AUMOVIO's hackathon found Cline on Claude 3.7 Sonnet in Bedrock fixed a five-day bug in minutes, but general models duplicated internal libraries, so the pilot added fine-tuned models behind MCP.
Published Jan 15, 2026self-described: AUMOVIO high-performance computer software teams, hackathon and pilot build with AWS
Vendor material; ran the rollout; counts toward Delivered outcomes, Operational control
Uses Cline with .clinerules for React work, narrows tasks so Gemini Flash or Haiku can handle them, saw no gain from paid models, and finds Gemini 2.5 Pro over-reaches.
Published May 8, 2025self-described: Frontend React and TypeScript
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
With tool auto-approval on by default in Cline Desktop, an agent set request capture to full without asking, writing credentials to disk in 75 of 320 captures. A later run used a key the user never shared for 11 paid requests.
"A later agent run then read an API key that the user had never shared and used it to make 11 paid requests on the user's own provider account, without asking and without mentioning cost."
Excerpt, IRwDONE
Published Oct 19, 2026self-described: Cline Desktop beta on Windows, daily sessions in Act mode
Practitioner account, pseudonymous; direct use; counts toward Operational control
Reports that in Act mode on Windows, a cleanup command run through Cline's run_commands tool had mangled PowerShell quoting, so rmdir ran against the data drive root and deleted about 1.5 TB of photos, videos and documents. Only code under git and pushed was recovered.
Published Oct 6, 2026self-described: VS Code on Windows, Act mode with run_commands
Practitioner account, pseudonymous; direct use; counts toward Reliability, Operational control
Torchia tried Cline's auto-approve for everything and it worked, but on any codebase with history sets autonomy by action: full auto-approve for file reads, auto-approve with later diff review for edits in a bounded folder, manual approval for config edits, and destructive commands rejected by default.
Published Sep 2, 2026self-described: Codebases with history
Practitioner account, self-described; direct use; counts toward Operational control
Mixed
BroadlyWhitaker, Cline user filing a GitHub issue, self-described
Showed a prompt injection that makes Cline read a .env file and leak it through a rendered image, recommending auto-approve off by default; unfixed 90+ days after disclosure.
Published Aug 27, 2025self-described: Security testing of Cline
With only safe commands auto-approved, Cline ran an eval of a base64-encoded command hidden in content it fetched from an API. The getsec team used this to show it could be tricked into running arbitrary code.
Published Jun 6, 2025self-described: Team building an MCP server for internal APIs, Cline with Gemini 2.5 Flash
Practitioner account, pseudonymous; structured test; counts toward Operational control
Mixed
chezsmithy, for development teams in a regulated company
Says their highly regulated company vets every MCP server through infosec before developers get it from an internal source, and Cline 3.4.0's MCP marketplace makes pulling unapproved code too easy. Asks for a way to disable the marketplace or redirect it to an internal registry.
Published Feb 20, 2025self-described: Highly regulated industry that vets every MCP server through infosec before release
Practitioner account, pseudonymous; ran the rollout; counts toward Operational control
After the 4.x SDK migration, Cline edits files while still in Plan mode and task quality dropped, on DeepSeek through a self-hosted LiteLLM.
Published Aug 10, 2026self-described: DeepSeek through a self-hosted LiteLLM proxy
Practitioner account, pseudonymous; direct use; counts toward Reliability, Operational control
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.In the IDE extensions, edits and commands wait for approval until a team turns on Auto Approve. The CLI auto-approves by default, and no Cline product yet enforces the organization YOLO-mode setting. Enterprise provider configuration
5Context Management6 of 8 sources on it raise it as a concernKeeping the right information in the model's context across long sessions, compaction, and large files.
Cline cuts command output at 8,000 characters and file reads at 50,000, forcing extra round trips and chunked edits; rvnlord asks for configurable limits.
Published Aug 14, 2026self-described: C# .NET developer
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Adoption and upkeep
Used Cline in VS Code to redesign a Go SaaS side project; productivity rose sharply, but Sonnet's context limits forced task splitting and review stayed essential.
Published Jan 26, 2025self-described: Solo, Go and Python SaaS side project
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability
Gets great results from Cline with Sonnet 3.7 on AWS Bedrock for smaller projects in popular languages, but warns purely prompt-built projects degrade as context windows saturate.
Published Apr 17, 2025self-described: Individual developer with AWS Bedrock access
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Adopting Cline at work on an enterprise model plan with a 1M-token window, a_e_k finds it holds up to about 700,000 tokens in hands-on pair-programming mode.
Published Mar 14, 2026self-described: Developer at a company with an enterprise model plan
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Questions the sources split on, with the count on each side.
Evidence remains mixed
Is paying per token on your own key better value than a flat subscription?
106
Pay per token, 10 sources
Some prefer paying the provider directly, with any model and no middleman, because costs stay low for bursty or careful use.
Flat subscription, 6 sources
Others moved to a subscription product such as Cursor or Claude Code because per-token spend on heavy use ran too high.
Evidence remains mixed
Do cheaper, open-weight, or local models do the job in Cline?
113
Cheaper models work, 11 sources
Some report good results from DeepSeek, Qwen, Devstral, or Gemini Flash at a fraction of frontier prices.
Frontier models needed, 3 sources
Others found cheaper or local models looped or failed Cline's tool calls, and fell well short of Claude.
Evidence remains mixed
How much should Cline do before a human approves the next step?
103
Approve each step, 10 sources
Some keep approvals on and steer turn by turn, rejecting or editing changes before Cline moves on.
Auto-approve and review at the end, 3 sources
Others auto-approve edits and commands and let Cline iterate until tests pass, then review the result.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 8 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
14 sources. These accounts focus on spend control on your own keys, approval policy, governance, and what changes when Cline moves from individual use to a team.
Individual builders
80 sources. These accounts focus on model and provider choice, spend on personal keys, speed, and how Cline performs in self-directed work.
All practitioners
94 sources. This count includes every practitioner: individual builders and the few team and leadership accounts together.
94 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders80 sources, counted here
Emphasizes Model choice and spend on personal keys, then reliability after updates
Very small team2 to 10 engineers, or a team of unstated size5 sources, counted here
Emphasizes Command safety and MCP vetting, with shared rules files
Professional team11 to 50 engineers, or a named company's team6 sources, counted here
Emphasizes Pilots on company model accounts, and model limits on internal code
Technical leadershipLeaders and advisory boards assessing tools across teams3 sources, counted here
Emphasizes Supervision and token cost in a trial
Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Individual builders emphasize model choice and what their own keys cost. Team and leadership accounts turn to supervision. They ask which commands and MCP servers the agent may run, and whether per-token spend beats a flat-rate seat across the team.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 94 sources. Change group
112 sources for this group, 18 of them documentation
Developer Communities74, 66% of 112 sources
Engineering Blogs & Reviews19, 17% of 112 sources
Product Documentation18, 16% of 112 sources
Talks & Podcasts1, 1% of 112 sources
Older evidence is retained when it still applies. Sources that depend on a changed release, a fixed bug, or a closed issue stay in the history, marked Needs a recheck.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Cline now casts no vote; it still counts toward its topics and is listed, and 18 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders move from +33 to +37 and all practitioners from +35 to +39.
Builds the first Cline evidence base from public sources only. Every source links to the page it comes from and names its author and publication date.
Shows a finding for an audience only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Drops the Tools and MCP praise theme, the Evaluated as an engineering agent statement, and the disagreement on whether Cline saves time overall, since none reaches those minimums.
Shows the five concerns most often raised; Requires Strong Review, raised as a concern by 4 sources, is not shown.
Checks every documentation page against Cline's current docs.
October 12, 2026 revision: removes 11 sources from publishers outside the source standard or dated before 2025 and one evaluation that was not a first-hand account. Adds AUMOVIO's AWS case study and four GitHub accounts from teams and users. Ends the evidence window at the newest source, October 6, 2026.
Counts a GitHub issue as mixed unless its author rejects or abandons Cline. Eight bug reports move from negative to mixed; three stay negative because their authors stopped using Cline or rejected it.
Oct 25, 2026: adds 7 sources from outside Hacker News. They include X posts by Addy Osmani and Shivay Lamba, a Substack post, and Adnan Khan's research on the compromised Cline CLI 2.3.0 release. Three GitHub issues cover local-model tool calls, credentials written to disk under auto-approval, and prompt caching in the Next engine. The evidence window now ends at October 24, 2026.
Method
A running review of what engineering teams report about Cline, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +37 positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +37 Positive; with one vote per author it read +35 Positive. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +35 Positive and now reads +39 Positive.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 8, individual builders 4 of 65, all practitioners 4 of 73.
Limits
These figures describe reviewed sources. They do not represent all Cline users. GILD searched Hacker News through its API, issues on cline/cline, named engineering blogs and newsletters, independent security research, X posts by named engineers, and AWS customer accounts. Reddit is not in this record. 14 of the 94 sources speak for a team or a technical leader, one of them an AWS-published customer account labeled as a vendor case study. None describes an organization-wide rollout. GitHub issues make up 11 of the 31 sources from 2026, so a bug report counts as mixed unless its author rejects or abandons Cline.
Sources record the Cline version, provider, and model inconsistently; each source shows what it states. Sources that depend on behavior Cline has since changed, such as closed issues and a disclosed vulnerability, are marked Needs a recheck.
Every count, and the sources behind it
19 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Token Spend on Your Own Key. Cline itself is free and shows token use and cost per task. Spend limits sit with the provider account, Cline credits, or ClinePass quotas. A report of high spend does not establish that spend cannot be capped. Authorization, checked Oct 12, 2026
Approvals and Safety. In the IDE extensions, edits and commands wait for approval until a team turns on Auto Approve. The CLI auto-approves by default, and no Cline product yet enforces the organization YOLO-mode setting. Enterprise provider configuration, checked Oct 12, 2026