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 ed85e9a
Browse filesBrowse the repository at this point in the historyBrowse files
feat(agents): order the Databricks catalog newest-first
The gateway pages `api/ai-gateway/v2/endpoints` in two phases —
Databricks-managed endpoints first, then workspace-created ones (the page
token literally decodes to `{"phase":"user"}`) — each alphabetical by
name. Buzz sorted nothing, so that order reached the picker unchanged and
buried brand-new models: `databricks-claude-opus-5` sat 8th behind five
older Claude endpoints, and `goose-claude-opus-5` (the newest endpoint in
the catalog) sat 55th of 63.
Each endpoint carries `created_timestamp`, so sort on it: newest first,
ties broken by name. The tiebreak matters — eleven managed endpoints
share one placeholder timestamp (1699610000000), and without it their
relative order would be arbitrary between runs.
Sorting in `fetch_v2_models` means both discovery paths inherit it with
no wire or type changes: the desktop's in-process
`discover_databricks_models` and the `buzz-acp models --json` subprocess
both go through this function, and the combobox filter preserves incoming
order.
Endpoints with an absent or unparseable timestamp sort last rather than
first, so a wire-shape change degrades to "unordered at the bottom"
instead of "shuffled to the top". `created_timestamp` is accepted as
either a JSON string (what the gateway sends) or a bare number.
Live against block-lakehouse-production, top of the list is now:
goose-claude-opus-5 2026-07-24
databricks-claude-opus-5 2026-07-23
databricks-gemini-3-6-flash 2026-07-20
databricks-gemini-3-5-flash-lite 2026-07-20
databricks-inkling 2026-07-14
Caveat worth knowing: the placeholder timestamp is not always accurate
for managed endpoints, so a few genuinely recent ones
(`databricks-kimi-k2-7-code`, `databricks-llama-4-maverick`) land at the
bottom with the 2023 batch. The gateway gives us nothing better to sort
on.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
0 commit comments