Fix: Encourage markdown inclusion in model responses for o1/o3 #6425
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
💻 Change Type
🔀 Description of Change
By default, the o1/o3 models do not attempt to produce output with markdown formatting, resulting in a poor user experience due to responses being unformatted and hard to read.
This PR manually adds the developer message "Formatting re-enabled" to encourage the inclusion of markdown in model responses.
The developer message "Formatting re-enabled" is the official suggested way, references: https://platform.openai.com/docs/guides/reasoning-best-practices and https://learn.microsoft.com/en-us/azure/ai-services/openai/how-to/reasoning?tabs=python-secure#markdown-output.
Test results:
📝 Additional Information
Summary by CodeRabbit