feat(studio): provider management, model router, gateway + controller provider routes - #976
Closed
jtenniswood wants to merge 1 commit into
Closed
feat(studio): provider management, model router, gateway + controller provider routes#976jtenniswood wants to merge 1 commit into
jtenniswood wants to merge 1 commit into
Conversation
… provider routes The runtime-config half of settings, consolidated with its server side. Provider list/add/test/remove and the active-provider switch run through the local controller against the daemon's auth file — server-side ownership; booleans and key-shape probes cross the wire, never key material (the provider-auth suite has pinned that logic since the server-tier PR). Built-in providers take base-URL overrides; custom gateway providers are validated. The model-router editor offers the daemon's whole model inventory; the MCP gateway stays user-entered but always validated with HTTPS-only egress. The About-this-daemon card lands with server-info.ts, its only consumer. local-controller.mjs grows /providers* + /model-router GET/PUT and reaches its final state; workspace.spec.ts reaches its final five-surface state (the provider spec pins the external-mode deployment-owned posture end to end). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jtenniswood
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack 11/21 — Studio: provider management, model router, gateway + controller provider routes
The runtime-config half of settings, consolidated with its server side so every write path is reviewed next to the UI that drives it.
auth.yamlownership — booleans and key-shape probes cross the wire, never key material (provider-auth.mjs's 29-case suite has covered this logic since PR 3). Base-URL overrides for built-in providers; custom gateway providers.validateGatewayURL); the About-this-daemon card off the safe identity probe (server-info.tslands with its only consumer).local-controller.mjsgrows/providers*+/model-routerGET/PUT and reaches its final state; the hermetic suite andworkspace.spec.tsreach theirs (the provider e2e spec pins the external-mode "deployment-owned" read-only posture end-to-end).settings/provider/[name]+ theworkspace/provider/[name]legacy stub);use-harness-runtime,use-provider-management,model-preferences(+test).Demo at this stack point: add/test/remove providers, switch the active one, route models per category, set the MCP gateway (managed); everything read-only and deployment-owned in external mode.
Part of the stacked landing of #618. Size note: at the top of the series' review budget;
model-router-sectionis the named split-out if review stalls.🤖 Generated with Claude Code