Anomalyco/OpenCode, Aider-AI/aider, and Cline Review

I hoped anomalyco/opencode would be a decent Claude Code alternative, and that it would work with a relatively small model like `qwen2.5-coder-14b-instruct-q5_k_m` for simple coding tasks.

Unfortunately, my experience was extremely disappointing. This happened on Fedora.

Instead of responding to simple prompts, it got stuck in what appeared to be an infinite loop producing nonsense like:

> Objection > work state > active > blocked > next move...

Even the response-copying functionality didn't work, so I couldn't easily copy the output. (Using Terminator Terminal Emulator)

And no, the model itself isn't the problem. I manually called the exact same llama.cpp OpenAI-compatible endpoint with `reply with Hi`, and it correctly replied `Hi`.

I also checked the OpenCode configuration and corrected the model ID to exactly match what the OpenAI-compatible `/v1/models` endpoint reports. Same result: endless nonsense.

So something in the OpenCode integration/agent prompting is clearly going wrong in this setup.

And please don't tell me to "read the docs." I've never read a single line of Claude Code documentation and have been using Claude Code without issues for several months. If Claude can make the experience that seamless, I'd expect a project with 200k stars to provide at least a usable experience.

Maybe I'm missing something obvious, but I wasted ~20 minutes trying to get a basic setup working.

Posting this in the hope it saves someone else 20 minutes.

Tried Cline with a local Qwen2.5-Coder 14B model through llama.cpp.

Same story. The model works perfectly when called directly, but the agent integration doesn't actually execute the tools. It generates things like:

<tools> {"name": "read_files", ...} </tools>

as plain text and then just sits there until I tell it to "do it" again. It repeats the exact same fake tool call.

So instead of:

Qwen → tool call → grep/find/read → result → Qwen

I get:

Qwen → pretend tool call → nothing happens → repeat.