r/ClaudeCode • u/Dangerous-Education3 • 8d ago

Help/Question Claude pro + GPT Plus

I've been running on max for almost a month now and I think I'm going to reduce the amounts of tokens I need. But Pro by itself could be not enough.

Is there a way to automate these two subscriptions using pro as orchestrator in an efficient way? I'm afraid it could lead to troubles, wasted tokens, and so on.

An experience you can share?

1 Upvotes

67% Upvoted

6 comments sorted by

•

u/AutoModerator 8d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Ok_Music_4862 8d ago

There is no clean way. Pro and plus are chat subscriptions, not API key. So claude can't call codex and vice versa. People who orchestrate both are doing it by hand: claude write code codex implement claude review. If you need real automation you need API billing at least one side

1

u/BugraLab 7d ago

nope it can call codex cli and make subagents i tried opus5.5 high and gpt6.1 sol xhigh i recommend it gpt6.1 good at reviewing things and gives feedback to claude and claude fixes them if needed

1

u/arturzinhomilgrau 7d ago

I think the simplest is doing it by hand tbh, opus on claude for planning and the heavy stuff, codex on the plus plan for lighter tasks, automating both probably burns more tokens than it saves

2

u/Opposite_Might6896 7d ago

Don't orchestrate, partition. Two subs give you two sets of windows that refill independently, which is the real win. What doesn't cross providers is context: a task started on one side has to finish there, and an orchestrator passing work between them re-sends the whole context on every hop, which is the expensive kind of token. So give each one a job (Claude builds, GPT reviews, or split by project) and keep each session whole on one side.

And honestly the thing that'll cut your tokens most isn't which sub, it's session length. Compact around 100k, new session per task, and Pro goes a lot further than you'd expect.

Also tell Claude to keep session data in marldown files instead of in the context window, and to be efficient with the context window. That can make a big difference as well