Repository navigation
feat: fast mode on lucy-vton-3.6; lucy-vton-latest resolves to 3.6 - #73
Merged
Merged
Conversation
- Advertise supported_speeds=("fast",) on the realtime lucy-vton-3.6
definition (backend serves 3.6 on the fast tier, billed at 2x).
- Update fast-capable model lists in the unsupported-speed warning,
RealtimeConnectOptions.speed docstring, README, examples, playground.
- lucy-vton-latest now resolves server-side to lucy-vton-3.6 (geometry
unchanged); update comments/docs accordingly.
- Tests: add lucy-vton-3.6 to FAST_REALTIME_MODELS and the no-warning
list; flip the assertion that 3.6 has no fast tier.
This was referenced Oct 11, 2026
Merged
AdirAmsalem
approved these changes
Oct 12, 2026
tomershlasky
added a commit
to DecartAI/sdk
that referenced
this pull request
Oct 12, 2026
…lves to 3.6 (#222) ## Description Two updates for `lucy-vton-3.6`, now that the API supports them: 1. **Fast mode on `lucy-vton-3.6`.** The realtime registry entry gains `supportedSpeeds: ["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. 2. **`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, and `lucy-vton-latest` keeps `supportedSpeeds: ["fast"]`. Following the AGENTS.md runbook, `supportedSpeeds` is added only now that the API actually serves 3.6 on the fast tier. ## Changes | File | Change | | --- | --- | | `src/shared/model.ts` | `supportedSpeeds: ["fast"]` on realtime `lucy-vton-3.6`; both `lucy-vton-latest` comments now point at 3.6 | | `src/realtime/client.ts`, `README.md`, `index.html` | fast-mode model lists now include `lucy-vton-3.6` | | `AGENTS.md` | removes "opt-in by name; no fast tier" from 3.6; `lucy-vton-latest` → `lucy-vton-3.6` | | `tests/unit.test.ts` | adds 3.6 to `fastRealtimeModels` (the pinned exact set); 3.6 asserts `["fast"]`; latest test titles say 3.6 | | `tests/realtime.unit.test.ts` | adds 3.6 to the "no speed warning" loop | ## Verification | Command | Result | | --- | --- | | `pnpm --filter @decartai/sdk typecheck` | pass | | `pnpm --filter @decartai/sdk test` | 386 passed (15 files) | | `pnpm --filter @decartai/sdk build` | pass | | `pnpm --filter @decartai/sdk test:package` | pass | | `pnpm --filter @decartai/sdk format:check` | 86 files, clean | The live e2e was not run locally because no `DECART_API_KEY` was available. ## Compatibility Additive. `models.realtime("lucy-vton-3.6").supportedSpeeds` changes from `undefined` to `["fast"]`. No ids, geometry or types change. ## Server-side - Fast mode for `lucy-vton-3.6` is already live on the API. - The `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) - JS SDK: #222 - Python: DecartAI/decart-python#73 - iOS: DecartAI/decart-ios#49 - Android: DecartAI/decart-android#34 - C++: DecartAI/decart-cpp#15 <!-- conductor-workspace-link --> --- [Open workspace in Conductor](https://app.conductor.build/decart/w/261)
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.
Summary
Mirrors the JS SDK (DecartAI/sdk) changes for the Python SDK:
lucy-vton-3.6(realtime only). The API now serves 3.6 on thespeed="fast"tier, billed at 2x like 3.5. The realtimelucy-vton-3.6definition now advertisessupported_speeds=("fast",), the same as 3.5. The video/batch definition is unchanged.lucy-vton-latestnow resolves server-side tolucy-vton-3.6(it was 3.5). The geometry is the same (realtime 1280x720 @ 30fps, video 1280x720 @ 20fps), so only comments, docs and examples change.Fast-capable realtime set is now:
lucy-2.5,lucy-latest,lucy-vton-3.5,lucy-vton-3.6,lucy-vton-latest.Changes
decart/models.py: addsupported_speeds=("fast",)to realtimelucy-vton-3.6. Update the unsupported-speed warning text. Change thelucy-vton-latestalias comments (realtime + video) to say it resolves to 3.6.decart/realtime/types.py: update the fast-capable list in theRealtimeConnectOptions.speeddocstring.tests/test_models.py: addlucy-vton-3.6toFAST_REALTIME_MODELS. Change the old "3.6 has no fast tier" assertion to("fast",). Rename the pinning test to..._vton_3_5_3_6. Add comments noting thatlucy-vton-latestresolves to 3.6.tests/test_realtime_unit.py: addlucy-vton-3.6to the models that must not warn onspeed="fast".README.md,examples/README.md,examples/realtime_synthetic.py,examples/video_tryon.py,playground/playground.py: update the fast-mode model lists and alias wording.No version bump or release.
Verification
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. This PR only changes docs/comments for the alias (geometry and fast capability are identical for 3.5 and 3.6), so merge order doesn't matter.Note
Low Risk
Registry metadata, docs, and test expectations only; no auth, billing logic, or connection behavior changes beyond advertising fast for 3.6.
Overview
Adds realtime fast mode (
speed="fast") forlucy-vton-3.6by settingsupported_speeds=("fast",)on its realtimeModelDefinition, matchinglucy-vton-3.5. Docs, warnings, examples, and the playground now list 3.6 among fast-capable models.Documents that
lucy-vton-latestresolves server-side tolucy-vton-3.6(was 3.5) in registry comments and user-facing text; video/batch geometry is unchanged. Tests pin the fast-capable realtime set and expect no warning when connecting withspeed="fast"on 3.6.Reviewed by Cursor Bugbot for commit 0dcc3c5. Bugbot is set up for automated code reviews on this repo. Configure here.
Companion PRs (lucy-vton-3.6: fast mode +
lucy-vton-latest→ 3.6)