相信直觉

You've been asking for this one... Now in preview: Codex in the ChatGPT mobile app. Start new work, review outputs, steer execution, and approve next steps, all from the ChatGPT mobile app. Codex will keep running on your laptop, Mac mini, or devbox.

这绝对是 Codex 最牛掰的实战教程，把常见用法和最近的爆火玩法都讲透了。 我之前更多是用 Codex CLI，听了逸尘的建议，现在用 Codex 桌面端，体验真是好了一大截。

/goal is the best command in Codex, Claude Code, and Hermes right now. And most are using it wrong. They write "make no mistakes". And pray. Here's how to structure yours for a mission, to rank your uncertainties before acting, to kill scope creep, and to close every loop other prompts leave open. /goal prompt [structure below] GOAL: CONTEXT: CONSTRAINTS: PRIORITY: (optional) 1. 2. 3. PLAN: DONE WHEN: VERIFY: OUTPUT: STOP RULES:

Codex can get dumber and slower on long sessions. Here's the fix: 1. Run Process_narration=false This will stop Codex from showing you all the planning steps, resulting in saving a lot of output tokens. 2. Prompt: "Act as an orchestrator. Use parallel agents to do the research and execution work. Write detailed tasks for each parallel agent and force them to act, iterate, get their tasks done, and bring back an in-depth report. Your job is to deeply analyze the agents' work, provide feedback, and provide them with continuous tasks." This prompt offloads the majority of the context-burning work to agents, and each agent has its own context window. So you can utilize 5 agents (5 context windows). 3. Add this hard rule: "Measure twice, cut once policy." Debugging and patching is messy work. Force Codex to plan first, act after (don't use plan mode; it's just overcomplicated). Ask it to make a task list for every task so it can track progress and iterate better. 4. Add this hard rule: "Keep the codebase clean, no tmp files, no dead code, no dead files. Stay organized all the time. No unnecessary folders, subfolders, or files." Claude keeps most of its working files in cache as temporary files (which is bloatware, but it keeps the codebase neat), but Codex is output-heavy. It creates tons of folders and files, and your workspace can become a mess after a few sessions. As a result, this contaminates the context window and degrades performance. Force Codex to stay organized and follow the file structure. These 4 techniques can help you save 40% context every session, and performance will be a lot better. For planning, use Codex 5.5 (extra high), and after the plan is done, shift to Codex 5.5 (high) with fast mode. This works faster.