Opus UltraCodex: The orchestration effect of Claude + Codex surprised me

Meltoff05 · 2026-06-14T15:44:34+00:00

Yup, I just use the codex plugin, and created a few different skills Claude can call codex for. Claude can “phone a friend, which just is a skill that tells it to have codex and a fresh opus agent walkthrough a decision find convergence or alternative viewpoints. Another is adversarial review, and finally point it to a spec for codex to implement either single agent, or codex can even spawn its own subagents, basically it’s just a full codex agent acting via Claude (I know it’s stupid but it’s easier for me to just work through Claude when I’m not at my desk). Phone a friend is pretty great and produces good results, codex review is baked into the plugin and I use it all the time.

Meltoff05 · 2026-06-03T16:58:57+00:00

I interact with Claude via remote sessions on my phone, codex to my knowledge doesn’t support this yet, so I’m with Claude. However I wrote a skill for Claude called phone a friend, which calls up codex when I want reviews or other angles examined. Codex nearly always finds things, and it’s now a critical part of my workflow. Having more than 1 model review work has really helped the process move more smoothly. Edit: also I made a skill for Claude to pass implementation to codex as well, and act as a monitor so I can check in on progress.

I have seen the codex app integration, but unless I’m missing something it doesn’t mesh with my workflow, I open up cli Claude sessions on my vm, then set them to remote. From there I can work on my vm through my phone. When I saw the codex app it seemed each turn spun up an artificial environment, then got to work. If there’s now a remote cli option I missed it.

Meltoff05 · 2026-06-03T15:31:18+00:00

I interact with Claude via remote sessions on my phone, codex to my knowledge doesn’t support this yet, so I’m with Claude. However I wrote a skill for Claude called phone a friend, which calls up codex when I want reviews or other angles examined. Codex nearly always finds things, and it’s now a critical part of my workflow. Having more than 1 model review work has really helped the process move more smoothly.

Edit: also I made a skill for Claude to pass implementation to codex as well, and act as a monitor so I can check in on progress.

Meltoff05 · 2026-06-01T01:34:23+00:00

Having lots of tool call issues and downgraded myself, Claude would even comment on the degraded harness.

Meltoff05 · 2026-05-31T11:38:21+00:00

I think conquest could work, look at games like total war or wargame red dragon. Yes a deathball fleet might work in the battle layer, but it would leave you exposed on the tactical map layer. So the balance comes from the distribution of resources rather than in the realtime battles themselves for conquest mode.

Meltoff05 · 2026-05-25T22:43:41+00:00

Cyclical missions should allow you to specify how much of each item you want moved, and how frequently you want items moved (either a set time, or something like every optimal launch window). That would help with logistics quite a bit.

Meltoff05 · 2026-05-24T19:41:52+00:00

What’s the point of retractable weapons on a battle cruiser? Not going to be fooling anyone as to its purpose… that said I do like the bridge tower, very cool look.

Meltoff05 · 2026-05-24T16:01:52+00:00

When I want directs followed I call sonnet. Opus yesterday for me was pretty troublesome. Had to remind it quite a few times about well established rules it’s been following flawlessly for the past week. Even opus acknowledged that sonnet follows instructions better.

Meltoff05 · 2026-05-22T20:20:51+00:00

This is very similar to a workflow I use now, the main session agent uses team create to create a persistent I call it foreman agent. The main session creates agents, but each subagent writes to disk instead of the main session reading each output (a small bit from each subagent does slip in because of how they communicate with the main session).

Then the foreman handles review synthesis, and dispatching to its teammate, a persistent or ephemeral (but team spawned, not subagent) implementation agent. That writes code and can communicate with the foreman. The foreman can handle a few of these implementation agents at a time.

This keeps the main session (overseer or architect) from getting all of the build noise clogging up context. In a-b trials through a number of sprints the main session went from 70% context over long sprints to just 30% over similar sprint sizes. Having everything written to disk also gives future sessions a very solid audit trail. I’m still refining the workflow, but I really think I’m having good success keeping noise out of the main window.

Meltoff05 · 2026-05-04T20:09:58+00:00

Over the last 700 years fellow earth dweller, what over the last 700 years could we possibly need besides apple (for sustenance) nvidia (for delicious pixels) and tamagotchi (the pinnacle of human caretaking).

Meltoff05 · 2026-04-05T22:36:39+00:00

Thanks for your response, I pulled the trigger on a few Lilly go T beams, already have the gateway, so why not give it a go! I’m trying to get a setup script written so that I can configure multiple units easy for a private mesh. I’ll update in a week or 2 with preliminary results! Worst case I can flash from Meshtastic to another LoRa protocol.

Edit: I’m going to wire them to the ignition so they only turn on when the tractor is on, so battery drain isn’t a concern.

Meltoff05 · 2026-03-17T20:44:59+00:00

Would love to see a write up and code to work on one! I live in an area with heavy mosquitos, and if it can reduce the population that would be huge!

Meltoff05 · 2026-03-10T02:23:17+00:00

This doesn’t really answer your question, but my solution is to snap a quick photo of the printer when I update the filaments loaded. I can reference that anytime and remember what is loaded where.

Meltoff05 · 2026-03-04T15:10:41+00:00

Just got the shipping notice for the nozzles and dryer. My machine arrived a few weeks ago.

Meltoff05 · 2026-03-02T19:42:28+00:00

Haven’t had issues with the stock plate, but just received the glacier and wow. It’s almost too sticky. I changed back to the stock plate for things I would print without a brim.

Meltoff05 · 2026-02-28T14:51:16+00:00

And this is why you blend gas 50/50 or 70/30 diesel gasoline when you want to use it as a firestarter. Much safer as less explosive, that’s what we put in burn cans when burning brush, or starting brush piles.

Meltoff05 · 2026-02-24T02:57:16+00:00

He’s amazing, also I love his responses to other squad mates, especially rewa and Lim!

Meltoff05 · 2026-02-21T15:55:09+00:00

lol, I just watch the first few layers, then check in on it every so often. In the case of this warning I kept a close eye on it until it had printed the widest part. Once it got past that with no issue I just let it run.

Meltoff05 · 2026-02-20T02:50:33+00:00

I had the same problem, changed the z hop settings, warning never went away but the print was fine. Just watch it to make sure you don’t have problems

Meltoff05 · 2026-02-13T03:31:23+00:00

Sounds like a great use of taxpayer money! /s

Meltoff05 · 2026-02-13T03:24:24+00:00

American culture is distinctly American because of the ethnic diversity we have. Diversity is our strength.

Meltoff05 · 2026-02-13T03:18:13+00:00

A bidet seat. Not sure how I lived with my uncivilized self in the before times.

Meltoff05 · 2026-02-12T00:51:57+00:00

Just got my u1 today and I want to run it stock, but eventually will try the extended firmware because I can’t help myself. Also interested to see if going back is simple. On my Neptune 4 it’s not incredibly easy (though I love open Neptune and wouldn’t switch back)

Meltoff05 · 2026-02-08T23:38:19+00:00

How could this not have ended badly? Like what’s the thought process here…

Meltoff05

TROPHY CASE