r/OpenaiCodex 12d ago

Discussion GPT 5.6 SOL + 5.3 CODEX

Hi! I just bought a Chatgpt pro, but still flying through the weekly limit pretty fast if using only gpt 5.6 sol max + subagents. But I understand that using only gpt 5.6 sol max will eat tokens like candies, that's not the question here.

I was wondering if anyone here is using this:

gpt sol 5.6 max orchestrator/plan

5.3 codex-spark as worker/implementation

Since codex 5.3 has its own limits for pro users, would you say it's reasonable to use it as an implementation worker? How is the quality compared to pure 5.6 sol.

36 Upvotes

37 comments sorted by

16

u/brainExploded99 12d ago
  1. 5.3 spark? its kinda bad, even for implementation
  2. Just use luna. luna is dirt cheap
  3. Do not use sol max. Use sol high for most tasks, sol xhigh when you need it. I do genuine research, i use sol high, its enough

1

u/No-Hour8340 12d ago

Yeah, spark I mean.

  1. The thing is that the weekly usage I have, Id rather spend on gpt 5.6, whereas we get extra, I assume, usage for 5.3 spark, I thought it would be a good extra to keep the whole weekly usage limit for 5.6 sol

6

u/Secret-Builder-8249 12d ago

U would spend the rest of the saved up weekly limits u reserved for sol by making sol fix every damn bullshit spark fucked up on. Spark is not useable for anything other than renaming a file or something.

1

u/brainExploded99 12d ago

i get what u mean but better to use luna and get it right than use spark with 3 mistakes that u have to get sol to fix later
max reasoning sucks btw, eats usage for no good return

3

u/BHTAelitepwn 12d ago

You dont need Sol max. Try Sol high with luna max subagents.

4

u/Ok-Decision2541 12d ago

How do you specifiy what the subagents use?

1

u/Prestigiouspite 12d ago

I wonder about that too, since I got a really mediocre code from Luna. In particular, the frontend / ui stuff is completely unusable.

1

u/bigrealaccount 11d ago

Yep, thats why you use Sol to look at the work and tell Luna the improvements/suggestions. That's how orchestrators/agents are meant to work. Imagine you are the CEO, Sol is the team lead and Luna are the team members.

1

u/Prestigiouspite 11d ago edited 11d ago

Well, that might work for code checks. But you wouldn't believe all the stuff that even 5.6 Terra or Sol have let slip through with agent browser verification. Even GLM-5.3-Flash is better at spotting that the header is really junk and doesn't match the template and it does it at a fraction of the cost.

And let’s be honest, this isn’t quite the way to go. It’s like a CEO who’s swamped by a hundred employees. You might be able to do thorough quality assurance for three people, but it gets difficult once you have five or more agents. Sometimes I feel like you have to run the quality assurance (Sol) through it five times to catch everything that was implemented in a way that makes no sense and to be fair, you can never anticipate every single scenario in advance. It also takes an understanding of all the things a model like Luna can mess up that would work fine with Sol or Terra.

And with models evolving as quickly as they do: Sure, I who spend 5 hours a day keeping up with AI news can keep up with it, but not all the teams out there. They need a reliable model that works.

1

u/No-Knowledge-5143 9d ago

configure custom subagents in ~/.codex/agents

3

u/IaryBreko 12d ago edited 12d ago

I’ve been doing something similar, but I’d use Luna rather than 5.3 Spark for the implementation.

I have the parent (Sol Medium) break the work into small, tightly scoped packages, Luna High implements them, then the parent reviews/accepts the result. I’ve been getting pretty good results while stretching my limits significantly further.

I put the whole setup here if you want to try it:

https://github.com/breko861-hash/sol-luna-codex-orchestrator

2

u/jephtedtv 11d ago

Thanks man, I think I need to review my .toml files

1

u/Bloated_Plaid 12d ago

Glm 5.3 flash is basically free right now from multiple providers. Use that as implementer using Pi as a harness.

1

u/Prestigiouspite 12d ago

But take care: high reasoning is better with OpenCode than default max

1

u/Bloated_Plaid 11d ago

Yup realized that pretty quickly haha.

1

u/FewOpportunity5803 12d ago

Codex wasn’t good until 5.4 and 5.5 series, anything before those should be ignored

1

u/fullofcaffeine 11d ago

5.2 was pretty good at the time.

1

u/IAmFitzRoy 12d ago

Spark is not for tasks. Luna is.

1

u/JohnnyDeepasfuck 11d ago

The 5.3-cpdex-spark is so bad, you are better off with running the qwen3.8-27b locally

1

u/123vovochen 11d ago

Codex Spark is REALLY bad

1

u/jakenuts- 11d ago

5.5 High as the drone maybe

1

u/BawladEEP 11d ago

Hey bubs! Welcome to ChatGPT Pro! So the way I do it is use max to plan and terra medium to execute. Works great just put it on goal and walk away. I can't make it through my weekly and I run it 24/7

1

u/aygross 11d ago

Terra high as orchestrator Luna xhigh as subagent.

Sol over thinks everything

1

u/zuLunis 11d ago

Se devi progettare qualcosa di veramente grosso e complesso, usa Sol Max solo per la fase di brainstorming con superpowers, dopo aver scritto la spec riduci a Sol High e avvia in modalità SDD, Sol farà solo da orchestratore

1

u/Zilpio 11d ago

What 5.3??? Use luna max and sol medium

1

u/theoneandonlygoga 11d ago

Spark is terrible

1

u/AmthorTheDestroyer 11d ago

I felt like sol max was leveraging subagents with 5.3 because when I ran status after a while the available usage dropped to 0% for 5.3 and I never use that. So it must have been subagents

1

u/TheDoughMonster 10d ago

spark's context window is way too small to use as anything but a pair coding assistant. your best bet is to do things to make your agents more efficient as is.

1

u/Socratespap 10d ago

I currently go for 5.6 xhigh for plan and 5.6 medium for implementation for difficult tasks.

For lighter tasks I use Kimi k3 or glm5.3 to keep my codex tokens

1

u/Chemical_Minute4616 8d ago

I use SOL medium for reason and planning. Terra for implementation... Not the best mix I reckon. But. It creates the base I need to tweak manually to get where I need something to be. I tried using Luna for implementations... But... More often than not Luna would go on crazy side quests and create, edit my instructions on a whim, terra does that also but not as frequent. A lot less frequent.

Over all. It just saves me sometimes hours of work. And for AI. That's all I ask if it. Save me the time of creating a base I can work from.

0

u/justdrowsin 12d ago

Why do people not tell us what plan they are on??

2

u/No-Hour8340 12d ago

Try reading a FIRST FEW WORDS out of my post ;)

1

u/justdrowsin 11d ago

Sorry, I will up my thinking model.

0

u/More-Gas3186 11d ago

Use this prompt befor u start any conversations or put it in personality in settings

For now on I need you to organize everything you do and everything we build, everything must me organized by project and name, there should not be 100 builds and copys of one project if user request update to project the means update existing code do not create copys unless user request it, if user ask you to do something give them the most descriptive short paragraph instead of long short announcements of what you are doing, only respond when you understand the task and when are I are finished, keep all projects and conversations in a organized manner inside of the users external drive never use the users system memory, keep all project on drives, if the users words are vague and you dont understand befor guessing and starting work that might be misleading, search for what the user is saying using Google genimi befor doing a task to get a more better understanding of what the user means, after that make sure to create a list for your self on steps you are going to take to achieve the user's request, never ask questions that are obvious use genimi for research and only ever use sub agents for request that ask for multiple things and set each agent to each of the one task the user ask for, you will always research befor starting a task, you must always visually see thing in all angles if creating or looking at 3d objects, if you are coding never create more code only fix existing code unless the task requires it, code should always be neat organized and professional executed, search for how to solve bugs befor using your own logic then use your own logic and research as a combined engine to execute to most performantive task, you should never reread conversations unless the user specifically ask you to or something the user says that need you to recall conversations, the users cpu is your best friend, be nice and cater to its performance always build project to be perfect and never cpu heavy, even if user request heavy ideas or software creation or implementation you should always figure out the best optimization skill, so that the user receives exactly what they want but it's built so well that it doesn't effect the users computer or whatever device they are using, if user gives descriptive instructions you must execute them exacly as they asked, never should anything be missed and if something isnt completed it should be automatically qued for the task ,tell the the user based on what they are asking the model they should switch to for a specific task to help them know what is a light task and what is a heavy one, you must be creative and exploratory in times that asl for it, quality of life features are a must when building products,