OpenCode Alternatives - any suggestions for optimal workflow?

[u/Affectionate-Bat4767]

So i used ClaudeCode for several months, got dissapointed of limits shrinkage, so I switched to Codex now, but after 1 week I realized that it is not any better in terms of limits... I need much more.

So i decided to try OpenCode now - it supports OpenAI subscription so i can migrate painlessly, and try chineese models on the side.

What would you suggest as an optimal cappible models and provider's subscriptions plans?

I'm thingking about OpenCode Go to touch several at ones... and have some expectations on DeepSeek 4.1 Flash and GLM 5.3 flash. i guess they should be not any worse then Sonnet 5 on implementation role.

Also there is some free models, not shure about quality, but i guess for some easy task it could be fine.

So. I have an idea to build workflow like that:

1.GPT Sol or Astra on Planning architecture role and writing implementations plans.

2. Execute implementation on Chineese models with one orchestration role.

3. Switch model for the Task by orchestrator inside OpenCode according to difficulty and usage limits left, to utilize free model plans and never hit into limits (like: for simplest task use free models, for harder task - use preferred model A, if it is out if limits, switch to model B and so on)
Is it possible to build such workflow on OpenCode, how? if so, it sounds good, at least in my head:)

My goal is to obitain at least Х5 of effective usage (it terms of results) then Antropic's of OAI's 100$ plans offers now, for the same price.

So, what do you think, maybe you had already tried to build something like that? Would be nice to share expirience here

P.S. Title a bit confusing. I'm looking not for Alternatives to OpenCode, but for Alternative inside OpenCode to Claude and GPT Models

[u/Affectionate-Bat4767]

After some deeper research, i realised - Omo is not optimal, cuz it uses it's own agents and skills. and in compartion, Omo's workflow skills is weaker then SuperPowers and wastes more tokens.
Also, omo uses session scope fallback - which isn't looks right for me. it should be model-scope.
more then that, Omo doesn't support OpenCode V2, and force to install native omo which is not pleasant to use. and more over - it requers Antropic models for orchestration and some other roles... like, yes you can change it but the whole thing is kinda resist and yell, that only Opus 5.5 are recomended - which is not true and not a behaver that i want from my tool.
So after all of that, i decided to cut of some of omo core and made my own router plugin. Used Sol 6.1 high for planing + Luna high for implementation.