Skip to main content
A custom node package in Cyberun Cloud is a versioned bundle that extends the runtime on your agents — typically a ComfyUI custom-node set. Packages are distributed to eligible agents so workflows that reference them can run. If custom nodes aren’t enabled on this deployment, the Custom Nodes entry won’t appear in the sidebar.

​
What a node record holds

  • Display name — the human-readable label shown in lists. Up to 255 characters.
  • Package name — the directory name under custom_nodes/ on the agent. Unique per team, up to 100 characters, restricted to alphanumerics plus -, _, .. Immutable once created.
  • Version — a free-form version string (1.0.0, 2024-05, anything), up to 50 characters.
  • File — the package archive. You upload it once; it registers and appears in the list.
  • Size — the archive’s file size.
  • Pip requirements — optional extra Python dependencies, one package per line. The agent already auto-installs the package’s own requirements.txt; this field is for additions only (e.g. opencv-python>=4.8).
  • Status — active (the agent includes it in its sync set) or disabled (kept in the catalog, excluded from sync).

​
How packages reach agents

Same pattern as custom models: an agent whose labels match a workflow’s requirements pulls the package on first need, caches it locally, and reuses it after that.

​
Updating a package

The metadata you can edit is display name, version, pip requirements, and status. You can also reupload the archive — the package name stays the same, but the file contents update. A reupload changes what new dispatches see. Tasks already running on an agent finish with the version they started with.