Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
A powerful tool that translates ComfyUI workflows into executable Python code.
| Date | Stars |
|---|---|
| 2026-07-24 | 2365 |
| 2026-07-25 | 2365 |
| 2026-07-28 | 2365 |
| 2026-07-30 | 2365 |
| 2026-08-06 | 2365 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# ComfyUI-to-Python-Extension  Build a workflow in ComfyUI, then walk away with runnable Python. `ComfyUI-to-Python-Extension` turns visual workflows into executable scripts so you can move from node graphs to automation, experiments, and repeatable generation without rebuilding everything by hand. This project supports: - exporting from the ComfyUI UI with `Save As Script` - converting saved API-format workflows with the CLI ## Install Choose the setup that matches how you want to use the project. This project supports Python 3.12 and newer. ### Web UI extension (`File -> Save As Script`) For ComfyUI to recognize this project as an extension, the repo must be discoverable through ComfyUI's `custom_nodes` search paths. Clone directly into `ComfyUI/custom_nodes`: ```bash cd /path/to/ComfyUI/custom_nodes git clone https://github.com/pydn/ComfyUI-to-Python-Extension.git ``` Or keep the repo elsewhere, then either: - symlink it into `ComfyUI/custom_nodes` - add its parent directory to ComfyUI's `custom_nodes` search paths via `extra_model_paths.yaml` Example symlink setup: ```bash git clone https://github.com/pydn/ComfyUI-to-Python-Extension.git cd /path/to/ComfyUI/custom_nodes ln -s /path/to/ComfyUI-to-Python-Extension ComfyUI-to-Python-Extension ``` Then install this extension into the same Python environment that launches ComfyUI. The `pyproject.toml` file declares the package dependencies, but those dependencies still need to be installed into ComfyUI's runtime Python. If you run ComfyUI from a source checkout with `uv`: ```bash cd /path/to/ComfyUI uv pip install -e ./custom_nodes/ComfyUI-to-Python-Extension uv run python main.py ``` If you use the Windows portable build: ``` cd C:\path\to\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-to-Python-Extension ..\..\..\python_embeded\python.exe -m pip install -e . ``` Running `uv sync` inside `ComfyUI-to-Python-Extension` creates this extension's own `.venv`. ComfyUI does not automatically import dependencies from that `.venv`; it imports custom nodes with the Python interpreter used to launch ComfyUI. After installation, restart ComfyUI. ### CLI exporter / generated scripts You can keep the repo anywhere for CLI usage and generated-script execution. ```bash git clone https://github.com/pydn/ComfyUI-to-Python-Extension.git cd ComfyUI-to-Python-Extension uv sync export COMFYUI_PATH=/path/to/ComfyUI ``` `COMFYUI_PATH` helps the exporter and generated scripts find the ComfyUI codebase. It does not, by itself, register this repo as a ComfyUI extension for the Web UI. It also does not install ComfyUI runtime dependencies such as `torch` into the current Python environment. `COMFYUI_PATH` is checked first. If it is not set, the exporter falls back to searching parent directories for a folder named `ComfyUI`. If the CLI fails with `ModuleNotFoundError: No module named 'torch'`, run the command with the same Python environment that launches ComfyUI, or install ComfyUI's runtime dependencies into the environment you are using for the CLI. For Windows portable builds, run the CLI with ComfyUI's embedded Python from the extension directory: ``` ..\..\..\python_embeded\python.exe -m comfyui_to_python --input_file ".\workflow_api.json" --output_file ".\workflow_api.py" ``` ## Web UI Export In current ComfyUI builds, `Save As Script` is typically available under: `File -> Save As Script` The command downloads a generated `.py` file. The current UI export uses the default filename `workflow_api.py` so it works in ComfyUI Desktop without relying on `prompt()`.  Notes: - menu placement can differ between frontend versions - the Web UI export uses a fixed default filename rather than asking for one interactively ## CLI Export 1. In ComfyUI, enable dev mode options if needed. 2. Save the workflow in API format: `File -> Export (API)`. 3. Run the exporter: ```bash uv run
Excerpt of 7,402 characters
Read on GitHub
94
26
3
haohaocreates · @Comfy-Org
3
3
Comfy Org PR Bot
2
1
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:1be07bcc5b69a26e, topic:stable-diffusion, topic:image-generation, topic:generative-art