Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
Publishing the three.ws nodes to the Comfy Registry
The node pack in three_ws_nodes/ is ready to publish. Its
metadata follows the Registry specification
and the publishing guide. Once it
is on the Registry, ComfyUI Manager lists it automatically.
| Field | Value |
|---|---|
Node id ([project] name, immutable) |
comfyui-three-ws |
Publisher id ([tool.comfy] PublisherId, immutable) |
threews |
| Display name | three.ws Forge |
| Version | 1.0.0 |
| License | Apache-2.0 (three_ws_nodes/LICENSE) |
| Icon | https://three.ws/apple-touch-icon.png (180x180 PNG) |
Both ids were confirmed unclaimed on 2026-09-17
(https://api.comfy.org/nodes/comfyui-three-ws and
https://api.comfy.org/publishers/threews returned 404).
What was already validated
comfy node validate(comfy-cli, run fromthree_ws_nodes/) passes: the config parses and the ruff security rules (S102, S307, E702) report nothing.- The package imports as a plain Python package and exposes
NODE_CLASS_MAPPINGS/NODE_DISPLAY_NAME_MAPPINGSwith both nodes. - The node smoke test (
python -m unittest test_nodes) and the shared client suite pass against an in-process stub of the Forge contract.
Owner steps
These need a human account, so they are the only steps left.
Create the publisher. Sign in at https://registry.comfy.org (GitHub or Google login) and create a publisher with the id
threewsexactly. The id is permanent and must matchPublisherIdinpyproject.toml. Ifthreewsis taken by the time you register, pick another id and changePublisherIdto match before publishing.Create an API key. On the publisher page, open API Keys, create a Registry Publishing key, and store it in the password manager. It is shown once.
Install comfy-cli somewhere outside the repo, for example
pipx install comfy-cli && pipx inject comfy-cli ruff(ruff is whatcomfy node validateshells out to).Publish from the node folder on a clean checkout of
main:cd integrations/comfyui/three_ws_nodes comfy node validate comfy node publish --changelog "First release: Text to 3D and Image to 3D nodes backed by three.ws Forge"Paste the API key when prompted (right-click paste on Windows; Ctrl+V can append a stray control character). comfy-cli zips only git-tracked files in this folder, minus
.comfyignore, so commit everything first. The command leaves anode.zipbehind; delete it, it must never be committed.
Post-publish verification
curl -s https://api.comfy.org/nodes/comfyui-three-wsreturns JSON with"id":"comfyui-three-ws"andlatest_version.versionof1.0.0.- https://registry.comfy.org/nodes/comfyui-three-ws renders the page with the three.ws icon, description, and repository link.
- Wait for the Registry's automated scan to mark the version active (it shows a status badge on the page; a flagged version does not appear in Manager).
- In a fresh ComfyUI: Manager > Custom Nodes Manager, search
three.ws, install, restart. Confirm the three.ws category holds both nodes. - Queue three.ws Text→3D with the default prompt on the
imagepipeline. It must finish with statusdoneand a.glbpath in ComfyUI's output directory. That completed generation is the success evidence recorded inmarketing/growth/opportunities.csv; update that row tolivewith the Registry URL.
Releasing updates
Bump version in pyproject.toml (semantic versioning; the Registry rejects a
version it already has), commit, and rerun comfy node publish from the same
folder.