You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3637b65
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(provider-core): expose model metadata through a ModelCatalog port
Antigravity, Claude, and Codex read the server's ModelManifest service
directly, so they could not leave apps/server. The manifest itself
(bundle, remote refresh, disk cache, compatibility policies) stays with
the server; providers now see only their own catalog entry through
@t3tools/provider-core/server/ModelCatalog:
- current(driverKind) / bundled(driverKind): the driver's catalog from
the manifest in memory or the bundle. Never fetches.
- refreshInBackground: the TTL-gated remote refresh drivers start from
provider checks.
- Pure helpers: classifyCatalogModels, applyCatalogDefault,
applyModelCatalog, catalogServerModel, with an optional CatalogMatching
so a driver maps its slugs to catalog families.
Provider-specific branches leave the generic code: Codex's family
matching and update-required models move to codexModelCatalog.ts, and
Claude's catalog resolves from its ProviderCatalog entry. The server's
ModelManifest module provides the port (layerModelCatalog), and its
layerTest provides both.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments