fix(custom-model): show which model a session is using when an endpoint cannot report it

Only llama-swap answers what is loaded, so behind a gateway such as Bifrost
nothing was marked and the picker fell back to discovery order apart from the
one CLI that had launched there before. A live session whose own injected
endpoint is that host now promotes its model as "In use by a session", under
its own tag and below llama-swap's "Currently loaded" answer, reading only
what Codeman injected rather than terminal text, and never a stopped session.
When genuinely nothing is known the picker says so instead of leaving an
unmarked wall, and stays quiet for an endpoint that merely failed to answer.
This commit is contained in:
Devvyn committed 2026-11-02 19:05:22 +08:00
1 parent 884e67d07e
commit 1f0823c582
7 files changed
+336 -40

No files matched your search

+11
View File
@@ -7824,6 +7824,17 @@ html[data-skin="og"] .welcome-primary:hover {
padding: 1rem 0;
}
/* "This endpoint cannot report which model it has loaded": the same `.form-hint`
`display: block` beats `[hidden]` trap the two rules below fix for the no-matches
line and the filtered rows, so the attribute needs the same re-assertion. */
#customModelPickModal .custom-model-pick-unknown {
padding-bottom: 0.15rem;
}
#customModelPickModal .custom-model-pick-unknown[hidden] {
display: none !important;
}
/* Same class of bug as the row rule below: the no-matches line carries
`.form-hint`, whose `display: block` outranks the UA `[hidden]` rule, so
`filterCustomModelPick()` toggling `hidden` changed nothing on screen and