Skip to content

Commit 996c24e

Browse files
committed
update
1 parent 081d29c commit 996c24e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/ai-services/openai/how-to/reasoning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -318,11 +318,11 @@ print(response.model_dump_json(indent=2))
318318

319319
## Markdown output
320320

321-
By default the `o3-mini` and `o1` models will not attempt to produce output that includes markdown formatting. A common use case where this behavior is undesirable is when you want the model to output code contained within a markdown code block. To override this behavior and encourage markdown inclusion in model responses add the string `Formatting re-enabled` to the beginning of your developer message.
321+
By default the `o3-mini` and `o1` models will not attempt to produce output that includes markdown formatting. A common use case where this behavior is undesirable is when you want the model to output code contained within a markdown code block. When the model generates output without markdown formatting you lose features like syntax highlighting, and copyable code blocks in interactive playground experiences. To override this new default behavior and encourage markdown inclusion in model responses, add the string `Formatting re-enabled` to the beginning of your developer message.
322322

323323
Adding `Formatting re-enabled` to the beginning of your developer message does not guarantee that the model will include markdown formatting in its response, it only increases the likelihood. We have found from internal testing that `Formatting re-enabled` is less effective by itself with the `o1` model than with `o3-mini`.
324324

325-
To improve the performance of `Formatting re-enabled` we have found that further augmenting the beginning of the developer message will often result in the desired output. So instead of just adding `Formatting re-enabled` to the beginning of your developer message, instead we recommend experimenting with adding a more descriptive initial instruction like one of the examples below:
325+
To improve the performance of `Formatting re-enabled` you can further augment the beginning of the developer message which will often result in the desired output. Rather than just adding `Formatting re-enabled` to the beginning of your developer message, you can experiment with adding a more descriptive initial instruction like one of the examples below:
326326

327327
- `Formatting re-enabled - please enclose code blocks with appropriate markdown tags.`
328328
- `Formatting re-enabled - code output should be wrapped in markdown.`

0 commit comments

Comments
 (0)