Studio Agentic UI: Define signed-out experience for Agentic UI chat

[katinthehatsite]

Related issues

Fixes STU-1898

How AI was used in this PR

It was used to extract the changes that were suggested in the exploration from #3975

Proposed Changes

This PR adds a logged-out experience for the users for the agentic UI:

Testing Instructions

• Pull the changes from this branch
• Start Studio with npm start
• Enable the Agentic UI feature flag from Studio -> Feature flags from the topbar
• Log out of WordPress.com
• Observe that New chat button is disabled
• Observe that when you select a specific site, you get redirected to its settings with the log in banner
• Observe the Log in button in the sidebar
• Confirm that the Share button for the previews is disabled and it asks you to log in to share the link

• Confirm that log in button works as expected and that once you log in, all the disabled options become available

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[bcotrim]

I did some brief testing.
Some initial comments:

• I believe this branch needs to adjust to the latest trunk updates
• While offline I still see my sites when I try publish:

[katinthehatsite]

I believe this branch needs to adjust to the latest trunk updates

I just did the rebase 👍

While offline I still see my sites when I try publish

I have not tested the offline mode yet, I will take a look now. I will check if it makes sense to handle this as a part of this PR or open a completely new issue to handle the offline mode across the whole agentic UI

[katinthehatsite]

@bcotrim for the offline mode, I think we need a separate issue. I will create one in Linear, there are multiple elements that need to de handled holistically e.g. Log in button, Publish button, New chat button, some sort of indication that the user is offline. I think we can focus on logged out screen in this PR, and handle the offline mode separately. What do you think?

[wpmobilebot]

📊 Performance Test Results

Comparing e3b2570 vs trunk

app-size

Metric	trunk	e3b2570	Diff	Change
App Size (Mac)	1352.92 MB	1352.93 MB	+0.01 MB	⚪ 0.0%

site-editor

Metric	trunk	e3b2570	Diff	Change
load	1034 ms	1096 ms	+62 ms	🔴 6.0%

site-startup

Metric	trunk	e3b2570	Diff	Change
siteCreation	6999 ms	7003 ms	+4 ms	⚪ 0.0%
siteStartup	2351 ms	2353 ms	+2 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

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

[bcotrim]

@bcotrim for the offline mode, I think we need a separate issue. I will create one in Linear, there are multiple elements that need to de handled holistically e.g. Log in button, Publish button, New chat button, some sort of indication that the user is offline. I think we can focus on logged out screen in this PR, and handle the offline mode separately. What do you think?

Yes, I think it makes sense to address offline mode in a separate issue.
I did mean to say "logged-out" in my test, I didn't check offline mode 😅

[katinthehatsite]

I did mean to say "logged-out" in my test, I didn't check offline mode 😅

I see what you mean now - I have adjusted the dropdown to show only the button to create a site when the user is logged out without loading all the other sites. This is how it looks like when the user is logged out:

Let me know what you think!

[bcotrim]

I did mean to say "logged-out" in my test, I didn't check offline mode 😅

I see what you mean now - I have adjusted the dropdown to show only the button to create a site when the user is logged out without loading all the other sites. This is how it looks like when the user is logged out:

Let me know what you think!

I think that's good for now, we can ask @shaunandrews for a review to get his thoughts on it.

However the request to fetch the sites is still being made, so we get this on the logs:

Error occurred in handler for 'fetchSyncableWpcomSites': Error: Authentication required to fetch WordPress.com sites.
    at fetchSyncableWpcomSites (/Users/bcotrim/.mognet/worktrees/studio/mognet-37cfb615/apps/studio/dist/main/index.js:48639:33)
    at async Session.<anonymous> (node:electron/js2c/browser_init:2:116010)
Error occurred in handler for 'fetchSyncableWpcomSites': Error: Authentication required to fetch WordPress.com sites.
    at fetchSyncableWpcomSites (/Users/bcotrim/.mognet/worktrees/studio/mognet-37cfb615/apps/studio/dist/main/index.js:48639:33)
    at async Session.<anonymous> (node:electron/js2c/browser_init:2:116010)
Error occurred in handler for 'fetchSyncableWpcomSites': Error: Authentication required to fetch WordPress.com sites.
    at fetchSyncableWpcomSites (/Users/bcotrim/.mognet/worktrees/studio/mognet-37cfb615/apps/studio/dist/main/index.js:48639:33)
    at async Session.<anonymous> (node:electron/js2c/browser_init:2:116010)
Error occurred in handler for 'fetchSyncableWpcomSites': Error: Authentication required to fetch WordPress.com sites.
    at fetchSyncableWpcomSites (/Users/bcotrim/.mognet/worktrees/studio/mognet-37cfb615/apps/studio/dist/main/index.js:48639:33)
    at async Session.<anonymous> (node:electron/js2c/browser_init:2:116010)

I think we should prevent the request from being made, if possible.