Reported by The Decoder
OpenAI has released new prompt templates for GPT-6.2 Astra and Sol covering writing style, initiative, and coding, alongside API changes that can discard reasoning content.
OpenAI says developers moving to GPT-6.2 Astra or Sol should review their system prompts. The company published copy-ready prompts in the models' documentation to curb behaviors it observed in both releases. Astra is built for the most demanding tasks, while Sol handles complex work at lower cost.
Astra writes more briefly and directly by default than earlier models, according to OpenAI . That means developers switching over should reconsider instructions like "be concise." For use as a colleague in everyday work, the company recommends a prompt that adopts user and source terminology, uses active voice, and puts key points first. When writing for external readers, the model should account for their lack of context. When editing, it should preserve the author's meaning and phrasing.
More from the original report
On long tasks, the model sometimes carries shorthand from its reasoning or other agents' messages into the final response. A dedicated prompt tells it to write that final answer so it stands on its own.
Treat your final answer as the user's first look at your work, and not as a continuation of intermediate commentary. The final answer must always be fully self-contained: users should never need to read earlier commentary updates for context, since they are collapsed when the final answer is shown to the user.
Write the final answer and all other human-facing material anew for the intended reader. Do not copy or closely paraphrase your reasoning or adopt its writing style. Do not carry over working shorthand, jargon, or abbreviations from your reasoning, tool calls, or instructions to subagents and automations.
When user intent is unclear, GPT-6.2 sometimes suggests a next step and waits for confirmation, OpenAI says. The company recommends a prompt telling the model to carry out those steps itself whenever it is authorized to do so. It should pause only for a major change in task scope, a real blocker, a decision the user must make, or an irreversible or destructive action.
When details are…
