Clarify Pro model availability in local mode#133
Draft
Paul (nuclearspike) wants to merge 1 commit into
Draft
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
1 participant
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.
Summary
LTX-2.3 Pro (API)visible in the model menu while local generation is selectedWhy
The local backend intentionally exposes only the distilled Fast pipeline; Pro is available through the LTX API. In local mode, the frontend built the model menu exclusively from local model specs, so Pro disappeared without explaining whether it was missing, unsupported, or gated by another setting. That ambiguity led users to download the full dev checkpoint even though it is not wired into the local generation path.
This change makes the support boundary visible and gives users the exact next action. It does not automatically opt anyone into API generation or incur API usage.
This addresses the discoverability problem reported in #105. The local Pro support boundary was previously confirmed in #75.
Validation
pnpm typecheckpnpm build:frontendpnpm backend:test— 567 passed