comfyui-running

What to consider before installing: - Functionality: This skill automates a local ComfyUI instance and a local browser (CDP). It will scan local drives to find ComfyUI, start ComfyUI if needed, and control a browser tab via the Chrome/Edge debugging port. - Config: You must supply a correct comfyui_root (in config.json or via env vars) or let the skill autodetect. Double-check the skill's config.json before running. - Env mismatch: The registry metadata claims no required env vars, but the code expects COMFYUI_ROOT, CDP_PORT, COMFYUI_PORT, etc. Treat the config.json as required. - Side effects: comfyui_browser.py removes proxy-related environment variables at import time (this affects only the running process but may change networking behavior). If you rely on proxy env vars for other tools, be cautious. - Local-only network: The code talks to 127.0.0.1 endpoints and the browser's debugging websocket; there is no obvious remote exfiltration endpoint in the code/docs, but you should still review the code yourself if you are worried about privacy. - Best practices: Run the skill in a controlled environment (e.g., a dedicated VM or container) if you are uncertain. Inspect config.json and the Python files (comfyui_browser.py, lib/comfyui_*.py) yourself. Ensure no sensitive data resides in the directories the skill will scan or that could be picked up by its filesystem checks. If you want, I can point out the exact lines that remove proxy vars, where env vars are read, and where subprocesses and websocket connections are created so you can review them more easily.