fix: remove AI model config from Manage tab, clarify Configuration labels#797
Merged
fix: remove AI model config from Manage tab, clarify Configuration labels#797
Conversation
…bels The Manage tab's AI Model Policy card duplicated what the Configuration tab already provides. Manage should only handle the WordPress entity (identity, status, access) — not AI model selection. Also updates Configuration tab labels: removes 'Global' prefix since on single-agent installs there's no agent-level distinction, and rewords per-context description to reflect that contexts are the same agent running with different toolkits, not separate agents.
Homeboy Results —
|
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
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.
Summary
Before → After
Manage tab (before): Identity + AI Model Policy + Access Management
Manage tab (after): Identity + Access Management
Configuration tab: Unchanged structurally, just clearer labels
The backend model resolution cascade is untouched — per-agent overrides still work via REST API and CLI for multi-agent installs.