Benching local Qwen as a Codex validator, co-agent, and challenger

I’ve been running a local Qwen model beside Codex for coding work, and it has been useful than I expected. It's never going to be a replacement for Codex. like a second set of eyes much better than me. The workflow is roughly: * Codex does the main repo work. * Local Qwen challenges the plan. * Qwen checks for overbuilding, missed hard directives, UI/design issues, bad assumptions, and long-context misses. * I review each interaction, test and validate before next stage. This isn't a "send massive prompt, thoughts and prayers" approach. I need things to work and scale.