ComfyUI ↔ Flame integration — is there an official Autodesk roadmap, or is this still DIY territory?

I’m using ComfyUI more and more in production, but as commercial work scales up, traceability becomes a real issue — I need generation settings, workflows, and node graphs tied to the actual Flame project, not floating around in a separate ComfyUI folder that it is hard to remember to archive.

I’ve seen several people building their own bridges (some using MCP), which is great, but honestly it’s a steep climb for those of us who aren’t deep into the tech side. What I’d love is something closer to what Nuke has done — ComfyUI settings embedded directly in the project/script file itself, with clean round-tripping between the two apps.

Performance-wise I think Flame could genuinely beat Nuke here. So my question is: does anyone know if Autodesk has an official plan for native ComfyUI integration in Flame, or is this destined to stay a community DIY effort indefinitely? Would love to hear from anyone closer to the roadmap, or from others solving this in production right now — what’s your setup?

I doubt there is a roadmap. There are no other integrations with other apps, so why would they create one with this?

One option - the OpenClip nodes I created for ComfyUI - the write node has a ‘publish’ toggle, ‘off’ by default. But if you enable it, it will store the current ComfyWorkflow as a json file along with the version of the OpenClip.

Inspired by the Flame publish workflows.

That would document the exact state of all nodes, prompts, etc. As part of that it would also document the versions of models you’ve been using.

One additional thought.

There’s a new course on Griptape (the Nuke platform for GenAI). It’s on fxphd, but in the marketplace, not part of the subscription. There’s a discount, but you have to ask for it. They didn’t include it in the email.

The first episode is a good comparison between ComfUI and Griptape and where they sit. They both have benefits, and you should know both (if you also work in Nuke).

But where it’s relevant to this discussion, is that Griptape is an effort to have tight integration with studio pipelines, including different licensing and runtimes that are not was flexible as ComfyUI but better suited to answer some of the questions you have.

Now, would ADSK acquire a Griptape like company to integrate with Flame? I wouldn’t totally rule it out, since it would also apply to other apps in ADSK’s portfolio. Unlikely to do it for just Flame, market is too small. Only time will tell.

One could argue that Autodesk already did that when they bought Wonder Dynamics, now called Autodesk Flow Studio. Very different tool to Comfy UI or Griptape but way more practical for Autodesk’s main M&E market, CGI.

I believe it utilises USD though, which Flame does not yet support (to my knowledge) so it’s not like you could utilise the camera tracking or clean plate generation tools I believe Autodesk Flow Studio has.