sensevoice-onnx requires setuptools<=65.0 in ComfyUI

If you searched for sensevoice-onnx setuptools conflict comfyui or pip check shows sensevoice-onnx requires setuptools<=65.0, treat it as a workflow-specific dependency conflict, not a reason to downgrade every package in your ComfyUI environment.

In practice, this usually means one custom node or audio workflow expects an older packaging stack than the rest of your current install.

What the conflict looks like

The high-signal line usually appears in pip check:

sensevoice-onnx requires setuptools<=65.0, but you have setuptools 7x.x

The exact installed version may differ, but the pattern is the same: sensevoice-onnx wants an older setuptools than the rest of the environment currently has.

What it usually means

This is not automatically a startup blocker for all of ComfyUI.

It usually means one of these:

First decision: do you need this workflow?

Before changing packages, answer this:

• Are you actively using a SenseVoice-ONNX custom node or audio workflow?
• Did the environment break right after installing or updating that stack?
• Is this line only visible in pip check, while ComfyUI itself still works?

If the answer is "I am not using it right now", the safest move is often to leave the warning alone until that workflow matters.

Use the Python that actually starts ComfyUI

For the official Windows portable package, run commands from the portable root:

.\python_embeded\python.exe -s -m pip show sensevoice-onnx setuptools
.\python_embeded\python.exe -s -m pip check

For a manual Git install, activate the venv first:

python -m pip show sensevoice-onnx setuptools
python -m pip check

If pip show points to a different Python than the one that launches ComfyUI, fix that first. Otherwise you will repair the wrong environment.

Safe repair order

Use this order to avoid widening the damage:

1. Confirm whether the workflow is actually needed.
2. Record the current pip check output.
3. Check whether ComfyUI core and unrelated workflows still start.
4. Repair the narrow SenseVoice-ONNX path only if it is a real blocker.
5. Re-run pip check and re-test the target workflow.

When not to downgrade globally

Do not downgrade setuptools across the whole environment just because one line in pip check asks for it, unless all three are true:

• the SenseVoice-ONNX workflow is important right now
• that workflow is actually failing
• you have confirmed the rest of the environment will tolerate the downgrade

If your main problem is broader package drift after plugin installs, use ComfyUI Dependency Conflicts. If the visible failure is a custom node import traceback, use ComfyUI Plugin Import Failed.

Practical takeaway

The key idea is simple:

• pip check is a clue, not an automatic command
• sensevoice-onnx requires setuptools<=65.0 is usually a narrow workflow conflict
• preserving a stable ComfyUI environment is usually more valuable than satisfying one stale package pin immediately