-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HACK week] Allow merchants to use their own API keys for AI-powered features #15372
base: trunk
Are you sure you want to change the base?
Conversation
If a merchant has submitted its own key in AI settings, use that one for performing the identifyLanguage call rather than the WPCOM-JP wrapper
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Generated by 🚫 Danger |
|
So we can distinguish if the AI usage comes internally or from the merchant’s API
this has been moved to be stored in keychain, test is no longer valid
Description
This PR explores allowing merchants to use their own API keys for existing WCiOS AI-powered features, like product AI creation.
We extend the ability to use those it to all merchants by allowing them to use their own OpenAI or Anthropic API keys, which allows them to create generative products for their WooCommerce stores on demand, rather than relying on WPCOM/JPAI eligibility.
P2: pdfdoF-6LE-p2
TODO: Clean-up:
AI Settings
row + eligibility checker: [HACK][Merchant AI key] Add feature flag & render settings row if eligible #15404GenerativeContentRemote
+ testsAISettingsView
+ ViewModelRELEASE-NOTES.txt
if necessary.Reviewer (or Author, in the case of optional code reviews):
Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement: