The Harness That Burned350 Euros in a Day — Cline Users' Bill

A title went up on r/CLine. "Cline+Gemini2.5 Pro-Preview — API cost of350 euros in one day."

The body carries an even more chilling side fact. "The Cline screen showed about160 euros on April7, but the actual bill was different. The display itself isn't accurate."

There's also a thread from someone trying Cline for the first time. "I handed work to a2000-line index.html. Turned off codebase indexing, didn't turn on auto-approve. Thought100 to200k tokens would do it. When it finished, 2.3 million tokens."

This post doesn't lead with praise for Cline's abilities. It reads the cost and failure records users actually wrote down first.

1. Where the cost loses control

Context oversupply. A paid user's (2 months) assessment: "The worst experience of any harness I've used. Four out of five sessions end in an error. The context suddenly empties, the agent times out and gets confused."

Plan mode duplicate output. A bug report: "In Plan mode, after outputting the needed information, it re-outputs the same information without user input. Cost doubles or more." A comment noting it was repeatedly confirmed on Gemini2.5 Pro.

Behavior change after a version upgrade. "Upgraded to Cline4.0.x and it's completely different. It reads dozens of files and sits in 'Thinking...' for15 minutes or more. It burns a lot of tokens, and responses come back like dense technical documents packed with the project's internal details."

Cost display bug. "I use Opus4.5 at $50–75 a day, but per-task cost is stuck at $0.00." When the dashboard is your cost-control tool, this bug is fatal.

2. What justifies this cost

The other side of the same thread: "Zed and OpenCode are fast and stable, but they're not the way I want. What I want is a working Cline."

Cline's strengths repeat in the user records. The edit-and-confirm UX inside VSCode, the breadth of model choice, the separation between plan and execution modes. The problem is that those strengths pair up with uncontrolled context growth.

User workarounds for cost control have already become culture. "Moved to OpenRouter and set a cost cap." "GCP lets you bankrupt yourself." "Prompt caching optimization is the key to low cost."

3. Rules for using Cline

Practical rules pulled from the user records.

1. Put the spend limit outside the harness. Even if the display says $0.00, the billing keeps running.
2. Restrict context to files, and start with indexing off. The2.3-million-token case is a textbook of control failure.
3. Check whether Plan mode has duplicate output. The same response twice means double the cost.
4. Re-verify behavior after a version upgrade. The record on4.0.x is "it reads more and thinks longer."
5. Cut the context per task. Context wipes in long sessions are recorded as the harness's chronic illness.

4. Conclusion — a strong tool, a weak budget

The user record on Cline compresses into one line. Its hand as an agent is strong; its accounting department is weak.

The experience of changing code inside VSCode is still top-tier. But the token consumption, context growth, duplicate output, and version-by-version behavior changes happening inside a session have to be controlled by the user directly. That350-euro-a-day bill doesn't come because Cline can't do the work — it comes because the harness isn't a cost watchdog.

If you're planning to use Cline: set your model cost policy first, and run Cline under that policy. Reverse the order and the bill arrives first.

Related posts: Aider user reviews · OpenCode user reviews · Cline agent hub entry

Sources

• Daily cost: Cline+Gemini2.5 Pro-Preview350€ API cost in one day (r/CLine,2025-04)
• Token burn: Why does Cline burn through tokens? (r/CLine,2026-06)
• Plan mode bug: Serious bug in Plan mode (r/CLine,2025-05)

-4.0.x behavior change: Upgraded to Cline4.0.x (r/CLine,2026-07)

• Overall complaint: Cline is an unusable mess of a harness (r/CLine,2026-08)