Repository navigation
feat(models): offer fast mode on lucy-vton-3.6; lucy-vton-latest resolves to 3.6 - #222
Merged
Merged
Conversation
commit: |
This was referenced Oct 11, 2026
AdirAmsalem
approved these changes
Oct 12, 2026
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.
Description
Two updates for
lucy-vton-3.6, now that the API supports them:lucy-vton-3.6. The realtime registry entry gainssupportedSpeeds: ["fast"]. The API already serves 3.6 on the fast tier, billed at 2x the standard realtime rate like 3.5. Without this change,speed: "fast"on 3.6 logs a "model does not list it" warning. This applies to realtime only; batch has no speed tier.lucy-vton-latest→lucy-vton-3.6. The alias resolves server-side, so the SDK only updates comments, docs and test names. 3.5 and 3.6 have identical geometry: realtime 1280x720 at{ideal: 30, max: 30}, video 1280x720 at 20 fps. The alias entries keep their values, andlucy-vton-latestkeepssupportedSpeeds: ["fast"].Following the AGENTS.md runbook,
supportedSpeedsis added only now that the API actually serves 3.6 on the fast tier.Changes
src/shared/model.tssupportedSpeeds: ["fast"]on realtimelucy-vton-3.6; bothlucy-vton-latestcomments now point at 3.6src/realtime/client.ts,README.md,index.htmllucy-vton-3.6AGENTS.mdlucy-vton-latest→lucy-vton-3.6tests/unit.test.tsfastRealtimeModels(the pinned exact set); 3.6 asserts["fast"]; latest test titles say 3.6tests/realtime.unit.test.tsVerification
pnpm --filter @decartai/sdk typecheckpnpm --filter @decartai/sdk testpnpm --filter @decartai/sdk buildpnpm --filter @decartai/sdk test:packagepnpm --filter @decartai/sdk format:checkThe live e2e was not run locally because no
DECART_API_KEYwas available.Compatibility
Additive.
models.realtime("lucy-vton-3.6").supportedSpeedschanges fromundefinedto["fast"]. No ids, geometry or types change.Server-side
lucy-vton-3.6is already live on the API.lucy-vton-latest→ 3.6 alias change is rolling out on the API separately. Only docs and comments here depend on it, so merge order doesn't matter.Companion PRs (lucy-vton-3.6: fast mode +
lucy-vton-latest→ 3.6)Open workspace in Conductor