Anyone is working seriously with Qwen 3.6 as a raisable sub agent for the larger

<!-- SC_OFF --><div class="md"><p>Been using ClaudeCode CLI with Opus 4.6 and many MCP's and honestly its addicting. </p> <p>Just tell it what to build and it does everything —

<!-- SC_OFF --><div class="md"><p>I am amazed by the development of locallm in the coding area. Right now im Testing Qwen3.6 27b and it works quite well, even tho this is not made

<!-- SC_OFF --><div class="md"><p>The idea is simple, if one agent is good then multiple agents working together must be better. In practice coordination between agents is an

<!-- SC_OFF --><div class="md"><p>Given the recent usage reductions in claude, people have been looking for ways to save usage.</p> <p>Obviously a local model running on a single

<!-- SC_OFF --><div class="md"><p>so as it says, I am not a FE eng, but want to do some light FE work<br /> I don't need the smartest model but need to get some work done.<br /> I

<!-- SC_OFF --><div class="md"><p>I've been thinking about why local-first AI agent architectures are getting serious enterprise traction in 2026, beyond the obvious &quot;keep

<!-- SC_OFF --><div class="md"><blockquote> <p>Wait, I need to be careful about the &quot;no_think&quot; tag in the system prompt. The system prompt says <code>/no_think</code>.

<!-- SC_OFF --><div class="md"><p>want to put a different multi-agent direction on the table because most of what i see assumes task teams.</p> <p>the dominant pattern right now: