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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @prabinjha, @kurtrank.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

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

Unlinked contributors: prabinjha, kurtrank.

Co-authored-by: dkotter <[email protected]>
Co-authored-by: jeffpaul <[email protected]>
Co-authored-by: JasonTheAdams <[email protected]>
Co-authored-by: karmatosed <[email protected]>

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

Codecov Report

❌ Patch coverage is 62.50000% with 93 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.76%. Comparing base (c2098b0) to head (04c2df4).
⚠️ Report is 76 commits behind head on develop.

@@              Coverage Diff              @@
##             develop     #146      +/-   ##
=============================================
+ Coverage      48.99%   56.76%   +7.77%     
- Complexity       473      505      +32     
=============================================
  Files             30       32       +2     
  Lines           2329     2565     +236     
=============================================
+ Hits            1141     1456     +315     
+ Misses          1188     1109      -79     

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

@jeffpaul This is ready for final review, noting I've not had success getting this to fully work in the Playground as the request to generate an image typically takes about 60 seconds and Playground always times out before that

This tested really nicely, and yes a bit of a lag in generating but there's :alot: happening in the background. To that specific extent, not something to hold up this PR, but perhaps helpful for a future iteration (but feel free to tell me I'm dumb here and we can skip it) would be some simple "loading text" that describes what's happening (e.g. "Generating image generation prompt from post content...", "Generating image from generated prompt...") so folks understand why its not an immediate response?

One thing that I think is worth pausing on to decide how best to land this experiment is the specific alternative text, title, caption, description for generated images. Currently the Title is set as AI Generated Image and the Description is This is an AI generated image.

Perhaps an iteration here to the Alt Text getting generated as well from the resulting image (perhaps hooking into the alt text ability?), the Title getting a truncated or condensed version of the generated alt text, the Caption stays empty as that's meta that more often is also rendered on the front end and may be best left for author/editor input, and the Description gets some provenance info (though anyone who knows me knows I'd LOVE to see something like c2pa-js used to store meta here) so something like “Generated by ExampleAI Image Model v2 on 05 Feb 2026. Prompt: ‘Minimal illustration of a 1700s sailor staring out to see from a dock.’”?

This tested really nicely, and yes a bit of a lag in generating but there's :alot: happening in the background. To that specific extent, not something to hold up this PR, but perhaps helpful for a future iteration (but feel free to tell me I'm dumb here and we can skip it) would be some simple "loading text" that describes what's happening (e.g. "Generating image generation prompt from post content...", "Generating image from generated prompt...") so folks understand why its not an immediate response?

The only issue here is while yes, we are running lots of things one after the other, they all run fairly quickly besides the actual image generation. So we could add a progress message but I think what we'd see is the message shows then is replaced before someone can actually read it, which may be more annoying then helpful. But the actual image generation part will take time (OpenAI is usually around 60 seconds, Google is typically faster but still ~40 seconds) so maybe still useful to have those messages?

One thing that I think is worth pausing on to decide how best to land this experiment is the specific alternative text, title, caption, description for generated images

I'm open to any suggestions here, I purposely left it fairly basic as a starting point.

Perhaps an iteration here to the Alt Text getting generated as well from the resulting image (perhaps hooking into the alt text ability?), the Title getting a truncated or condensed version of the generated alt text

My one concern in regards to alt text is that's a separate Experiment and we can't assume users will have both of those active (Image Generation and Alt Text Generation). In that situation, not sure how we handle that, as the Alt Text Generation Ability won't be available to use if it's not turned on. I guess we could have a light-weight duplicate of that specific to Image Generation, though I could see some complaints there from users wondering why AI is generating alt text when they don't have that Experiment turned on.

the Caption stays empty as that's meta that more often is also rendered on the front end and may be best left for author/editor input

Yeah, I agree on keeping this empty

