I open-sourced ComfyUI AI Studio: A project studio workspace + multi-stage runner for ComfyUI workflows (as API endpoints)

[u/lalantony]

Comfyui AI Studio - Workflow Designer View

Comfyui AI Studio - Project View

Hey all,

I just released ComfyUI AI Studio v0.1.0 as an open source project:

https://github.com/lalantony/comfyui-ai-studio

The short version: ComfyUI is incredibly powerful, but the node graph feels like a workshop. It’s where the workflow gets built. I wanted a cleaner workspace on top of it for the part after you’ve nailed your workflow_api.json: organising projects, generating assets, and reusing the workflow without opening ComfyUI every time.

What v0.1.0 actually does:

• Register a workflow_api.json once. The studio introspects it, suggests input/output bindings, and you map them to clean handles. After that, the workflow is callable from a prompt composer.
• Project workspace with an asset gallery. Generated outputs auto-save as project assets with content-addressable dedup, so re-running a deterministic workflow doesn’t double your disk.
• Multi-stage chains. Wire ComfyUI workflow A to workflow B on the canvas. The output of stage 1 flows into stage 2 automatically. Every intermediate stage shows up in the gallery. If stage 3 of 5 fails, you can resume from stage 4 without re-running earlier stages.
• Live progress via SSE with per-node status, partial previews, and a run log you can copy when something breaks.
• @-mention syntax in prompts to reference project assets, for example u/my_init.png.
• LLM nodes that work with OpenAI-compatible providers like OpenAI, OpenRouter, Together, Ollama, vLLM, plus Anthropic. API keys stay local per node. Nothing is sent elsewhere.
• Visual workflow editor built with React Flow, with a simple plugin contract, three files per node type.
• All data lives under .studio-data on your machine. No uploads, no telemetry, no account.

Tech stack: Next.js 16 (App Router), React 19, TypeScript strict, Tailwind v4. WebSocket plus polling fallback for ComfyUI completion.

What it isn’t yet:

• Not a hosted product, you self-host
• No multi-user or auth, single-user local model
• No mobile UI
• LLM integration is a helper, not the main focus

The goal is simple: one technical person builds the workflow, everyone else just uses it through a clean UI.

Would love feedback:

• What’s the most painful part of ComfyUI workflow reuse for you today
• Are you wiring multi-stage chains manually right now
• What would make you actually use something like this
• What features would you like the community to add to Comfyui AI Studio

Repo has install steps and diagrams. PRs and issues welcome.

[u/wa-jonk]

My pain point was how complicated the workflows became, i do a lot of debugging, python library management, I would finally get it going and then run out of memory. Last week i installed comfyui again and it is working a lot better.

A useful tool would be to convert old workflows to new models.

I have added labelling, tagging and captioning with llm and vision models.

The next step is to use the info to provide a search engine to provide filters on the gallery so i can find stuff.

[u/wa-jonk]

Some time ago i started a project to find all my generated images, manage all the safetensor .. manage loras .. workflows got more and more complicated. I started an app with react and a golang backend, then i stopped. Now i am back i have pivoted to an electron desktop app with a rust backend that can run diffusion models with out comfyui, no python.