Skip to content

Move Studio Code Desktop from feature flag to beta flag#3549

Merged
sejas merged 4 commits into
trunkfrom
move-studio-code-to-beta-flag
Jun 2, 2026
Merged

Move Studio Code Desktop from feature flag to beta flag#3549
sejas merged 4 commits into
trunkfrom
move-studio-code-to-beta-flag

Conversation

@sejas
Copy link
Copy Markdown
Member

@sejas sejas commented May 20, 2026

Proposed Changes

  • Let's move Studio Code UI to beta flags so users can enable it in their end.

The ENABLE_STUDIO_CODE_UI env var is no longer wired. Users now toggle Studio Code Desktop from the macOS app menu under WordPress Studio → Beta Features → Studio Code Desktop. The choice persists in ~/.studio/app.json under betaFeatures.

Screenshot 2026-06-02 at 11 59 51

Testing Instructions

  • Start the app with npm start.
  • Open Electron → Beta Features in the macOS menu bar — the "Studio Code Desktop" item should be present and unchecked by default.
  • Open the Assistant tab on a site — the legacy WPCOM assistant should render.
  • Toggle Studio Code Desktop on; reopen the Assistant tab — the new Studio Code chat UI should render instead.
  • Toggle it back off; the legacy assistant should return.
  • Quit and relaunch the app — the toggle state should persist (verify in ~/.studio/app.json under betaFeatures.enableStudioCodeUi).
  • Confirm ENABLE_STUDIO_CODE_UI=true npm start no longer flips the UI (env var is intentionally removed).

Pre-merge Checklist

  • Have you checked for TypeScript, React or other console errors? (Tests pass, no errors)

@sejas sejas self-assigned this May 20, 2026
@sejas sejas force-pushed the move-studio-code-to-beta-flag branch from 7dd6678 to 2677552 Compare June 1, 2026 17:21
@sejas sejas force-pushed the move-studio-code-to-beta-flag branch from 2677552 to eacf983 Compare June 2, 2026 10:51
@sejas sejas marked this pull request as ready for review June 2, 2026 11:00
@sejas sejas requested review from a team, nightnei and youknowriad June 2, 2026 11:02
@youknowriad
Copy link
Copy Markdown
Contributor

What do you think about moving it to Stable directly for the next release (I'm working on metrics and I'll have a PR for that soon)?

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@youknowriad youknowriad left a comment

Choose a reason for hiding this comment

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

Approving but I'm wondering if we can go directly to stable.

@wpmobilebot
Copy link
Copy Markdown
Collaborator

wpmobilebot commented Jun 2, 2026

📊 Performance Test Results

Comparing b7e2455 vs trunk

app-size

Metric trunk b7e2455 Diff Change
App Size (Mac) 1329.74 MB 1329.74 MB 0.00 MB ⚪ 0.0%

site-editor

Metric trunk b7e2455 Diff Change
load 1682 ms 1621 ms 61 ms 🟢 -3.6%

site-startup

Metric trunk b7e2455 Diff Change
siteCreation 9067 ms 9028 ms 39 ms ⚪ 0.0%
siteStartup 4405 ms 4409 ms +4 ms ⚪ 0.0%

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

@sejas
Copy link
Copy Markdown
Member Author

sejas commented Jun 2, 2026

Approving but I'm wondering if we can go directly to stable.

Agreed! Let's aim to move it to stable to all users in next Studio release. Let's give it a bit more test these days and remove the beta flag too.

@sejas sejas enabled auto-merge (squash) June 2, 2026 11:47
@sejas sejas merged commit 6f0070d into trunk Jun 2, 2026
11 checks passed
@sejas sejas deleted the move-studio-code-to-beta-flag branch June 2, 2026 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants