Repository navigation
Keep tenant default from rewriting every agent Model column (CL-6782) - #612
Merged
TheGreatAxios merged 2 commits intoSep 4, 2026
Conversation
Contributor
Author
Self-reviewVerdict: the diff is comments/copy/tests only — the underlying behavior (unset model stays "Default",
No fixes made; nothing confirmed-open. Targeted tests:
|
Changing Settings default must not PATCH agent capabilities, and the roster Model column must keep stored values (unset stays Default).
Settings default-model pick stays an offering-priority write. Existing agents keep stored capabilities.model; new agents may still default at create. Unset roster cells stay Default, never the live catalog winner.
TheGreatAxios
force-pushed
the
cl-6782-changing-tenant-default-rewrites-every-agent-model-column
branch
from
September 4, 2026 05:49
de04d5b to
4e730cc
Compare
TheGreatAxios
changed the base branch from
cl-6748-agents-roster-shows-slug-idledeployed-shout-and-raw-model
to
main
September 4, 2026 05:49
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.
Stacked on CL-6748 (PR #602). Changing Settings tenant default must leave existing agents stored Model values unchanged. New agents may still pick up the default at create.
Connections chooseModel PATCHes offering priority only — never agent-definitions. The roster reads stored capabilities.model; unset stays a stable Default, never the live catalog winner. Catalog mapping for a set model still uses displayName from 6748.
Fixes CL-6782