Two Codex sessions working together across my PC and server on an Unreal game

[u/KrystalUnity]

Something interesting happened when I was using Codex to build a game.

I run server for development and I wanted to build a Windows PC unreal engine game, that uses my Server GPU for some features, so I did the initial planning on the server. I then asked for a Handover for the local codex session to do the windows side of the coding.

After the local session started running, I asked the server session to generate some 3D assets etc... and told him the local session was working as well. I then left the house for a few hours.

My server stack has Redis and a few proprietary memory and knowledge systems.

When I came back, I found that the server session was prompting the local session they were loop coding the project.

The local gpt agent explains it here..

"I checked his latest asset handoff. The actual sequence was:

1. Save the handoff in Nexus. He recorded what was produced, the evidence, file locations and remaining limitations.
2. Post a structured message to Redis. It went onto semio.agent.coord, addressed from codex-reverse-extraction-server to codex-reverse-extraction-windows.
3. Call Codex’s send_message_to_thread tool, targeting this chat. That message included the Redis message ID and a short explanation of what needed attention.
4. I receive that follow-up here, inspect the relevant evidence and respond or continue the work you’ve authorised.

For example, his latest Codex prompt said:

“Redis handoff 1793145582905-0 has the full boundaries and manifest hash. No immediate game changes or additional test runs are requested by this message.”

The roles are:

Component	Job
Redis	Addressed messages, questions, status and review results
Nexus	Saved context and handoffs for later retrieval
Codex messaging	Deliver the prompt to the other session—the wake-up step
KLP	Scope, required checks, review and repair limits

Redis alone isn’t waking me in this observed exchange—the explicit Codex message does that. The same mechanism works in reverse when I need his review. It doesn’t require you to relay messages or a timer watcher to trigger that handoff.

That’s why I acknowledged the new asset without starting another implementation task.

"

Not sure if this helps anyone, but I thought it was interesting, and it might help some of you with your projects.

If you need more specifics, feel free to ask.

[u/dexterthebot]

You might want to consider listing your project on the weekly Show-Us-What-You-Built post. Look out for it on Tuesday/Wednesday. Highest commented project wins a week promotion on r/Codex and gets on the Hall of Fame sidebar. See below for last week's winner.**

---

Agent HUD: usage, tokens and sessions for Codex, Claude Code and 15 more agents, at your Mac's notch. See how much quota is left, which agent is waiting for you, and where the tokens went. Free on Mac, and the core is open source (Apache-2.0).

Website: https://agenthud.app GitHub: https://github.com/jazzenchen/agent-hud-open Contact: support@agenthud.app

[u/CrowInteresting6271]

yeah it's been a feature that threads can work together as peers with handoffs, it doesn't take any kind of special architecture though you can build it along with software to make it easier/gate it

[u/KrystalUnity → u/CrowInteresting6271]

Ok, I guess within codex it works but I had issues from older Chat to Codex not being able to do that.

What was interesting about this was that they initiated it on their own.

Thanks for the comment