-
Notifications
You must be signed in to change notification settings - Fork 393
Pro-active option to enable gpt-5 use in Agents Playground #574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Added note about gpt-5 model config, as it doesn't support obsolete parameters like "temperature" and "top_p", which are still available in the Agents Playground. That's why the value of those 2 parameters should remain at default "1" to prevent "unsupported parameter" error message.
|
Learn Build status updates of commit fd68f9c: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a proactive note about gpt-5 model configuration in the Agents Playground to prevent common user errors. Since gpt-5 models do not support the obsolete temperature and top_p parameters that are still present in the UI, users need guidance to avoid encountering "unsupported parameter" errors.
Key changes:
- Added documentation note warning users to keep
temperatureandtop_pat default value of1when using gpt-5 models in Agents Playground
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
Added note about gpt-5 model config, as it doesn't support obsolete parameters like "temperature" and "top_p", which are still available in the Agents Playground. That's why the value of those 2 parameters should remain at default "1" to prevent "unsupported parameter" error message.