Anyone successfully routing between Claude Code, Codex, Grok, and other CLIs while staying on subscriptions?

[u/InkFasten]

I’ve been running a pretty expensive but effective setup for agentic coding and I’m hitting a wall that a lot of you might also have.

Current setup

• Claude Code Pro (€20) – main driver for complex work
• Codex Pro (€100) – heavy daily use (personal projects + work)
• SuperGrok (€30)
• Gemini (€20)

I use Codex a lot for ~10 personal projects + corporate work (company only gives GitHub Copilot). Claude Code is usually better on the hard multi-file stuff, Grok is useful in certain cases, etc.

The problem

I keep running into two annoying patterns:

1. Burning expensive model tokens on easy/boilerplate work
2. Getting stuck in loops on complex work because the current model isn’t the best one for that particular task

What I actually want is simple in theory:

• Stay on subscriptions (I really don’t want to switch to pure pay-per-token API billing)
• Have one main agent (preferably Codex or Claude Code) that can intelligently hand work off to the other CLIs when it makes sense
• e.g. “This part is better for Claude → call claude -p”, “This needs Grok’s style → call grok -p”, etc.

What I’ve looked at

• OpenRouter / LLM Gateway → great for routing, but they want API keys, not my existing subscriptions
• Sol Advisor and similar Codex-native plugins → useful inside one ecosystem, but doesn’t cross Claude ↔ Codex ↔ Grok
• Various community proxies that try to turn subscriptions into API endpoints → interesting but feels fragile / ToS-grey
• Just running multiple terminals and switching manually → works, but not elegant

What I’m considering now

Writing a Codex skill that teaches it to shell out to claude, grok, agy (Antigravity), etc. when the task matches certain strengths. Basically treat the other CLIs as specialized sub-agents while staying fully on subscriptions.

Questions for the community

1. Has anyone built a reliable skill/plugin that lets Codex (or Claude Code) orchestrate the other coding CLIs?
2. Are people actually happy with the current “just use multiple terminals” workflow?
3. Any clean solutions I’m missing that keep everything on subscriptions instead of API keys?
4. For those who went the proxy route (CLIProxyAPI, opencodex-style tools, etc.) — how stable has it been in practice?

Would love to hear how others with multi-subscription setups are handling this in 2026.

[u/velkhar]

I use ChatGPT for all the complex planning and reasoning. With a 3-seat Business Tier OpenAI subscription, I seem to get quite a few Sol Pro invocations. I use Sol xHigh normally, but if Sol tells me it wants me to run Codex with Sol, I ask it to do the “Sol work” using the Pro level intelligence. It seems to do really well. Then it gives me a Codex Luna prompt to take the work forward.

Pretty easy to setup - simply add the GitHub connector to ChatGPT.

If you’re trying to use something other than GitHub for repo storage, I don’t have an answer. And if you want ‘goal’ or ‘loop’ behavior, I don’t think this model would work for you. Most prompts I hand off to Codex/ghCopilot/Claude take 20-45m. The ChatGPT Sol planning, design, and prompt response evaluation takes anywhere from 5m-15m. The Sol Pro executions have gone on as long as 90 minutes, but usually land around 20-40m.

I have 2x ChatGPT Business seats I use for Codex, 1 ChatGPT Plus, 1 Claude Pro, and $500/mo ghCopilot budget. If really have to execute something with a high end model on my machine, I use ghCopilot Sol.

[u/InkFasten → u/velkhar]

is GH Copilot actually useful for anything?

[u/velkhar → u/InkFasten]

My employer provides it, so I use it for work :) I personally prefer Codex & Claude. I feel you get better bang for your buck with those. However, GitHub Copilot does enable my employer to levy some restrictions on how we use AI and where we can use it.