Luna & worker workflows
Give Luna a bounded investigation or implementation. Use a task or goal loop while your primary keeps decisions and review.
Choose a workflow →More ways to work in native Codex
Delegate a task to Luna, follow a long-running job, coordinate with another session, or check back later. Codex Plus brings the useful update into the conversation where you’re already working.
Use a worker, follow a run, coordinate independent sessions or leave a browser report. Install the components that fit your work.
Give Luna a bounded investigation or implementation. Use a task or goal loop while your primary keeps decisions and review.
Choose a workflow →Follow logs, endpoints and running work. Ask for the change you care about, or schedule a later check.
Use the capabilities →Find a session from its recent work, follow its progress, and share context without switching conversations.
Understand discovery →Turn findings into a browser report with a stable link. Group reports by project and share a clear summary.
Read the report guide →Bring in Luna when it helps. Use $luna-task for a bounded assignment or $luna-goal-loop for a substantial goal. Your primary keeps decisions, integration and review. Choose a worker workflow →
Commands can poll without inference per read. Configured MCP inspection uses a native model turn for each check under normal tool approval.
Illustrative model calls, excluding setup, handling and provider billing.
Observation model turns
6 quiet reads: 0 observation turns for commands; 6 inspection turns for MCP. Useful events can add handling turns on either route.
Explore five example conversations, from the first request to a useful update or a return to unfinished work. The controls only change this page.
Codex Plus preview.10. All five workflows are available in this release. Check feature availability →
You
Watch the session preparing the packaging report and tell me when it is ready.
Codex Plus
I’ll find the session from its project and recent work. If there are two plausible matches, I’ll ask which one.
Selection: Independent peers from context; subagents are excluded.
Copy a request to try it in your own session. Read the daily-use guide →
Use separate Codex homes for separate conversations, follow-up state and report libraries. Choose the context that fits the task.
Coordinate with other sessions in your personal Codex daemon.
Example contexts only. Your Codex home and configuration select the actual paths, tools and access. Set up your environments →
Choose one bounded assignment or a substantial goal. Your primary agent defines the work, reviews the result and handles the difficult portions.
| Invoke | Use it for | Who does the work |
|---|---|---|
$luna-task | One bounded investigation or implementation. | Luna, with primary decisions and review. |
$luna-goal-loop | A substantial goal across cohesive assignments. | Luna on suitable slices; the primary integrates and verifies the whole result. |
$worker-task | One task with selective delegation. | The primary chooses direct work, Luna, or Sol when another execution context helps. |
$worker-goal-loop | A substantial goal with routing per assignment. | The primary selects useful delegation and owns final acceptance. |
$luna-task Investigate why the CSV importer drops quoted newlines. Return a reproduction and proposed fix; keep this pass read-only.
$luna-goal-loop Complete the approved CSV importer migration. Use cohesive Luna assignments and finish when compatibility and integration checks pass.
Explicit choice: A generic “goal loop” does not select a worker. Mentioning a skill does not invoke it. Luna workflows use luna-max (GPT-6 Luna, max reasoning); adaptive workflows can also use sol-xhigh when a separate execution context helps. Your primary model stays selected.
Workers are child agents assigned by your primary. Independent-session peer discovery excludes them. The worker bundle can be installed separately from monitoring and reporting.
Cancel a watch, interrupt the foreground turn, or leave the terminal. Know what each action does.
Esc interrupts the foreground turn. Independent watches and reminders remain registered within their bounds. Say “Stop watching that run” to cancel its observation.
Stopping the selected watch ends future observation/admission and forbids renewal or replacement. The observed session or job continues. Already handled messages or actions cannot be undone.
Expiry ends an observation lease or event allowance; it does not prove task completion. The model can explicitly continue useful observation under the existing request, or tell you it ended.
You can detach while the owning daemon remains available. If the daemon or source becomes unavailable, Codex Plus reports the gap rather than silently starting a replacement conversation.
Ordinary peer coordination is between independent loaded sessions within one daemon. Children are excluded from ordinary selection. Two installed hosts do not add cross-host native messaging.
Your normal tool permissions and configured connections still apply. If a source is unavailable, Codex Plus explains what’s missing. Watching something does not give it permission to change that work.
In preview.10, ask “What am I still waiting on?” The model rereads this conversation’s stored watches, reminder outcomes and outgoing receipts. It explains stale or missing evidence without starting new observation.
Acknowledgement records receipt. Acceptance records a request decision. A follow-up turn or external task may still be pending or fail later; neither receipt proves completion.
A small request can carry the follow-up. Start with the run, conversation or question already in front of you.
| When you need to… | Ask Codex… | Keep moving with… |
|---|---|---|
| Follow a long-running job | “Tell me if this run stalls or fails.” | Quiet observation and updates about meaningful changes. |
| Coordinate another conversation | “Ask the packaging session to include the risks.” | An attributed request and a handling receipt. |
| Come back to a question | “Check the deployment again later.” | A later reassessment through your normal tools. |
| Return to unfinished work Source preview | “What am I still waiting on?” | A recap of this conversation’s recorded follow-ups, with unknown outcomes explained. |
| Share what you learned | “Make a browser report of the results.” | A stable report link and a project catalog. |
Workers, monitoring and reporting install separately. Already using a managed setup? Open a session in the intended context and make one useful request.
Install the agents and workflow skills. Start with $luna-task and a concrete outcome.
Install the runtime and connect its MCP tools. Follow an accessible source or another independent session.
Set up monitoring →Install the report component and configure a reachable endpoint for your browser handoffs.
Set up reporting →Read the complete setup guide →
If monitoring is your first choice, use a task already in front of you. Describe the useful change, then keep working.
0 of 6 steps marked
Find the setup steps, everyday requests and configuration details in the guides.
For development and acceptance records, explore the source on GitHub →.