Add developer settings mode with the ability to set desired provider and model per feature#486
Conversation
…one to toggle developer mode on and off
…r mode is turned on
…oper only settings
…lt that to text_generation. Override this in alt text and image generation to be vision and image_generation
… mode is on, get all providers and models. When a feature is turned on, output a select input and populate that with providers. When a provider is selected, show a models dropdown and populate that with models for that provider. Ensure these are saved anytime they change
…ion with the other setting fields. Adjust styles a bit
…Add a method that will use this data, if it exists, on the prompt builder
…the provider/model override setting
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #486 +/- ##
=============================================
+ Coverage 68.10% 69.14% +1.03%
- Complexity 1059 1066 +7
=============================================
Files 65 66 +1
Lines 5039 5175 +136
=============================================
+ Hits 3432 3578 +146
+ Misses 1607 1597 -10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hi @dkotter, I tried testing this PR using the “Try it in Playground” button, but it doesn’t seem to be working. When Playground opens, it shows a “Blueprint execution failed” error and isn’t able to download/install the plugin from the CI artifact URL.
|
|
@dkotter PlayGround button is not working
|
|
@itsgajendraSingh @raftaar1191 The Playground link should work now. Note the GitHub Action that adds that Playground link is a bit flakey and doesn't seem to always work when a new commit is pushed (seems to fairly often update the referenced build even if that build doesn't exist). I'd recommend for best results to just pull the PR down and test locally. |
jeffpaul
left a comment
There was a problem hiding this comment.
Its not immediately clear when clicking the new gear icon and its color/state changing is doing (even with the "Developer mode" on-hover text). So perhaps we switch to the vertical ellipses like Gutenberg and add one item there to select/check/enable for "Model selection" with description of "Select the specific provider and model per feature"?
This has been updated now (also updated screenshots in the PR description). I did add this menu item in a |
…select. Add a class to our reset button so we can target that specifically for style changes to avoid having those styles leak
Misalignment was my fault, overaggressive CSS that was impacting that which I've fixed now. For the missing caret, this is actually expected here. This page is using So what you're seeing here is you can click into the input and start typing and it will show you options that match. But that means it's slightly different than a normal select that just shows you dropdown items (and that will render that caret). That said, for now I've forced these inputs to always use the normal |
… hiding everything behind the loading spinner
Updated now to show the label with the spinner icon below instead of hiding everything with that spinner |
jeffpaul
left a comment
There was a problem hiding this comment.
Awesome, happy to see this merge into 0.9.0 today if you're good with that






What?
Add a new "developer mode" option on the settings page that when toggled on, shows a new settings section on each feature that allows you to choose the desired provider and model.
Why?
While the average user may not care about the actual model being used for a feature (and likely won't know the difference between the dozens of model options) there are certainly users and situations where setting the desired provider (and optionally model) is desired and beneficial.
Since we don't want to overwhelm users with settings they don't care about, we're hiding these new options behind a "developer mode" that can be toggled on and off.
How?
Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Sonnet 4.6
Used for: Initial review and plan; executed on that plan and wrote tests; final review and tweaking done by me
Testing Instructions
npm i && npm run buildSettings > AIScreenshots or screencast
Changelog Entry