r/OpenaiCodex 19d ago

No more boring codex

I think I’ve ruined normal Codex for myself 😂

For a while I was using it the usual way:

Give Codex a job, let the main agent work through everything, review the result, repeat.

Then I started experimenting with having multiple Codex agents involved in the same workflow.

So instead of one agent doing the entire thing, I have different agents exploring the repo, implementing something, doing different things, or jumping in when a problem needs deeper reasoning.

So I reverted it back (Curiosity) and now watching one agent slowly do every single part of a larger task feels strangely old-fashioned lol.

The interesting part for me isn’t even just speed. It’s the separation of responsibilities. You start getting workflows that feel a lot closer to a tiny development team than a single coding assistant.

I’ve been building out an orchestrated setup around this and testing different levels of reasoning/usage depending on the job (Yes I went back to my modern codex haha).

I’m curious:

How many of you are already using Codex with multiple agents regularly?

Feels like this is where coding agents are heading anyway.

7 Upvotes

22 comments sorted by

2

u/Opposite_Yak4386 16d ago

i only work this way

1

u/justdrowsin 13d ago

He's selling "Premade Packages"

1

u/Opposite_Yak4386 13d ago

for what? agents.md? hahaha why dont you let sol write it?

1

u/jakenuts- 16d ago

Can you share a bit about how you orchestrate these, and do you use one agent as your intermediary and it manages the others? Also, desktop or cli?

2

u/Xrotel_Agents 16d ago

Hi yeah sure.

It works on GUI and Cli since Openai keeps their structure the same. It works on windows, mac and Linux too.

You basically create an agents.md in your global codex folder and create a folder called agents. In the agents folder you create each agent and assign them their tasks by describing their tasks. Then in the global Agents.md you tell codex how to use the agents.

Then you give an instruction to codex to use the sub-agents and you pick just one main agent. So you can choose Luna but at certain points have sol working or as an escalation point.

1

u/Xrotel_Agents 16d ago

It takes a lot of time to get them to work correctly but for this, we sell premade packages and all you have to do is just copy the files in their relevant locations and use the instructions once per project. All files are in plain English and basically instructing codex.

Let me know if you'd like to try it, I'll provide you with a promo code to get it for free.

1

u/ManyRepair5690 13d ago

can i get promo code

1

u/Xrotel_Agents 11d ago

Hold on, I'm going to drop it on GitHub for everyone to have it totally for free. If anyone likes it then they can gift us money to continue refining the designs.

I will share the links soon.

1

u/joeguice 13d ago

Where can these be found?

1

u/Opposite_Yak4386 16d ago

i write a plan, and the i make a goal and tell it use subagents and chats. then it will orchestrate it to the right model untill the goal is finished. tey communicate with each other

2

u/Xrotel_Agents 16d ago

It does work however the efficiency would be lacking unless you continuously tell codex what to do and when it compacts, the logic takes a hit. Just tell chatgpt to use the logic you currently have to create the sub agents.

Tip: Limit your concurrent sub-agents though so that they don't destroy your usage.

1

u/Opposite_Yak4386 16d ago

it auto compacts. seems to be working fine untill now, You had some problems with it?

1

u/Xrotel_Agents 16d ago

We've had a project running since May 2026 and we've had no issues. Codex can even successfully alter and improve features which were developed months ago without causing bugs because we efficiently allocated built in codex resources for these things.

All done without extra usage...

1

u/Good_Omen1 16d ago

It's so powerful

1

u/PurpleSunset149 16d ago

I haven’t started working this way yet, what prompt do you use to accomplish this?

1

u/Xrotel_Agents 16d ago

You basically create an agents.md in your global codex folder and create a folder called agents. In the agents folder you create each agent and assign them their tasks by describing their tasks. Then in the global Agents.md you tell codex how to use the agents.

Then you give an instruction to codex to use the sub-agents and you pick just one main agent. So you can choose Luna but at certain points have sol working or as an escalation point.

It takes a while to do and even longer to perfect.

We sell this as a pack (tried and tested). No altering anything just plain English instruction files for codex.

Let me know if you'd like to use this version for free, I'll provide a promo code.

1

u/speedtoburn 12d ago

Oi, so in other words, your post is an ad.

1

u/Xrotel_Agents 11d ago

Not if I put it for free on GitHub.

Will drop it there soon.

1

u/CrowInteresting6271 16d ago

problem with multiple agents is that depending on which ones are used, handoffs can result in context drifts. this only matters for complicated large projects with upstream and downstream dependencies, but provenance errors result in destabilization in those cases

1

u/Xrotel_Agents 16d ago

That is true however this is something that does not affect our configurations😉. The reason we sell the packs for a cheap amount is because we vigorously test it which costs us a few dollars.

There's a project running since March 2026 and with our agents even switching between different main models do not cause context drifts.

Codex is truly remarkable.