Is it possible to use comfy-cli to install a node with specific version

[doombeaker]

Thank you for the greate tool comfy-cli.

Describe the solution you'd like I want to install node with a specific versoin, like

comfy node registry-install comfyui-kjnodes==1.0.5

Is it possible yet?

[snomiao]

Research Findings: Version-specific Node Installation

Thank you for the feature request! I've researched the codebase to determine if installing a node with a specific version is currently possible.

Current Status

Yes, this feature is already partially implemented! The registry-install command supports version-specific installation, but it's currently marked as hidden in the CLI.

How It Works

The command signature (from comfy_cli/command/custom_nodes/command.py:873-889):

@app.command(
    "registry-install",
    help="Install a node from the registry",
    hidden=True,  # <-- Currently hidden from users
)
@tracking.track_command("node")
def registry_install(
    node_id: str,
    version: Optional[str] = None,  # <-- Version parameter exists!
    force_download: bool = False,
):

Implementation Details

1. API Support: The RegistryAPI.install_node() method (comfy_cli/registry/api.py:103-125) already accepts a version parameter:

   • If version is None → fetches latest version
   • If version is provided → fetches that specific version via /nodes/{node_id}/install?version={version}

2. Backend: The registry API endpoint supports version queries and returns the appropriate NodeVersion with download URL.

3. Installation Flow: Downloads the versioned zip file, extracts it, runs requirements.txt and install.py scripts.

To Use Right Now

While the command is hidden, you can still use it:

comfy node registry-install comfyui-kjnodes --version 1.0.5

Or without a version (gets latest):

comfy node registry-install comfyui-kjnodes

Recommendation

The feature exists and appears functional based on the code. The command is marked as hidden=True, which suggests it might be:

1. Still in testing/experimental phase
2. Waiting for full registry rollout
3. Being evaluated for UX/stability

Next Steps: The maintainers could consider un-hiding this command if the registry backend is stable and ready for production use. The implementation looks complete and follows proper patterns with tests in place.

Let me know if you'd like me to test this further or if there are any concerns about making this command publicly available!