Skip to content

Add support for the new gpt-image-2 model#456

Merged
jeffpaul merged 2 commits intoWordPress:developfrom
dkotter:update/gpt-image-2
Apr 22, 2026
Merged

Add support for the new gpt-image-2 model#456
jeffpaul merged 2 commits intoWordPress:developfrom
dkotter:update/gpt-image-2

Conversation

@dkotter
Copy link
Copy Markdown
Collaborator

@dkotter dkotter commented Apr 22, 2026

What?

Adds the new gpt-image-2 model to our preferred model list

Why?

OpenAI recently announced the new gpt-image-2 model and it supposedly is significantly better than the previous model and it's also cheaper to use.

How?

  • Add gpt-image-2 to our preferred model list
  • Remove gpt-image-1-mini from that list

Use of AI Tools

None

Testing Instructions

  1. Checkout this PR
  2. Setup the OpenAI provider
  3. Turn on image generation
  4. Generate an image and ensure it works

Changelog Entry

Added - gpt-image-2 to our preferred model list.

Open WordPress Playground Preview

@dkotter dkotter added this to the 0.8.0 milestone Apr 22, 2026
@dkotter dkotter self-assigned this Apr 22, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 22, 2026

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 <[email protected]>
Co-authored-by: jeffpaul <[email protected]>

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

@dkotter dkotter requested a review from jeffpaul April 22, 2026 03:27
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.90%. Comparing base (43d3bde) to head (e0b1ac7).
⚠️ Report is 6 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #456   +/-   ##
==========================================
  Coverage      66.90%   66.90%           
  Complexity       907      907           
==========================================
  Files             59       59           
  Lines           4699     4699           
==========================================
  Hits            3144     3144           
  Misses          1555     1555           
Flag Coverage Δ
unit 66.90% <100.00%> (ø)

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

☔ View full report in Codecov by Sentry.
📢 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.

Copy link
Copy Markdown
Member

@jeffpaul jeffpaul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way we can push these sorts of updates without having to ship a plugin release?

@dkotter
Copy link
Copy Markdown
Collaborator Author

dkotter commented Apr 22, 2026

Is there a way we can push these sorts of updates without having to ship a plugin release?

So this has been discussed multiple times previously but we could remove the preferred models list and rely on the AI Client and individual providers to determine what model to use. This could result in the latest models being used without any code changes (in this case, gpt-image-2) but there's no guarantee that will be the case (depends on the sorting, if any, a provider brings and also depends on what order the AI Client lands on).

My preference is to maintain this preferred list and it's not hard for us to update these versions and have those go out in a subsequent release, but I do understand the benefit to removing this list and relying on the AI Client to decide.

@jeffpaul jeffpaul mentioned this pull request Apr 22, 2026
27 tasks
@jeffpaul jeffpaul merged commit 295be9d into WordPress:develop Apr 22, 2026
18 checks passed
@github-project-automation github-project-automation Bot moved this from Needs review to Done in WordPress AI Planning & Roadmap Apr 22, 2026
@dkotter dkotter deleted the update/gpt-image-2 branch April 22, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants