Meta AI Browser Launcher

This is the node the rest of the pack depends on and the one nobody wants to talk about. MetaAiSingleVideoGenerator and MetaAiImageGenerator both work by driving a real Chrome window against meta.ai/media - which means they need a browser profile that's already logged into Meta. The Meta AI Browser Launcher is how you get that profile: it opens a fullscreen Chrome window pointed at meta.ai, you sign in and maybe solve a CAPTCHA by hand, you close the window, and the cookies are saved for the other nodes to reuse.

That's the entire job, and it's genuinely the difference between this pack working and failing at a login wall.

How it works

The node runs Playwright in sync mode and launches a persistent Chromium context - persistent being the key word. Instead of a throwaway browser, it uses a profile directory inside the pack folder (default meta_playwright_profile3), so anything you do in that window - login, cookies, session - survives after you close it. It starts fullscreen and non-headless on purpose: the author wants you to interact with it. While the window is open, the node watches the Chrome process and holds its own execution until you close the window. Then it reports the profile path.

Like its siblings, it forces a re-run on every queue (IS_CHANGED returns NaN). And because it blocks while the browser is open, you want to run it as a standalone step, not chained in the middle of a generation workflow.

Inputs and output

Two inputs, one output, nothing to figure out.

• activate - a BOOLEAN, default true. Set it false to skip launching the browser entirely; the node just returns a "deactivated" string.
• profile_name - which profile directory to use. Default meta_playwright_profile3 matches what the video generator expects. The image generator, by default, uses a different profile (meta_playwright_profile), so if you're planning to use that node too, keep the names straight or set them explicitly.

The single output, profile_path (STRING), is the absolute path to the profile folder - mostly informational. You don't need to wire it anywhere for the pack to work; it's there so you can see where your session is stored and point other nodes at it if you want.

Installing it

Same story as the rest of the pack: install via ComfyUI Manager (search "ComfyUI-MetaAI") or clone and install by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/systemaiofinterest-wq/ComfyUI-MetaAI.git
cd ComfyUI-MetaAI
pip install -r requirements.txt
playwright install

playwright install downloads the Chromium build - skip it and nothing in this pack will launch a browser. No model files, no API keys; the only "heavy" dependency is Playwright itself. The README also points Windows users at instalar_ffmpeg.bat (needs WinRAR and admin rights), but that's only relevant once you generate video.

Where people get burned

• Run it once, then let the other nodes use the profile. Forget it and the generators hit Meta's login wall every single run.
• The node blocks your queue until you close the window. If ComfyUI looks frozen "on" this node, it's not hung - a Chrome window is open somewhere. Close it and the node finishes. This one got me: it's easy to think ComfyUI crashed.
• Profile names matter. The video generator defaults to meta_playwright_profile3; the image generator defaults to meta_playwright_profile. Log in under one and generate under the other and you're not logged in. Set them consistently.
• It's a manual step, not automation. There's no auto-login and no CAPTCHA solver; the point is that a human does the once-per-machine login. The author is upfront that the whole pack is a scraping workaround, so expect Meta to keep tightening the login flow.

If your only goal is free meta.ai video or images, this node is step one and you never touch it again. If the login-session juggling sounds like more trouble than it's worth, that's a fair read too - but it's the price of admission for this pack.