A Hugging Face bemutatta a Workflow1111 projektet, amely a népszerű AUTOMATIC1111 képgeneráló felület szinte összes funkcióját egyetlen Gradio-alapú vizuális munkafolyamatba sűríti. A rendszer 11 különböző média-pipeline-t és 73 csomópontot tartalmaz, amelyek lefedik a szövegből történő képalkotást, a felskálázást, a háttéreltávolítást és a videógenerálást is.
A munkafolyamat különlegessége, hogy a különböző feladatokat, például a promptok finomítását vagy a képelemzést különálló nyelvi modellek végzik a háttérben. A felhasználók a saját Hugging Face-fiókjuk segítségével közvetlenül a felhőben is futtathatják a rendszert, de a kód saját gépre vagy helyi grafikus kártyára is letölthető.
Minden egyes kimeneti pont automatikusan egy-egy REST API-végponttá és MCP-eszközzé válik. Ez azt jelenti, hogy a generált munkafolyamatokat AI-asszisztensek és fejlesztői ügynökök is közvetlenül tudják vezérelni és használni.
Az eredeti szöveg (Hugging Face)
What's on the canvas Text-to-image Hi-resolution fix Image-to-image Let an LLM write the prompt Read an image back into a prompt Detection to inpaint mask Prompt matrix Upscale and background removal Annotators PNG Info Image-to-video Running models on your own GPU Every output is an API Where this sits next to ComfyUI Build your own In our last post, we built five small gr.Workflow graphs and hinted at what it would take to build something as complex as AUTOMATIC1111's stable-diffusion-webui. In this post we walk you through Workflow1111, where we have rebuilt most of AUTOMATIC1111's feature set as a single workflow canvas.
Workflow1111 is a graph of eleven media pipelines built using seventy-three nodes. It brings together SOTA models for text-to-image, hi-resolution fix, image-to-image, prompt-matrix grids, VLM interrogate, detection-to-inpaint masks, ControlNet-style annotators, background removal, PNG Info storing, and image-to-video.
You can run any of these pipelines by signing in with your Hugging Face account or providing an access token. Once you sign in, the model calls use your own quota.
👉 Try Workflow1111, or duplicate the Space and start rewiring it for your own use case.
All the media pipelines are built from the same four operator kinds covered in our last post and the official guide. Each node on the canvas wraps one operator, and the operator's inputs and outputs become the ports you connect edges to. As a quick reference on our four operator kinds: fn is a Python function, model is a model called through InferenceClient, space is another Gradio Space, and dataset is a row from a Hub dataset.
Let's go through the pipelines one by one.
This is the core pipeline. It has the controls you'd expect from A1111's txt2img tab: negative prompt, steps, CFG, seed, width and height, plus a model_id field for choosing the checkpoint. The prompt goes through a prompt-builder fn node first, which appends the selected style preset and cleans up the text, then into a model node that calls the checkpoint through Inference Providers. A post-process fn node writes the generation parameters into the PNG's metadata on the way out, which is what the PNG Info pipeline reads back later.
In Automatic1111, hi-resolution fix first upscales the txt2img output and then runs a second denoising pass. Here it's a two-node detour instead. The text-to-image result goes into a FLUX.1-Kontext model node with a refine instruction ("enhance fine detail and micro-texture, keep the composition identical") and comes back sharper and larger.
That same Kontext node doubles as the image-to-image tab. Upload an image, describe the change you want, and it returns the edited image.
Start with a rough prompt like "A lighthouse in a storm." This pipeline sends it to a Qwen3-4B model node, and a small fn node turns the reply into a clean list of tags, capped at forty: "stormy sea, wet rocks, dramatic composition, low angle shot, volumetric lighting, ominous tone." You can connect any diffusion model node to this output to render the image.
There's no custom node involved, unlike in ComfyUI. In a Gradio workflow the LLM and the diffusion model are both ordinary model operators on the same canvas.
This is like AUTOMATIC1111's Interrogate button, with a VLM doing the interrogating instead of CLIP. Qwen2.5-VL looks at a night-market photo and writes a prompt that could have produced it. A ViT classifier node reads the same image and returns labels: restaurant 51.9%, tobacco shop 15.6%, toyshop 9.1%.
Both nodes use the same image input, so gr.Workflow runs them in parallel and you get both answers in roughly the time it takes to run one.
AUTOMATIC1111 makes you paint an inpaint mask by hand. This pipeline generates one from a detector instead. DETR finds six objects in a street photo (three people, a dog, a bicycle, and a car), and from there the workflow splits into two branches: one draws the detected boxes on the original image, the other turns th