Comfy co-founder Yoland Yan said on October 29, 2026, that Higgsfield had sent a cease-and-desist letter demanding the removal of Comfy’s Open Source Higgsfield challenge within 48 hours. According to Yan, the objections concerned the use of Higgsfield’s name and its CEO’s likeness, which allegedly made the contest appear associated with the AI-video company.
Yan said the challenge would remain online. Comfy’s published contest page listed an October 30 submission deadline and a November 6 winner announcement, placing the public allegation immediately before the competition’s scheduled close.
The underlying demand remains unconfirmed. The original X post was not directly retrievable during research, and the attached letter has not been independently authenticated. RuntimeWire’s report traces the allegation to Yan’s account; it provides no independent confirmation from Higgsfield. No Higgsfield response or legal ruling appears in the reviewed sources.
What Comfy Says Higgsfield Demanded
Yan’s October 29 post described a letter received the previous night and said Higgsfield wanted the challenge taken down within 48 hours. Yan characterized the dispute as involving three connected issues: Higgsfield’s name, its CEO’s likeness, and the impression that Higgsfield was involved in the event.
Comfy’s response, as presented by Yan, is that the competition clearly identifies ComfyUI as its organizer and disclaims affiliation with or endorsement by Higgsfield. Yan also accused Higgsfield of failing to follow through on a promise to open-source its product. That accusation is Comfy’s stated rationale for the contest, not an independently established finding about Higgsfield’s commitments.
Yan’s position on the takedown demand was explicit: “The challenge stays up.”
The distinction between the post and the letter matters. The available account explains how Comfy describes the objections, but it does not provide an independently verified basis for assessing the letter’s complete wording, scope or legal reasoning. Any description of Higgsfield’s demands therefore needs to remain attributed to Yan.
What the Contest Actually Asks Builders to Do
Comfy’s official challenge page presents the event as a two-week effort to recreate popular applications using ComfyUI. Its opening pitch directly names the commercial company: “Higgsfield said they’d open source their platform. Let’s help.”
The page asks participants to start with a recognizable output, such as a performance effect, cinematic camera move or music-video transformation, then build a working app that lets someone else create their own version. Examples include changing a video’s camera angle and swapping a character.
That describes an effort to reproduce user-facing capabilities. The published requirements do not establish that entrants obtained Higgsfield’s source code, model weights or internal implementation. Calling the contest reverse-engineering should therefore be understood carefully: recreating an observed result is different from demonstrating access to the system that originally produced it.
The contest’s published structure also shows that this is a prize-backed development event, with specific deliverables and dates:
| Contest detail | Published terms |
|---|---|
| Registration opened | October 15 |
| Submission deadline | October 30, at 9 a.m. PT |
| Winners announced | November 6 |
| Best Overall prize | $10,000 |
| Other main prizes | GeForce RTX 5090 awards for Most Innovative, Most Viral and Open Weights Only |
| Runner-up prizes | Ten awards of $250 in Comfy Credits |
| Code requirement | Publish app code with an open-source license and setup instructions |
| Model restrictions | Partner models are allowed generally; Open Weights Only excludes partner nodes and closed-source APIs |
These details make the timing consequential. Yan’s allegation surfaced the day before submissions were due, when builders would plausibly be preparing repositories, demonstrations and setup documentation. A demand to remove the whole event could affect its submission and discovery infrastructure, even though it would not automatically determine the status of every participant’s code.
The precise overlap remains unclear because the letter’s delivery time has not been verified. The alleged 48-hour window should not be converted into a definite expiration time from the post’s publication alone.
The Trademark Dispute Is About Presentation
The branding argument described by Yan concerns whether people could mistake the challenge for an event associated with Higgsfield. That is a different question from whether a ComfyUI workflow can produce a similar video effect.
Three elements deserve separate attention:
- The Higgsfield name: It identifies the product being challenged, while also serving as the contest’s most prominent reference point.
- The CEO’s likeness: Yan says this was another objection. The available evidence does not establish exactly how the likeness appeared or the legal basis asserted against its use.
- Perceived affiliation: Comfy says it made its independence clear. That is its answer to the alleged concern that Higgsfield was associated with the competition.
The contest page supports one part of Comfy’s explanation: its opening pitch is plainly critical of Higgsfield’s alleged failure to release its platform. At the same time, the company’s name is central to the event’s identity. Those two features can coexist. Critical intent and the way a promotion appears to viewers are separate considerations.
My view is that the most useful distinction here is between the technical target and the promotional packaging. A builder’s decision to recreate a camera effect presents different practical questions from an organizer’s decision to use a company’s name or an executive’s image to market a contest. Treating everything as one dispute over open source obscures the specific objections Yan says the letter raised.
Comfy’s claimed disclaimer is relevant to understanding its position, but the reviewed evidence cannot settle whether the overall presentation created confusion. Nor can it establish whether the alleged likeness claim has merit.
“Open Source” Does Not Mean Every Model Is Open
The contest rules contain another consequential distinction: publishing an application’s code does not necessarily make its entire AI stack open.
Comfy requires entrants to publish their app code under an open-source license and supply setup instructions. However, the rules allow partner models for the broader competition. Only the Open Weights Only category expressly excludes partner nodes and closed-source APIs, according to the contest page.
An openly licensed workflow can therefore still depend on a commercial service to generate its output. Readers may be able to inspect and modify the application while remaining dependent on an external provider for inference, account access or credits.
Frequently Asked Questions
4 questions
1Has Higgsfield confirmed sending the letter?
No public confirmation or response appears in the reviewed sources. The allegation comes from Comfy co-founder Yoland Yan.
