News · 2026-10-02
Comfy launches an agent that builds and repairs visual workflows
Comfy launched Comfy Agent on October 1 to find resources, build and edit visual workflows, fix errors, and run workflows inside Comfy Cloud. The agent makes the canvas an action surface for conversational assistance, while its documented local mode still sends agent requests through Comfy’s online service.
Key facts
- Comfy announced the product October 1, 2026.
- The interface supports up to five parallel chats.
- Cloud access ships first; Desktop was promised in a few weeks and remains forthcoming in the reviewed documentation.
- Primary sources are Comfy’s launch post and agent documentation.
A visual generation workflow is more than a prompt. It can involve models, processing nodes, templates, settings, and connections between components. That gives experienced users control, while making setup and troubleshooting harder for someone who knows the desired image or video but not the exact graph needed to produce it.
Comfy’s product moves assistance into that graph. The company says the agent can search for models, nodes, templates, and assets; create or change workflows; inspect errors; and execute work. Users can continue editing the canvas and inspect node parameters. Those are stated product capabilities, rather than an independent estimate of how often the agent successfully completes a task.
Imagine an assistant beside a mixing desk. Instead of offering verbal advice about which knobs to turn, the assistant can connect components and adjust the setup, while the operator can see the controls. That visibility matters: a generated workflow is an artifact a user can inspect and refine, rather than just a conversational recommendation.
The graph also provides feedback. A broken node or failed run can give the agent a concrete error to work from. That is the same broad tool-use loop appearing in coding and engineering products: propose a change, execute it, inspect the result, and revise. Comfy’s announcement does not show a standardized success-rate evaluation across representative workflows.
Launch and documentation status need careful separation. The October 1 post presents the product as beta and says it is available to everyone in Comfy Cloud. It promises Desktop support “in a few weeks.” Current documentation calls the Cloud version generally available while still listing Desktop as coming soon. The evidence confirms the Cloud product and a stated future commitment, rather than a firm Desktop release date.
Costs follow the existing credit system. Comfy says the agent is free to try, then draws from Comfy Credits, the same pool used for generations. Its documentation lists token charges, including a named model rate. That establishes billing information, but the dossier does not support expanding it into a complete statement about every underlying provider, future model selection, or local-language-model roadmap.
The data and privacy documentation is particularly important for anyone attracted by local creative software. Cloud workflows run on Cloud graphics processors. For local use, chat history and workflow files stay on the machine and local nodes run on local hardware, but the agent’s messages and relevant workflow information are processed online.
Storage location, execution location, and reasoning location are therefore different questions. Keeping a workflow file on a laptop does not establish that its contents never enter a remote request. Conversely, using online agent assistance does not mean every generation runs remotely. The documented distinction gives users something concrete to assess instead of relying on the word local as an all-purpose privacy guarantee.
Permissions have another split. The docs describe approval and automatic modes for running workflows, but the agent can edit in either mode. A run approval is not a blanket promise that every proposed canvas modification receives the same checkpoint. That makes inspecting the resulting graph part of a meaningful user workflow, especially when an edit changes resource use or processing behavior.
Early reception is too small to generalize. The launch features selected preview creators, and its post showed only a small number of reactions and comments during the dossier check. A supplied StableDiffusion feed confirms a discussion appeared, without enough comment evidence to characterize sentiment. The strongest unresolved question is routine reliability on complicated graphs, rather than whether an attractive demonstration can be produced.
Comfy Agent is nevertheless a shipping tool, not merely research code. It joins a broader move from assistants that describe work to agents that manipulate the application’s native objects. Our lesson on agent harnesses explains why the canvas, errors, tool interface, and execution controls can matter as much as the model underneath. The useful next evidence is independently measured workflow completion, clear Desktop availability, and transparent data flow under real use.
Key questions
Where is Comfy Agent available now?
Does a local Comfy workflow mean the agent is offline?
Can Comfy Agent edit a workflow without approval?
Cite this
APA
Ground Truth. (2026, October 2). Comfy launches an agent that builds and repairs visual workflows. Ground Truth. https://groundtruth.day/news/comfy-agent-cloud-workflow-builder.html
BibTeX
@misc{groundtruth:comfy-agent-cloud-workflow-builder,
title = {Comfy launches an agent that builds and repairs visual workflows},
author = {{Ground Truth}},
year = {2026},
month = {oct},
url = {https://groundtruth.day/news/comfy-agent-cloud-workflow-builder.html}
}
Comments are replies to this story on Bluesky — reply with any Bluesky account to join in.