Topic

Gradio

1 post about Gradio. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Hugging Face
Rebuilding AUTOMATIC1111 with Gradio Workflow
Workflow1111 rebuilds most of AUTOMATIC1111’s stable-diffusion-webui feature set as a single Gradio Workflow canvas. It combines eleven media pipelines and 73 nodes for text-to-image, refinement, image-to-image, prompting, interrogation, detection masks, annotators, upscaling, background removal, PNG metadata, and image-to-video. The implementation uses four operator kinds—Python fn functions, model calls through InferenceClient, Space calls, and Hub dataset rows—with parallel branches for independent work; 32 of 36 operator nodes are fn nodes, and 22 run in-process without network calls. Models can run through Inference Providers, Spaces, or a local GPU, while output nodes automatically become REST endpoints and MCP tools. The result is a browser-accessible, OAuth-enabled workflow that can also be duplicated, rewired, deployed, and called from code.

The best engineering reads, once a week.

Topic

1 post about Gradio. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Hugging Face
Rebuilding AUTOMATIC1111 with Gradio Workflow
Workflow1111 rebuilds most of AUTOMATIC1111’s stable-diffusion-webui feature set as a single Gradio Workflow canvas. It combines eleven media pipelines and 73 nodes for text-to-image, refinement, image-to-image, prompting, interrogation, detection masks, annotators, upscaling, background removal, PNG metadata, and image-to-video. The implementation uses four operator kinds—Python fn functions, model calls through InferenceClient, Space calls, and Hub dataset rows—with parallel branches for independent work; 32 of 36 operator nodes are fn nodes, and 22 run in-process without network calls. Models can run through Inference Providers, Spaces, or a local GPU, while output nodes automatically become REST endpoints and MCP tools. The result is a browser-accessible, OAuth-enabled workflow that can also be duplicated, rewired, deployed, and called from code.

The best engineering reads, once a week.