[Partner Nodes] feat(ByteDance): add 1080p resolution to Seedance 2.5

[bigcat88]

API Node PR Checklist

Scope

• Is API Node Change

Pricing & Billing

• Need pricing update
• No pricing update

If Need pricing update:

• Metronome rate cards updated
• Auto‑billing tests updated and passing

QA

• QA done
• QA not required

Comms

• Informed Kosinkadink

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0633ad9e-fb24-4ed7-9625-2a41638dad0b

📥 Commits

Reviewing files that changed from the base of the PR and between 0d80858 and d2c1683.

⛔ Files ignored due to path filters (1)

• comfy_api_nodes/apis/bytedance.py is excluded by !comfy_api_nodes/apis/**

📒 Files selected for processing (1)

• comfy_api_nodes/nodes_bytedance.py

Included review availability: Your plan includes up to 10 reviews per rolling hour; 9 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (8)

• GitHub Check: Run Pylint
• GitHub Check: test (ubuntu-latest)
• GitHub Check: test
• GitHub Check: test (windows-latest)
• GitHub Check: test (windows-2022)
• GitHub Check: test (macos-latest)
• GitHub Check: test (ubuntu-latest)
• GitHub Check: test (macos-latest)

🧰 Additional context used

📓 Path-based instructions (6)

**/*

📄 CodeRabbit inference engine (AGENTS.md)

**/*: Keep changes small, direct, and limited to the narrowest necessary code path and smallest number of files.
Prefer practical fixes, minimal dependencies, and existing repository patterns; remove obsolete, dead, unreachable, or unused code.
Preserve existing APIs, node names, model-loading behavior, file layout, and workflow compatibility unless replacement is explicitly intended.
Core ComfyUI must not add outbound internet requests, telemetry, tracking, reporting, remote configuration, or background network activity. User-authorized model downloads are limited to the requested artifact and must exclude telemetry and unrelated metadata.

Files:

• comfy_api_nodes/nodes_bytedance.py

**/*.py

📄 CodeRabbit inference engine (AGENTS.md)

**/*.py: Keep state and capability flags on the object that owns the behavior. Prefer explicit parent-owned attributes over probing child objects with getattr; use child checks only when the child owns the delegated behavior.
Preserve shared method signatures, argument order, return shapes, side effects, and error behavior unless every affected caller and interface is intentionally updated.
Do not add unused compatibility parameters, flags, attributes, constructor options, or model-specific options to shared helpers; keep one-off behavior at the integration boundary.
Normalize third-party return conventions at integration boundaries so core code receives the expected type and shape; avoid undocumented caller-side unwrapping.
Do not add torch.no_grad, torch.inference_mode, or inference-mode wrappers. Do not add model freeze/unfreeze toggles; only disable globally enabled inference mode when a training path requires gradients.
Remove inference-only training behavior such as dropout while preserving checkpoint and state-dict compatibility; use nn.Identity when deleting a module would alter keys or ordering.
Keep imports at module scope except established optional-backend probes or imports required to avoid cycles; avoid unnecessary try/except blocks and use specific exceptions with useful fallbacks.
Do not add workarounds for unsupported library versions, especially PyTorch exception-and-float-cast retries, unless a comment names the exact versions still requiring them.
Let unsupported model formats, invalid quantization metadata, and bad states fail with clear errors instead of silently degrading output.
Match local style, keep comments sparse and useful, and remove comments that merely restate obvious code.
Treat dtype, device placement, VRAM use, and offloading as correctness concerns across CPU, CUDA, ROCm, MPS, DirectML, XPU, NPU, and low-VRAM environments.
Prefer existing ComfyUI and Comfy Kitchen operations, quantization helpers, cast/offload helpe...

Files:

• comfy_api_nodes/nodes_bytedance.py

**/*.{py,json}

📄 CodeRabbit inference engine (AGENTS.md)

Treat legacy combo, io.Combo, and io.DynamicCombo values affecting filesystem access as untrusted; revalidate them at load/save boundaries with folder_paths, containment checks, or fixed allowlists.

Files:

• comfy_api_nodes/nodes_bytedance.py

