Repository navigation
fix(videos): allow up to 9 reference images on Seedance 2.0 - #3027
Conversation
Seedance 2.0 (including Fast/Mini) supports up to 9 reference images per ByteDance's omni-reference documentation, but the shared video request schema hard-capped reference_images at 3 for every model. Raise the schema cap to 9 and enforce the real per-provider limits in the constraint checker: bytedance Seedance 2.0 accepts up to 9, all other providers keep the previous cap of 3. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughChangesThe gateway now supports provider-specific reference image limits: up to 9 for Seedance 2.0 and up to 3 for other providers. Tests cover acceptance and rejection cases, while the mock upstream server parses and stores reference images. Reference image limits
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
A user reported that Seedance 2.0 Fast only accepted up to 3 reference images, while ByteDance's official Seedance 2.0 omni-reference documentation states it supports up to 9 reference images (alongside up to 3 reference videos and 3 reference audio clips).
This was not Fast-specific: the shared
reference_imagesrequest schema inapps/gateway/src/videos/videos.tswas hard-capped at.max(3)for every video model, so all three Seedance 2.0 variants (seedance-2-0,seedance-2-0-fast,seedance-2-0-mini) were affected.Changes
videoReferenceImagesSchemacap from 3 → 9 (the maximum any model supports).getVideoProviderConstraintReasons:reference_imagesOpenAPI description to reflect the new range.reference_imagecontent items so forwarding can be asserted.Tests
New tests in
videos.spec.ts:The reference videos/audios
.max(3)caps already matched the docs and were left unchanged. Fullvideos.spec.tssuite (45 tests) passes.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Bug Fixes