Enable Jetpack Offline Mode on Studio sites by default (PROTECT-192) - #4705
Draft
agent-sandbox-automattic[bot] wants to merge 1 commit into
Draft
Enable Jetpack Offline Mode on Studio sites by default (PROTECT-192)#4705agent-sandbox-automattic[bot] wants to merge 1 commit into
agent-sandbox-automattic[bot] wants to merge 1 commit into
Conversation
…ine Mode Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related issues
How AI was used in this PR
Fully AI-generated: the agent located both
defaultConstantsblocks (one for the Playground runtime, one for the native PHP runtime), added the constant to each, and wrote this PR. The diff was reviewed by the agent before committing.Proposed Changes
Studio sites now have
JETPACK_DEV_DEBUG=trueinjected into every WordPress configuration, which puts Jetpack into Offline Mode. This ensures Jetpack Account Protection is automatically bypassed on local development sites — users won't hit Jetpack's login protection or other network-dependent Jetpack features when working locally.The constant is added to the shared
defaultConstantsobject that is applied to every site's blueprint at startup, so the behavior is consistent across both the Playground (WASM) and native PHP runtimes, and works whether or not the user has a custom blueprint.Testing Instructions
JETPACK_DEV_DEBUGistrueinwp-config.php(e.g.wp eval 'echo JETPACK_DEV_DEBUG;'via Studio's WP-CLI).wp jetpack statusshould show offline/development mode).Pre-merge Checklist
Linear: PROTECT-192