**/*.{py,md,txt,json}

📄 CodeRabbit inference engine (AGENTS.md)

Keep warning and info messages short and actionable, remove noisy or misleading logging, and make documentation edits concise, factual, and tied to changed behavior.

Files:

• comfy_api_nodes/nodes_bytedance.py

**

⚙️ CodeRabbit configuration file

**: IMPORTANT: Only comment on issues directly introduced by this PR's code changes.
Treat AGENTS.md as mandatory repository policy, not optional style guidance.
Flag PR changes that violate AGENTS.md even when the code is otherwise functional.
In particular, enforce architecture boundaries, dtype/device/memory rules,
interface contracts, import style, no unnecessary try/except blocks, no inline
imports, no outbound internet paths in core ComfyUI, and narrow scoped fixes.
Prefer direct findings over suggestions when a rule is violated. Only ignore
AGENTS.md when it clearly conflicts with a newer explicit maintainer instruction
in the PR.
Do NOT flag pre-existing issues in code that was merely moved, re-indented,
de-indented, or reformatted without logic changes. If code appears in the diff
only due to whitespace or structural reformatting (e.g., removing a with: block),
treat it as unchanged. Contributors should not feel obligated to address
pre-existing issues outside the scope of their contribution.

Files:

• comfy_api_nodes/nodes_bytedance.py

comfy_api_nodes/**

⚙️ CodeRabbit configuration file

comfy_api_nodes/**: Third-party API integration nodes. Focus on:

• No hardcoded API keys or secrets
• Proper error handling for API failures (timeouts, rate limits, auth errors)
• Correct Pydantic model usage
• Security of user data passed to external APIs

Files:

• comfy_api_nodes/nodes_bytedance.py

🧠 Learnings (10)

📚 Learning: 2026-02-21T14:01:41.482Z

Learnt from: pythongosssss
Repo: Comfy-Org/ComfyUI PR: 12555
File: comfy_extras/nodes_glsl.py:719-724
Timestamp: 2026-02-21T14:01:41.482Z
Learning: In PyOpenGL, bare Python scalars can be accepted for 1-element array parameters by NumberHandler. This means you can pass an int/float directly to OpenGL texture deletion (e.g., glDeleteTextures(tex)) without wrapping in a list. Verify function-specific expectations and ensure types match what the OpenGL call expects; use explicit lists only when the API requires an array.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-04-18T16:55:46.724Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 13465
File: comfy_api_nodes/nodes_bytedance.py:1496-1506
Timestamp: 2026-04-18T16:55:46.724Z
Learning: In `comfy_api_nodes` Python async node implementations (e.g., `async def execute`), synchronous CPU/IO-heavy helpers (such as video/audio trim/resize and base64/MP3 conversion) may be called directly without offloading to a thread executor (e.g., `asyncio.to_thread`). Treat this as an existing, broader refactor concern rather than a new PR regression: if the PR does not introduce additional synchronous blocking calls, reviewers should not flag it as a new issue. However, if the PR adds new synchronous CPU/IO work inside `async def execute`, prefer offloading with `asyncio.to_thread` (or an equivalent background executor) to avoid blocking the event loop.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-05-07T17:59:26.050Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 13753
File: comfy_api_nodes/nodes_gemini.py:1148-1157
Timestamp: 2026-05-07T17:59:26.050Z
Learning: In ComfyUI node implementations under `comfy_api_nodes/`, when building JSONata expressions that use `IO.PriceBadge` for `$lookup` against a price map keyed in lowercase, do not add an explicit `$lowercase()` around widget values (e.g., combo options like "1K", "2K", "4K"). The ComfyUI frontend automatically lowercases widget values before evaluating the JSONata expression, so the lookup keys will already match the lowercase map entries.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-07-14T20:09:03.091Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 14928
File: comfy_api_nodes/nodes_sync_so.py:168-202
Timestamp: 2026-07-14T20:09:03.091Z
Learning: In the `comfy_api_nodes/` package, partner/API node `execute` implementations should keep the full submit → poll → status-check → download flow written inline within each node (even if similar logic appears across multiple nodes). This is an intentional repo convention to optimize per-node readability and independent editability, so during reviews you should generally not recommend refactoring this pattern into a shared helper function for these nodes (unless there’s a concrete correctness/security issue).

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-07-16T16:29:35.022Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 14958
File: comfy_api_nodes/nodes_heygen.py:554-558
Timestamp: 2026-07-16T16:29:35.022Z
Learning: When implementing ComfyUI API nodes in this repo, for any billable HTTP POST operations, follow the established policy: keep the existing default retry behavior. Do not add idempotency keys or disable retries. The rationale is to prevent failures from aborting the entire workflow; when reviewing new API nodes, check that POST billing requests preserve the default retry configuration and remain consistent with this policy.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-08-04T18:49:57.785Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 15295
File: comfy_api_nodes/nodes_bfl.py:1037-1051
Timestamp: 2026-08-04T18:49:57.785Z
Learning: When consuming dictionaries produced by IO.Autogrow.Type, rely on their iteration order to match the configured template-slot order. This ordering is preserved by _expand_schema_for_dynamic, parse_class_inputs, and build_nested_inputs, so consumers should iterate the dictionary directly when processing dynamic slots.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-08-11T17:33:31.657Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 15501
File: comfy_api_nodes/nodes_ltxv.py:213-217
Timestamp: 2026-08-11T17:33:31.657Z
Learning: When reviewing ComfyUI nodes that use IO.DynamicCombo, account for schema expansion by comfy_api/latest/_io.py::DynamicCombo._expand_schema_for_dynamic. Prompt validation in execution.py validates each resulting IO.Combo value against extra_info["options"] and rejects invalid values with value_not_in_list before execute() runs. Review validation logic against only the reachable option domain for closed IO.Combo.Input lists inside a DynamicCombo, unless the node provides another input path that bypasses prompt validation.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-08-13T17:36:37.574Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 15579
File: comfy_api_nodes/nodes_bytedance.py:2115-2118
Timestamp: 2026-08-13T17:36:37.574Z
Learning: In ComfyUI API node implementations, treat saved `widgets_values` as positional. When renaming or changing the type of a widget input, do not rely on backend `execute()` to migrate legacy values, because prompt validation may reject the value before execution. Implement compatibility handling in the frontend or workflow/template migration layer so legacy workflows are converted before backend validation.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-08-14T20:00:13.296Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 15612
File: comfy_api_nodes/nodes_fishaudio.py:297-297
Timestamp: 2026-08-14T20:00:13.296Z
Learning: In partner nodes under comfy_api_nodes, do not flag direct calls from async def execute to shared audio/video conversion helpers such as audio_bytes_to_audio_input, audio_ndarray_to_bytesio, or audio_tensor_to_contiguous_ndarray as individual regressions. If event-loop offloading is needed, implement it centrally in the shared helpers under comfy_api_nodes/util as a dedicated refactor, preserving clean call sites across partner nodes.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

📚 Learning: 2026-08-12T15:35:37.339Z

Learnt from: bigcat88
Repo: Comfy-Org/ComfyUI PR: 15471
File: comfy_api_nodes/nodes_minimax.py:1084-1113
Timestamp: 2026-08-12T15:35:37.339Z
Learning: In Python partner API nodes under comfy_api_nodes/, keep each node’s execute body self-contained, including input validation and the submit → poll → status-check → download flow. Do not extract duplicated validation into shared helpers when limits are endpoint-specific or model-version-specific, because vendor constraints may diverge; preserve per-node readability, independent editability, and a limited blast radius.

Applied to files:

• comfy_api_nodes/nodes_bytedance.py

🔇 Additional comments (3)

comfy_api_nodes/nodes_bytedance.py (3)

120-120: LGTM!

---

2072-2072: LGTM!

---

2243-2251: LGTM!

---

📝 Walkthrough

Walkthrough

The Seedance 2.0 tooltip now describes maximum quality and 4K without mentioning 1080p. Seedance 2.5 now supports 1080p in addition to 480p and 720p. Seedance 2.5 pricing now includes separate 1080p per-frame rates for requests with and without reference video. Existing 480p and 720p pricing remains distinct.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the main change: adding 1080p resolution support to Seedance 2.5.
Description check	✅ Passed	The description covers the API node scope, pricing updates, billing tests, and QA for the changeset.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}