№ 0211Reddit post
Muse Glimmer as code reviewer in a multi-model pipeline
A Claude Code-orchestrated pipeline where Qwen 3.8 27B writes code, Muse Glimmer sanity-checks it, and DeepSeek arbitrates disagreements; a tool-allowlist fix cut payloads 161KB to 24KB.
u/Graemer71 runs Claude Code as orchestrator, DeepSeek 4.1 Flash for planning, Qwen 3.8 27B Q8 for boilerplate and Muse Glimmer to sanity-check code and push issues back. After a token spike, a diagnostic server showed the --tools allowlist cut tools from 55 to 7 and payloads from 161KB to 24KB.
Found out why Claude was burning so many tokens when just orchestrating.
OK, for context, I have Claude Code desktop app driving the CLI and orchestrating the code and verification tasks to try to save tokens. So Claude runs things, a Deepseek 4.1 Flash (cloud) session does the planning, Qwen 3.8 27b Q8 does the boiler plate coding and Muse Glimmer sanity checks the code and pushes any issues back to Qwen. If there are issues Qwen and Glimmer can't agree on, Deepseek validates. If Deepseek can't sort it out, it goes back to Claude. This had been working fine, but then in the last few days token use spiked, tasks that used to take 10 minutes were taking an hour or more and Qwen started going into more and more reasoning loops. It seems that since I last checked (on 12th September) the CLI changed. I used to strip unnecessary tool calls from the prompt using --disallowedTools and enabledPlugins: false. It would seem that these no longer work. In the end I got Claude to build a request-dumping diagnostic server, that actually measured the payload bytes, and confirmed --tools (an allowlist) is the flag that works now: 55→7 tools, 161KB→24KB, byte-verified. It also caught something specific to my workflow running the wrapper from inside an already-active
