Local ComfyUI Configuration

Setting up local ComfyUI and the Chrome extension for on-machine AI generation.

Local ComfyUI runs on your own machine, using your own GPU. There are no per-job usage fees. Ordinary Animator reaches your local instance in one of two ways: through a Chrome extension that proxies requests from the browser, or -- if you start ComfyUI with --enable-cors-header -- directly. The connection test says which one answered.

Chrome extension

A browser page will not normally connect to localhost for security reasons. The Ordinary Animator Chrome extension bridges this gap, and is the route to use if you would rather not change how you start ComfyUI.

Install it from the Chrome Web Store:

  1. Open the Ordinary Animator ComfyUI Connector listing.
  2. Click Add to Chrome, then confirm.
  3. The extension appears in your toolbar. Click it to confirm it is active.

The extension only proxies requests from ordinaryanimator.com to localhost:8188 -- it does not access any other sites or data.

Developers: you can also load it unpacked -- enable Developer mode at chrome://extensions, click Load unpacked, and select the comfyui-connector/ directory from the repository.

Local ComfyUI install

A compatible local ComfyUI setup (custom nodes and launch scripts matching Comfy Cloud) is available at:

github.com/alankent/comfyui-cloud-parity

# Clone the setup scripts
git clone https://github.com/alankent/comfyui-cloud-parity.git ~/git/comfyui-cloud-parity

# Create a directory for ComfyUI and run the installer
mkdir -p ~/comfy-local && cd ~/comfy-local
bash ~/git/comfyui-cloud-parity/setup.sh --api-key YOUR_COMFY_CLOUD_KEY

# Start ComfyUI
bash ~/git/comfyui-cloud-parity/start.sh

A Comfy Cloud API key is required to fetch the current node list. See Comfy Cloud Configuration for how to get one.

To update later: git pull in the scripts directory, then re-run setup.sh --skip-torch.

If you already have a ComfyUI install you want to connect directly, see Test Connection below.

Test Connection

Once ComfyUI is running on localhost:8188 and either the extension is active or you started ComfyUI with --enable-cors-header:

  1. Open Settings in Ordinary Animator and choose the ComfyUI section.
  2. In the Local ComfyUI (localhost) block, switch Enable on.
  3. Click Test local connection.

Success names the address it reached and whether it got there via the browser extension or a direct connection. If the test fails, check that:

  • ComfyUI is running (you can open http://localhost:8188 in the browser)
  • The Chrome extension is installed and active (icon visible in the toolbar) -- when ComfyUI is up but the extension is missing, the failure message says so and offers the install link
  • You are using Chrome, or another Chromium browser such as Edge

Your graphics card

Under the connection test, Your graphics card has two fields: the card's name and how much graphics memory it has, in GB.

This is what lets every model row tell you whether an operation will run on your machine, and how slowly -- so it is worth filling in even if you mostly generate in the cloud. Without it, model rows say Local: tell us your card in Settings rather than guessing.

When the local connection test succeeds, ComfyUI is asked what card it is running on and the answer appears as an offer: Detected: RTX 4070, 12 GB -- Use. Press Use to fill the fields, then Save. It is only ever an offer: nothing you have typed is replaced unless you press Use, so if you have two machines, or ComfyUI reports the wrong figure, your own answer stands.

Files you pointed us at

At the bottom of the ComfyUI section, Files you pointed us at lists every file you have told the platform to load from somewhere of your own. Each entry shows the filename and the folder it is loaded from, with a Remove button beside it.

Entries appear here when a run cannot find one of the files its operation names, reports Found <file> in <folder> -- use it, and you press it. That answer is remembered for every later run, which is what you want -- until you move the file back. Then Remove the entry and runs go back to looking where the operation says.

The list belongs to your account, not to a project: where you keep your files is a fact about your machine, so a teammate never sees your entries and is never affected by them.

Each entry is used only for runs on your own ComfyUI. Cloud runs always load the file from the cloud copy and ignore the list entirely. When a run uses one of these files, the folder name is written the way your own ComfyUI writes it, so the same entry works whether you are on Windows, macOS or Linux.