GPT-5.6 Luna · workflow
The author recommends using Luna as a thread orchestrator, letting different threads choose Sol, Terra, or Luna for each task instead of having Sol Ultra automatically generate a batch of equally expensive subagents. The original prompt is very short. Its core。
The author recommends using Luna as a thread orchestrator, letting different threads choose Sol, Terra, or Luna for each task instead of having Sol Ultra automatically generate a batch of equally expensive subagents. The original prompt is very short. Its core idea is use the right model for the task, routing planning, implementation, and documentation research to the appropriate model.
I've been experimenting with using Luna to operate Codex itself. One thread can spawn, steer, and archive other threads… This is a necessary excerpt; read the original source for full context.
Give each thread a clear goal and completion check to prevent the orchestrator from continually creating threads.
Record planning, implementation, and research separately so you can verify whether model routing actually occurred.
The original post also provides a skill gist: https://gist.github.com/hashimwarren/d2ad4d3a12562dbac8e8f29f0d419999.
Comments point out that this may simply add another routing layer and may not be better than native subagents; validate it with task completion time, token usage, and first-pass success rate.
Reddit, r/codex · Source date: Not disclosed · Edited: 2026-09-20
Read the original sourceGPT-5.6 Luna
Run this guide in the environment listed above. Downloading does not transfer the template or establish model availability for your account.
