Repository navigation
feat: models grouped by provider, refreshed one provider at a time - #27
Merged
Merged
Conversation
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.
Note
Clanker Claude Opus 5.5 is responding on behalf of meetsu
The Models page now folds models under each provider, and each provider refreshes and switches on its own.
what changed
one folding section per provider or custom route, with enabled count, last read time, a refresh button and a switch for every shown model (
models-view.svelte).the open sections are remembered; a search opens the matching sections and filters their rows.
a model's id copies on click; the section heading stays in view while a long list scrolls.
POST /admin/api/models/refresh?pool=<id>rereads one pool and keeps every other pool's rows (AppState::refresh_models_in).GET /admin/api/modelsreturnslistings: each pool's last read andstalewhen its live listing failed.the poller rereads only stale pools each minute, replacing the global
models_incompleteflag.PATCH /admin/api/modelswith{"ids":[...],"enabled":bool}toggles many models in one config write.catalog refreshes run one at a time, and each reads the disabled list when it publishes, so a switch made meanwhile holds.
a failed Copilot or Antigravity live read keeps the previous rows and marks the pool stale, even when another account of the pool answered.
the flaky Windows heartbeat test now runs on real time with a 200 ms beat (
AppState::socket_heartbeat_ms, 25 s by default) instead of a paused clock.to question
the provider switch acts on the shown rows, so with a search it only touches the matches; that keeps a bulk change visible before it happens.
verified
cargo test --workspace --all-targets --locked: all pass, 260 tests, including 5 new ones;an_overlapping_refresh_keeps_newer_rows_and_switchesanda_failed_copilot_listing_is_marked_and_retriedfail on the first commit,one_answering_account_does_not_hide_another_ones_failureon b0232a7.pnpm --dir dash check: 0 errors, 0 warnings.listings.opencode_go.refreshed_at.captures
sticky heading while OpenRouter's list scrolls
phone, 390 px