Claude Code and OpenCode with local Qwen: compatible or supported?
OpenCode documents local llama.cpp. Claude Code can traverse a compatible gateway, but Anthropic does not support routing it to non-Claude models.
Practical writing on AI agents, applications and workflow automation. Assess cost, risk and business fit before committing to a build.
OpenCode documents local llama.cpp. Claude Code can traverse a compatible gateway, but Anthropic does not support routing it to non-Claude models.
Codex can use a custom provider over the Responses wire. This guide shows the minimum profile, support boundary and the Qwen result.
Bielik led one Polish RAG study and PLLuM led another. Here are the numbers, why the order reversed, and how to build an auditable company brain.
A useful coding-agent benchmark needs work requests written like ordinary issues, clean workspaces, hidden checks, retained metrics and a separate review. This method evaluates a patch before acceptance.
A patched vLLM profile won one complete Qwen Code task. llama.cpp remained the simpler fallback. Here is what the evidence covers and what it leaves open.
Wire-level reasoning effort, no fixed max_tokens, preserved thinking and task-scoped sessions removed observed failures in a home-PC experiment.
A practical local Qwen3.8-27B startup pattern: verify the profile, inspect the API, watch GPU memory, switch to a fallback and run a restart test.
Qwen recalled facts from 230,085 tokens but needed 563.4 seconds. A public 146-question Polish RAG study shows what retrieval adds.
Eight failures from a home Qwen and RTX 3090 experiment, with controls for upgrades, version changes, handover, testing and operator training.
In our measurement, DFlash2 raised median decoding from 93.3 to 120.9 tok/s while the context limit fell from 150,000 to 65,536 tokens.
One card can process requests in sequence or in parallel. We pair our task times with a public 1, 2, 4 and 8-stream RTX 3090 test.
Four clients drove the same local Qwen3.8-27B. We compare the tasks, elapsed time, hidden tests and actual code choices. OpenCode won one import; Qwen Code won the long run.
Four small tasks revealed more than one large benchmark. Qwen Code read contracts well at medium effort, but hidden tests still found a missing validation rule.
An empty folder, one sentence and local Qwen on a home RTX 3090. The first ATS dashboard took 26:03. Here are the prompt, output and complete repair cost.
Every configuration returned three planted facts, but 250k was almost ten times slower than 60k. Here is how to choose a useful context window.
Q4 leaves more room for context, Q5 uses more VRAM, and W4A16 needs a different stack. Here are the profiles that fit and what the test cannot prove.
A complete record of one home experiment with Qwen3.8-27B: serving profile, timings, tokens, energy, VRAM, coding tests, failures and limits.
Qwen3.8-27B, Bielik-11B-v3.0-Instruct and PLLuM-12B-chat-2512 compared by parameters, architecture, Polish use, licensing, hardware and deployment.
Clean fixtures, separate worktrees, hidden checks outside the agent folder, an explicit tool list, telemetry and retained diffs. We also name the gap: shell was not a full sandbox.
We decompose the real laptop -> private endpoint -> Qwen -> tool path, showing what the home experiment protected and what a company still needs.