Skip to content
MehranMarxian edited this page Sep 1, 2026 · 1 revision

FAQ

Is it really free? What's the catch?

Free, MIT-licensed, no subscription, no credits, no account. The catch is that you supply the compute — it drives a ComfyUI server on your own machine, so you need a GPU and the patience to install some models once.

Do my images get uploaded anywhere?

No. ComfyUI runs on 127.0.0.1 — your own machine. There is no telemetry, no account, and no automatic transmission of images, prompts, model names, or diagnostics. Copy Diagnostics writes a local text report and sends it nowhere; you choose whether to paste it into a bug report.

The plugin asks Photoshop for filesystem and network permission because it needs temporary files and a connection to localhost. That is the whole reason.

Do I need to know ComfyUI?

No, but you need it installed and running. You never have to build a graph — OpenLayer ships its own workflows and picks node IDs for you. If you do know ComfyUI, the editable source graphs are in src/workflows/source/ and you can bring your own.

Why does it use port 8190 instead of 8188?

So it does not fight with another tool already using your ComfyUI. You do not have to move your server — open Settings and click Find ComfyUI Active Port, and it will find one on any port.

Does it work on macOS?

Unverified. The plugin is built on Photoshop UXP, which is cross-platform, and the release package has been correct ZIP-spec since v0.10.0 (earlier ones unpacked wrongly on macOS and gave a blank panel). Nobody has confirmed a working macOS install end to end. If you try it, please report either way.

The panel opens but says it can't connect

Start ComfyUI, then click Check ComfyUI. If it still fails, click Find ComfyUI Active Port. To confirm the server is alive at all:

curl http://127.0.0.1:8190/system_stats

Generate fails and I don't know why

Run Settings → Check Workflow Health. It names the exact model file or ComfyUI node that is missing, and the folder it belongs in. That is almost always the answer.

How much do I actually have to download?

12.5 GB gets you five tools. See Choosing a Model. The ~177 GB figure is what every preset would cost together, and nobody needs that.

Why is the download total in Setup different from what I expected?

Because it counts each file once. Several presets share the same 8 GB text encoder, so a naive per-preset sum roughly doubles the real number. Setup checks what you already have and tells you the remaining total for your machine.

Can I use my own LoRAs?

Yes — eleven presets across Text to Image, Image to Image and Sketch to Image take an optional LoRA. Choosing nothing leaves the shipped workflow untouched. If you pick a LoRA from a different model family it stays selectable but is marked, and generating will succeed with a visibly unchanged image — that is the silent failure the warning is about, not a bug.

Why did Unflatten hand my picture back unchanged?

The subject fills the frame. It needs something standing in front of something else; a close-up has no front and back to find. This is true of photographs and generated images alike — it is about composition, not where the image came from. The panel cannot detect this in advance, which is why it is stated on the screen rather than guessed at in code.

Why doesn't Multi-Reference keep my friend's face?

It composes scenes; it does not cast people. Clothing, props, setting and lighting carry across from a reference — a face comes back as a plausible stranger, even from a clean studio portrait. That was confirmed across 48 test generations before the feature shipped, and nothing in the panel claims otherwise.

Can Claude actually use this?

Yes — all ten generation tools are reachable over the Model Context Protocol, and it is not Claude-specific (Codex CLI, VS Code agent mode, Cursor, Windsurf, Zed, Cline and Continue all speak it). It is off by default, runs entirely on your machine, and the agent can only press buttons the panel already has. See Agent Bridge (MCP).

Is it safe to use on client work?

It is an alpha. Everything runs locally so there is no confidentiality concern, but the output quality and edge cases are still being tested — work on duplicate layers, especially with Inpaint, Outpaint and Unflatten. See what works and what does not.

Creative Cloud says the plugin isn't verified by Adobe

Expected. It is not signed and not distributed through Adobe Exchange, so Creative Cloud shows a trust prompt. Click through it. Also keep the .ccx on the same drive as Photoshop — the installer only searches the drive the file is sitting on.

How can I help?

Test something and say what happened, on what card, with which model, in Discussions or an issue. "This worked exactly as described" is a real data point — especially from macOS.