Comment by abustamam

12 hours ago

I'm interested in seeing how this changes folks' workflows.

For me, at work I use opus to plan, brainstorm, grill, ask questions about my codebase, etc. It is pretty good about understanding the codebase holistically and providing architecturally clean solutions that actually work. Then I use sonnet as a plan executor and it does well. Follows instructions and runs tests and just overall does great.

At home I make some toy projects using opencode go (I've standardized on deepseek 4 pro as my opus replacement) but it's pretty obvious from the amount of times I've had to fix or revert a change that broke something that it's no opus. I got similar results with kimi. Have not played too much with Qwen.

So I'm wondering what I'd use to get a similar stack at work. Folks say that this version of glm is basically Jan 2026 opus pre me f. Big if true. So would I use GLM for plan and Deepseek v4 pro/flash for execution? Or maybe Kimi or Qwen? I know I'll probably never get as good quality code as I do at work but I'm just toying around here.

I tend to mix them. Write the thing with GLM and get DS or Opus to review the finished result for issues

I use glm for all code investigations and top level system design of all kinds, and then present finding to confirm and act upon to opus. everything that burns token goes there.

the finding aren't always accurate, but it saves ton of opus token

likewise I have google ai from my photo storage, so I give claude / opencode a skill that uses gemini (agy now) command line for web searches, using their flash model line.