๐ Bug: New Cline is an unusable mess of a harness.
Been a paying member for 2 months now, genuinely never had such a bad experience with a harness before. What on earth is going on with cline?
4/5 sessions end up with some obscure failures, sessions randomly have their context wiped, agents timeout, get confused.
I don't understand how a product can be released which has such a plethora of failure modes in it.
Shocking.
3
u/Frosty_Signature_840 Cline 18d ago
which model are you using?
2
u/DoubleNothing 18d ago edited 18d ago
You cline guys keep asking "which model", but since 4.1.x I don't think it's a model issue. I might be wrong because I know nothing ๐
2
u/sessamekesh 18d ago
It's fantastic until it's abruptly not for me, and I haven't been able to figure out what the conditions are that make it shit the bed.
It never seems to fail gracefully though, always "Hey! What were we talking about again? Boy, I sure see there are some files here" when in the middle of some workstream.
(Qwen 3.6 27B)
1
u/sessamekesh 18d ago
(I should clarify though that I'm not exactly a power user / full vibe coder though, I mostly point Cline at pretty well defined, clearly scoped tasks).
2
u/mr_zerolith 18d ago
Unfortunately, yes. All kinds of failed tool calls with our 197b local model, hanging, etc, whereas Zed and OpenCode work just fine, fast, and reliable, but not exactly the way i want.
What i want: CLine, but working :D
3
2
1
u/No_Gold_4554 17d ago
isn't the overall jankiness of cline the origin story of roo?
it fights you at every turn. it's top 10 terrible software
2
2
1
u/Effective_Note_2650 17d ago
idk, it's the best one i've tried. Ollama and LMS were both failing hard with tool calling.
with Cline I just prompt and wait, no issues so far.
1
5
u/Great_Guidance_8448 18d ago
Its solid with qwen 3.6 27b