Agentic: Studio Code AI semi-open beta - #4456
Conversation
095556b to
582886e
Compare
582886e to
9ef388d
Compare
📊 Performance Test ResultsComparing ad466c7 vs trunk app-size
site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
sejas
left a comment
sejas
left a comment
There was a problem hiding this comment.
Code looks good. I hardcoded some variables to verify it, because I got some issues when testing it with the backend.
copy
Let's just make sure the message of closed beta appears first and above any other message like payment required. #4422
| export function formatAiBlockedNotice(): string { | ||
| return __( | ||
| 'Studio Code AI is unavailable for this WordPress.com account. If you believe this is a mistake, contact WordPress.com support.' | ||
| 'Studio Code AI is blocked for this WordPress.com account. If you believe this is a mistake, contact WordPress.com support.' |
There was a problem hiding this comment.
We can consider adding a URL to contact us. Maybe https://wordpress.com/support/contact/
| export function formatAiAccessRequiredNotice( | ||
| quota?: Pick< StudioAssistantQuota, 'costUsage' > | null | ||
| ): string { | ||
| if ( quota && quota.costUsage > 0 ) { |
There was a problem hiding this comment.
This will only identify users who used Studio Code during this month.
There was a problem hiding this comment.
Yeah, I know. We reset it in the DB and I haven't found info about usage in teh past, so decided to go this way. it's already 5-th of August and we will release it later, so if somebody hasn't used Studio code for the last ~10 days, probably it's not a problem to show the default notice.
I was considering to check for stored chats locally, it's an option, but this way adds a lot of code and I am nt sure that it's very critical.
WDYT, Antonio?
| return __( | ||
| 'Thanks for participating in the Studio Code AI beta. Access is now limited. Apply to continue at <applyLink>developer.wordpress.com/studio/studio-code-beta</applyLink>.' |
There was a problem hiding this comment.
Let's add a translators comment in both versions of the string.
| return __( | |
| 'Thanks for participating in the Studio Code AI beta. Access is now limited. Apply to continue at <applyLink>developer.wordpress.com/studio/studio-code-beta</applyLink>.' | |
| return __( | |
| /* translators: <applyLink> and </applyLink> wrap the beta application URL and must be kept as-is. */ | |
| 'Thanks for participating in the Studio Code AI beta. Access is now limited. Apply to continue at <applyLink>developer.wordpress.com/studio/studio-code-beta</applyLink>.' |
3 participants
Related issues
How AI was used in this PR
AI assisted
Proposed Changes
This PR is a preparation for switching Studio Code AI to semi-open beta with access-request flow.
Access blocked by default (existing user)
Access blocked by default (new user)
Access blocked manually
Testing Instructions
See testing instructions in 163871-ghe-Automattic/missioncontrol