Skip to content

[FORNO-326] Add Jetpack AI abilities to Page/Site editor#49979

Open
kat3samsin wants to merge 3 commits into
trunkfrom
forno-326/jetpack-ai-to-page-site-editor
Open

[FORNO-326] Add Jetpack AI abilities to Page/Site editor#49979
kat3samsin wants to merge 3 commits into
trunkfrom
forno-326/jetpack-ai-to-page-site-editor

Conversation

@kat3samsin

Copy link
Copy Markdown
Contributor

Fixes #

Proposed changes

  • Allow the Jetpack AI provider bundle/data to load on supported page and site editor surfaces.
  • Gate Jetpack AI provider exposure behind the same rollout checks used for the in-development sidebar suggestions: preview enabled, proxied request, Jetpack AI enabled, and AI features available.
  • Keep page/site editor provider data from overriding the host-selected agentId.
  • Add tests for proxied page/site editor provider data, unproxied skips, disabled AI skips, and provider registration/enqueue behavior.

Related product discussion/links

  • FORNO-326

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  • Confirm PHP syntax:
    • php -l projects/plugins/jetpack/extensions/plugins/ai-assistant-plugin/ai-sidebar/class-jetpack-ai-sidebar.php
    • php -l projects/plugins/jetpack/tests/php/extensions/plugins/ai-sidebar/Jetpack_AI_Sidebar_Test.php
  • Confirm whitespace:
    • git diff --check
  • On a proxied Simple test site, open the post editor and confirm Jetpack AI Sidebar data includes agentId: wp-orchestrator.
  • On a proxied Simple test site, open the page editor and site editor and confirm Jetpack AI provider data is present without agentId.
  • Confirm unproxied requests, disabled Jetpack AI, and disabled preview gate do not emit Jetpack AI provider data.

Note: Local PHPUnit could not run in this checkout because WORDPRESS_DEVELOP_DIR is not configured.

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the forno-326/jetpack-ai-to-page-site-editor branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack forno-326/jetpack-ai-to-page-site-editor

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions github-actions Bot added [Extension] AI Assistant Plugin [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Tests] Includes Tests labels Jun 25, 2026
@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!


Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

  • WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly:
    • Scheduled release: July 7, 2026
    • Code freeze: July 6, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Jun 25, 2026
@jp-launch-control

jp-launch-control Bot commented Jun 25, 2026

Copy link
Copy Markdown

Code Coverage Summary

Coverage changed in 1 file.

File Coverage Δ% Δ Uncovered
projects/plugins/jetpack/extensions/plugins/ai-assistant-plugin/ai-sidebar/class-jetpack-ai-sidebar.php 166/192 (86.46%) 0.66% 3 ❤️‍🩹

Full summary · PHP report · JS report

@kat3samsin kat3samsin changed the title AI Sidebar: gate provider exposure to proxied requests [FORNO-326] Add Jetpack AI abilities to Page/Site editor Jun 25, 2026
@kat3samsin kat3samsin force-pushed the forno-326/jetpack-ai-to-page-site-editor branch from a59d3e2 to 11aa799 Compare June 26, 2026 12:44
@kat3samsin kat3samsin marked this pull request as ready for review June 26, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Extension] AI Assistant Plugin [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Tests] Includes Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant