feat(site): scope chat model settings to organizations - #27960
Draft
ethanndickson wants to merge 1 commit into
Draft
feat(site): scope chat model settings to organizations#27960ethanndickson wants to merge 1 commit into
ethanndickson wants to merge 1 commit into
Conversation
ethanndickson
force-pushed
the
ethan/codagt-709-model-config-frontend
branch
from
August 10, 2026 06:57
0505466 to
143f1aa
Compare
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.
Part of CODAGT-709.
Moves the AI model settings under
/ai/settings/organizations/:organization/models, with an organisation switcher and redirects from the legacy paths. Provider state is rebuilt from the server's redacted descriptors instead of deployment values, the agents sidebar fetches models once per organisation the user belongs to (failures downgrade to a partial error rather than blanking the page), and the page-levelRequirePermissiongate is gone: the server's RBAC filter is the source of truth, and the UI gate is advisory. The fan-out exists because the model catalog is now per-organisation and there is deliberately no cross-organisation union endpoint; requests run in parallel and most users are in one or two organisations, so this is fine for now, but a union endpoint is the natural follow-up if deployments with many organisations per user find it costly.One shared-component change to flag:
OrganizationAutocompletenow sorts deterministically (active organisation first, then alphabetical), and gainsariaLabel/triggerClassNameprops plus a keyboard-navigation workaround for a cmdk issue. The sort change is visible in the template and user creation forms too, since they share the component.Must merge together with the API PR below it, which deletes the routes this branch stops calling.