Skip to content

feat(catalog): Opus ultracode tier, retire Fable 5, add model priority - #9

Merged
dorukozgen merged 1 commit into
mainfrom
feat/catalog-effort-priority-retire
Jun 23, 2026
Merged

dorukozgen merged 1 commit into
mainfrom
feat/catalog-effort-priority-retire

Conversation

@dorukozgen

Copy link
Copy Markdown
Contributor

Summary

Three model-metadata changes in the catalog, all consumed by the desktop model picker (companion PR in fleetifydev/fleetify):

  1. Opus ultracode tier — claude-opus-4-8 (+ [1m]) gain an ultra_code effort level above max. The picker now renders this Opus-only top tier data-driven instead of the app injecting it client-side.
  2. Retire Fable 5 — claude-code + anthropic Fable 5 get active = false. The picker shows it disabled (greyed, non-clickable); dispatch is blocked.
  3. priority field — new integer on [fleetify]. Model-picker sort weight: higher floats toward the top of its provider's list, ties keep catalog order, omitted ⇒ 0. Wired through defaults.ts / types.ts / schema and emitted on every model in dist (all 0 for now — set per model to reorder).

Verification

  • bun run validate ✓ — 17 providers, 132 models
  • bun run build ✓ — dist/ regenerated
  • bun test ✓ — 31/31

Notes

  • dist/ is regenerated and committed (repo's publish flow); non-claude-code provider files changed only in the generatedAt/commit stamp.
  • After merge, publish/tag so jsDelivr serves the new catalog (the desktop app's live model-list path reads it; effort/active/priority also work offline via the companion PR's regenerated snapshot).

🤖 Generated with Claude Code

Three model-metadata changes consumed by the desktop model picker:

- Opus 4.8 (+ 1M variant): add an `ultra_code` effort level above `max`
  so the picker renders the Opus-only top tier data-driven, instead of the
  app injecting it client-side.
- Retire Fable 5 (claude-code + anthropic): `active = false`. The picker
  shows it disabled (greyed, non-clickable) and dispatch is blocked.
- New `priority` integer on `[fleetify]`: model-picker sort weight. Higher
  floats the model toward the top of its provider's list; ties keep catalog
  order; omitted ⇒ 0. Wired through defaults/types/schema and emitted on
  every model in dist (all 0 for now — set per model to reorder).

Consumed by fleetifydev/fleetify (snapshot + picker) — see its companion PR.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dorukozgen
dorukozgen merged commit 82e7831 into main Jun 23, 2026
2 checks passed
@dorukozgen
dorukozgen deleted the feat/catalog-effort-priority-retire branch June 23, 2026 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant