跪拜 Guibai
← All articles
Backend · Interview · Java

OpenAI's New Prompt Guide Tells You to Stop Over-Engineering Your First Prompt

By 程序员飞鱼 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

The merge of ChatGPT and Codex into a single desktop tool with mid-stream correction commands changes the interaction model from one-shot prompting to a persistent, steerable session. Developers who treat prompts as a final draft waste time; the official guidance now endorses a conversational, iterative loop.

Summary

The era of meticulously crafted, multi-paragraph prompts is fading. OpenAI's updated guidance explicitly states that a first prompt doesn't need to be perfect; the workflow now centers on checking initial results and requesting specific changes. This shift is enabled by the merged ChatGPT and Codex desktop experience, which introduces Steer and Q commands. Steer merges a new instruction into an ongoing agent task, while Q queues it for the next round, eliminating the need to restart conversations when a detail is missed.

Beyond iterative prompting, the guide emphasizes giving AI concrete, executable steps to reproduce bugs rather than vague descriptions. With Computer Use, Codex can run those steps locally and observe the failure directly. For UI generation, developers should supplement screenshots with text describing invisible behaviors like hover states, validation rules, and keyboard interactions. A native voice input feature in the desktop app also lets developers talk through ideas when they can't find the right words, a mode Sam Altman himself says he can't go back from.

Takeaways
Start with a rough prompt and refine it after seeing the output; the first attempt doesn't need to be polished.
Use the Steer command in Codex to inject a new instruction into an agent task that is already running.
Use the Q command to queue a follow-up task that should execute after the current conversation finishes.
Report bugs with executable reproduction steps so Codex can use Computer Use to observe the failure locally.
Supplement UI screenshots with text descriptions of hidden behaviors like hover states, validation logic, and keyboard shortcuts.
Voice input on the desktop app handles rambling, unstructured speech well enough to replace typing for many interactions.
Conclusions

OpenAI's official endorsement of imperfect first prompts marks a departure from the prompt-engineering-as-craft era, driven by models that now handle ambiguity better and agent architectures that support mid-task correction.

The Steer and Q commands turn a stateless chat into a task queue, which is a small UI change with large implications for how developers manage long-running agent jobs.

Requiring executable bug reproduction steps shifts the debugging burden back onto the human to provide a precise trigger, but the payoff is that the AI can now verify the fix by running the steps itself.

Concepts & terms
Steer
A Codex command that merges a newly typed instruction into an agent task that is currently executing, allowing mid-stream course correction without restarting.
Q
A Codex command that queues a new instruction to be processed as the next task after the current conversation or agent job finishes.
Computer Use
An OpenAI agent capability that lets Codex control a local computer to run commands, observe outputs, and reproduce bugs by following executable steps.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