the Description gets some provenance info (though anyone who knows me knows I'd LOVE to see something like c2pa-js used to store meta here) so something like “Generated by ExampleAI Image Model v2 on 05 Feb 2026. Prompt: ‘Minimal illustration of a 1700s sailor staring out to see from a dock.’”?

Main issue here is the Ability that generates an image only returns the generated image, it doesn't return anything else, like provider, model, prompt used, etc. We could look to update the Ability to do that if we think that would be valuable, though I'd also need to figure out if the AI Client can tell us what provider and model was used (I'm assuming so but not something I've tried).

The only issue here is while yes, we are running lots of things one after the other, they all run fairly quickly besides the actual image generation. So we could add a progress message but I think what we'd see is the message shows then is replaced before someone can actually read it, which may be more annoying then helpful. But the actual image generation part will take time (OpenAI is usually around 60 seconds, Google is typically faster but still ~40 seconds) so maybe still useful to have those messages?

Ok, yeah maybe we ignore this for now and see if there's community feedback about the time to completion and if some sort of loading info is helpful.

My one concern in regards to alt text is that's a separate Experiment and we can't assume users will have both of those active (Image Generation and Alt Text Generation). In that situation, not sure how we handle that, as the Alt Text Generation Ability won't be available to use if it's not turned on. I guess we could have a light-weight duplicate of that specific to Image Generation, though I could see some complaints there from users wondering why AI is generating alt text when they don't have that Experiment turned on.

Perhaps if the alt text experiment is disabled / that ability is not available, we fall back to adding in directly the raw image gen prompt (knowing that'll likely include sub-optmial "Generate image of" sort of context, but at least someone generating the image could immediately edit/remove it?).

Main issue here is the Ability that generates an image only returns the generated image, it doesn't return anything else, like provider, model, prompt used, etc. We could look to update the Ability to do that if we think that would be valuable, though I'd also need to figure out if the AI Client can tell us what provider and model was used (I'm assuming so but not something I've tried).

Let's chat about how quickly feasible this could be, balancing that with still getting this feature shipped since its otherwise near ready.

Ok, yeah maybe we ignore this for now and see if there's community feedback about the time to completion and if some sort of loading info is helpful.

I went ahead and added this as it was pretty simple and now that we're potentially generating alt text as well, that's another few seconds of waiting. So now each step will show a progress message.

Perhaps if the alt text experiment is disabled / that ability is not available, we fall back to adding in directly the raw image gen prompt (knowing that'll likely include sub-optmial "Generate image of" sort of context, but at least someone generating the image could immediately edit/remove it?).

Made this change now. If the alt text Experiment is on, after an image is generated we send it back to generate alt text and use that. If that Experiment isn't on, we use the prompt instead.

We then take that and trim it down to use as the title instead of hardcoding to AI Generated Image

Let's chat about how quickly feasible this could be, balancing that with still getting this feature shipped since its otherwise near ready.

This was also fairly easy so I've gone ahead and made this change. The image generation Ability will now return the image data plus information about the provider and model used. This information is then used in the image description after is is imported.

@adamziel one thing I've run into in using the Playground testing link in this PR is that sometimes Playground stalls out / response times drag on and I'm not reasonably able to test PRs in Playground (with this PR its because of the comms/wait in generating a prompt+image). Perhaps an enhancement for the Playground PR button action would be to also export below the button something like (or download a ZIP here) sort of text that links to the ZIP used so folks could test locally?

Error: Network error occurred while sending request to https://api.openai.com/v1/images/generations: cURL error 28: Operation timed out after 30002 milliseconds with 0 bytes received

Currently getting timeout issues in testing locally, going to build a new local and try again

Ok, got things working locally, phew, one tweak is the date in the Description field is likely US-centric MM/DD/YYYY (I'm guessing) so let's update to DD Month YYYY (e.g. 6 February 2026)?

Ok, got things working locally, phew, one tweak is the date in the Description field is likely US-centric MM/DD/YYYY (I'm guessing) so let's update to DD Month YYYY (e.g. 6 February 2026)?

Right now we're using new Date().toLocaleDateString() to generate this date, which the toLocaleDateString part of that will

return a string representing the date portion of a Date object, formatted according to specific locale conventions and time zones

So instead of forcing a particular format, the format used will depend on the individual user's locale and timezone settings. I can update that though if we want to force a specific format for all users.

So instead of forcing a particular format, the format used will depend on the individual user's locale and timezone settings. I can update that though if we want to force a specific format for all users.

While I'd like to make the format a bit more ISO-specific, its probably best to follow the site-specific setting for now and we can always iterate in the future if feedback comes back strongly in a different direction.