You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On localhost, WrongOrigin is expected because the tokens belong to the production domains. This local check confirms the updated tokens and expiry are included in both pages.
Summary by CodeRabbit
Chores
Updated WebMCP trial metadata on the personal WordPress and website playgrounds. The current token is valid through March 30, 2027, replacing one that expired November 17, 2026. This keeps the trial metadata current for visitors using these playgrounds; the metadata’s placement and the rest of the pages remain unchanged.
No actionable comments were generated in the recent review.
Walkthrough
The personal WordPress and website playground entry points now use WebMCP origin-trial metadata with tokens expiring 2027-03-30, replacing Chrome 156 trial metadata that expired 2026-11-17.
WordPress/wordpress-playground#3844: This PR updates WebMCP registration to use document.modelContext; both PRs concern WebMCP in the same entry points.
Suggested reviewers:fellyph
Merge Risk: Minimal · up to 0b00b
This renews the WebMCP origin-trial tokens so the feature keeps working past the November 2026 expiry. No merge-blocking risk was found; confirm the token status in Chrome DevTools after deployment.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title clearly and concisely describes the main change: renewing WebMCP origin-trial tokens for the website.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 8278ac5e-e4b6-4a3c-9f7f-bda252350cdc
Commits
Reviewing files that changed from the base of the PR and between ada3b06 and 0b00bc1.
Files selected for processing: 2
packages/playground/personal-wp/index.html
packages/playground/website/index.html
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renew the WebMCP origin trial for my.wordpress.net and playground.wordpress.net through March 30, 2027.
Motivation for the change, related issues
The current tokens expire on November 17, 2026. Renewing them keeps WebMCP available in Chrome while the API remains in origin trial.
Implementation details
Replace both origin-trial tokens and update the expiry comments in the HTML entry points.
Testing Instructions
npm run dev.npm exec nx -- dev playground-personal-wp, and open http://127.0.0.1:5401/website-server/. Repeat the DevTools check.On localhost, WrongOrigin is expected because the tokens belong to the production domains. This local check confirms the updated tokens and expiry are included in both pages.
Summary by CodeRabbit