Skip to content

Update our preferred models - #913

Merged
jeffpaul merged 5 commits into
WordPress:developfrom
dkotter:update/openai-model
Aug 7, 2026
Merged

Update our preferred models#913
jeffpaul merged 5 commits into
WordPress:developfrom
dkotter:update/openai-model

Conversation

@dkotter

@dkotter dkotter commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

What?

Updates the preferred Anthropic text and vision model from claude-sonnet-4-6 to claude-sonnet-5, the preferred Google text and vision model from gemini-3-flash-preview to gemini-3.6-flash and the preferred OpenAI text and vision model from gpt-5.4-mini to gpt-5.6-luna and removes the setting of custom temperature parameters.

Why?

We want to ensure the default models we recommend are using the latest versions of models. In addition, the OpenAI GPT-5.5+ models don't support setting temperature values unless reasoning mode is turned off. There are a few different approaches we could take here:

  1. Remove the setting of temperature values (what this PR does)
  2. Set reasoning effort to none but will need to ensure we only apply this to OpenAI models
  3. Update the OpenAI provider to ignore temperature values if the model doesn't support it

For now I've gone with option 1 in this PR as I don't think setting temperature really provides any value but open to thoughts there.

How?

Updates our preferred models for Anthropic, Google and OpenAI to be the latest versions and removes anywhere we were using using_temperature on the prompt builder

Use of AI Tools

None

Testing Instructions

One by one, configure Anthropic, Google and OpenAI and test all features to ensure they still work

Changelog Entry

Changed - Updated preferred models to more recent ones for the three default providers.
Deprecated - Filter wpai_meta_description_result_temperature is no longer being used and will be removed in the next release.
Removed - No longer set custom temperature values on any of our requests.

Open WordPress Playground Preview

@dkotter dkotter added this to the 1.3.0 milestone Jul 31, 2026
@dkotter dkotter self-assigned this Jul 31, 2026
@dkotter
dkotter requested a review from a team July 31, 2026 15:02
@dkotter
dkotter requested a review from jeffpaul as a code owner July 31, 2026 15:02
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: dkotter <dkotter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@codecov

codecov Bot commented Jul 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.41%. Comparing base (7976907) to head (4b0e875).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #913      +/-   ##
=============================================
- Coverage      80.43%   80.41%   -0.03%     
  Complexity      2565     2565              
=============================================
  Files            110      110              
  Lines          10448    10437      -11     
=============================================
- Hits            8404     8393      -11     
  Misses          2044     2044              
Flag Coverage Δ
unit 80.41% <100.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jeffpaul
jeffpaul merged commit c858d37 into WordPress:develop Aug 7, 2026
40 of 41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants