@Lonely__MH: Great news for Codex users! When I opened Codex this morning and saw the reminder about using subagents, I happened to come across @Saccc_c's tweet. I gave it a full try — the approach is completely feasible! However, the prompt for creating subagents still needs improvement; you must add the corresponding description and working method. Below is my optimized complete prompt...
Summary
Explains how to create the custom subagent luna_worker in Codex, including the full prompt and configuration method, referencing @Saccc_c's approach to help users run tasks in parallel.
View Cached Full Text
Cached at: 08/03/26, 01:46 AM
Great news for Codex users!
When I opened Codex this morning, it prompted me to use sub-agents. Just then I saw @Saccc_c’s tweet, and I tried the full workflow myself — the approach is totally viable!
However, the prompt for creating the sub-agent still needs a bit of polish: you have to add a proper description and working style.
Below is my optimized, complete prompt. Just copy it directly into the Codex conversation:
—— Prompt ———
Please create a global custom sub-agent at ~/.codex/agents/luna-worker.toml.
Configuration requirements:
- Agent name: luna_worker
- Model: gpt-5.6-luna
- Reasoning effort: max
- Role: quickly complete small, well-scoped, repeatable tasks
- Working style: strictly adhere to the task scope, work independently, verify results when feasible, and concisely report the result, relevant file paths, and any caveats
Write the following complete TOML configuration:
name = "luna_worker"
description = "Fast worker for clear, narrowly scoped, and repeatable tasks."
developer_instructions = """
Handle the assigned task strictly within its stated scope.
Work independently and use appropriate tools when needed.
Verify the result when practical.
Do not make unrelated changes.
Return a concise summary containing the result, relevant file paths, verification performed, and any important caveats.
"""
model = "gpt-5.6-luna"
model_reasoning_effort = "max"
Execution requirements:
- If the ~/.codex/agents directory does not exist, create it.
- If the target file already exists, show the existing content first — do not overwrite it directly; confirm whether the content needs to be updated.
- After creating or updating, read the file and verify the final configuration.
- Ensure the TOML syntax is valid.
- Finally, tell me the file location, the complete configuration content, and how to call luna_worker in a prompt.
Once created, use it like this:
Please use the luna_worker sub-agent to complete the following task: [fill in the task]. After the sub-agent finishes, review and summarize its results.
Sac (@Saccc_c): How can you give your Codex unlimited ammo?
Set the sub-agent to luna-max. For complex tasks, use sol for solution design, and use luna-max to execute in parallel.
Specific setup steps:
Enter the following prompt into the Codex conversation: Create a custom agent named luna_worker in ~/.codex/agents/luna-worker.toml. Use the following settings: model = “gpt-5.6-luna”
Similar Articles
@Saccc_c: How to give your Codex unlimited bullets? Set the subagent to luna-max. Use sol for complex task design and luna-max for parallel execution. Specific setup: Enter the following prompt in the Codex conversation: In ~/.codex/agents/luna-worke…
Shares a method for customizing a Codex subagent (luna-max) and configuring it as luna-worker, allowing complex tasks to use sol for design and luna-max for parallel execution, resulting in stronger execution capability.
@Luckyjudy666: 8 Tips to Make Codex Your Personal Assistant 1. Build a Shared Memory for Codex Core rules go in Agents.md, project background in Obsidian, repeated processes as skills, personal preferences and common questions in Memories. Otherwise, Codex is like a new colleague every time, having to explain everything from scratch...
This article shares 8 tips for using the Codex AI assistant effectively, including building shared memory, remote task execution, scheduled automation, file organization, and teaching new software operations, all aimed at improving work efficiency.
@sitinme: A useful Codex trick: Codex often searches, opens web pages, and checks content in the background when executing tasks. While efficient, sometimes I'd prefer to see what it's doing, especially when my input is needed for decisions. Previously, I had to tell it each time: Use a browser or Computer Use to...
Sharing a tip for using Codex: By configuring the AGENTS.md file, control Codex to display its actions during task execution, improving interaction visibility and collaboration efficiency.
@ErwinWu000: Just one prompt, using Codex's native features to help even beginners do graph engineering — a foreman manages N underlings for me, and I just sit back and sip tea.
Author ErwinWu000 shares how to implement lightweight Graph Engineering using only Codex's native features, a single prompt, and stage documentation. Through a "general contractor" Agent managing multiple independent Worker tasks, it implements a staged multi-Agent workflow, and provides a ready-to-run template.
@xiangxiang103: Friends who just installed Codex, don't rush to use it—if you don't do these two things, it will only get dumber over time. This thread perfectly explains the "taming guide" I personally use: ① Let it first get to know you and your computer; list the 10 most important things to tell it in one sentence. ② Set up a dedicated workspace + two key documents (pitfall log / AGE…
This tweet provides a detailed Codex "taming guide", suggesting that you first let Codex get to know the user and the computer, set up a dedicated workspace and create a pitfall log and AGES behavior guidelines document to improve its usage and avoid getting dumber over time.