MobileClient (Dummy Node)

The node named MobileClient in this pack is a lie. It's a dummy - the display name in the node menu reads "MobileClient (Dummy Node)" - with zero inputs, zero outputs, and no function to run. Don't go hunting for it in the graph menu expecting to wire it into a workflow. The actual product is the web app that ships alongside it, and that app is a genuinely pleasant way to poke at ComfyUI from your phone.

Why you'd reach for it

The full node editor on a touchscreen is torture. Nodes are finger-sized, edges need a stylus, and pinch-zooming on a phone makes you feel like you're piloting a drone with your elbows. This pack skips the graph entirely and gives you a clean mobile page with the three things you actually want from bed at 11pm: a gallery of what just rendered, a live queue status, and a way to edit the prompt and hit regenerate.

You reach the client at http://SERVER/extensions/ComfyUI-MobileClient/index.html - and the README puts the warning in caps: the index.html part cannot be omitted. That's the #1 thing people trip on. /extensions/ComfyUI-MobileClient/ alone gives you nothing.

How it works

The MobileClient class exists only to register WEB_DIRECTORY = "./web", which tells ComfyUI to serve the extension's static files. The page itself - index.js plus a couple of small modules - is a self-contained app with no backend of its own. It talks straight to ComfyUI's existing HTTP API: /queue for status, /api/history for past images, /api/prompt to submit generations, /api/view to pull images. "Real-time" here means polling every couple of seconds (the default interval is 2000ms), not websocket push. Settings, including any username/password for Basic auth, live in localStorage.

Installing it

Install is about as painless as it gets. Via ComfyUI Manager, search "ComfyUI-MobileClient" - the pack is published to the Comfy Registry - or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/vkff5833/ComfyUI-MobileClient

Then restart ComfyUI. No pip dependencies, no model downloads, no requirements.txt to fight over. The pyproject.toml is essentially empty, which is refreshing in an ecosystem where installing a node pack routinely drags in a second copy of transformers.

Where people get burned

Field editing is pattern-based, not schema-aware. The app decides which workflow inputs are seeds, prompts, integers, or floats by matching input names against key patterns (defaults: seed/noise_seed, prompt/text, steps/width/height, cfg, and so on). If your workflow uses a custom node that names things differently, those fields just won't show up as editable. You can extend the patterns in the settings screen, but it's fiddly for exotic nodes.

The security part is on you. The whole point of a mobile client is reaching your box from outside your LAN, and ComfyUI's API is unauthenticated by default - anyone who can reach the port can run arbitrary workflows. Set a username and password in the app's settings and lock the server down before you open it up. The gallery and shortcut keys (arrows to browse, Space to regenerate, Enter to edit) are the pleasant surprises.

Is it the best mobile option? It's small and unglamorous, and there are fancier remote-UX packs out there. But for "check the queue, tweak the prompt, regenerate," this one is honest about what it does - no models, no keys, no extra services, just a spare browser tab on your phone.