เจนภาพไม่ตรงใจ?
ให้ AI ไปสั่ง AI

Build a small local connector that lets me drive meta.ai image and video generation from my own computer. Use Node.js plus Playwright driving a real Chrome browser. Do not use any secret or private API. Do not call GraphQL directly because the community CLI approach that called GraphQL directly is broken now that meta.ai moved message sending to WebSocket, so only drive the visible website like a human would.

Requirements for the connector:

1. Provide a `login` command. It must open a visible browser window on meta.ai and ask me to log in myself with a backup account. Never ask for or accept my password. After I finish logging in, save the session with Playwright storageState as a session file in the user folder so later runs can reuse it.

2. Provide a `status` command. It must check that a saved session exists and that a cookie named ecto_1_sess is present. If either is missing, tell me to run login again.

3. Provide an `image --prompt "..." --out name` command. It must open meta.ai with the saved session, wait for the composer textbox ([role="textbox"]), fill my prompt with keyboard.insertText because typing long prompts character by character is too slow, then press Enter. Then poll every 2 to 3 seconds for a new <img> element that was not there before sending. Download the image from its src into an output folder with a file name that includes the date. Use a timeout around 180 seconds.

4. Support a `--ref` option with image generation. When I pass a reference photo, attach it to the composer first and wait until its preview appears before typing the prompt and sending.

5. Provide a `video --prompt "..."` command. It works the same way but waits for a <video> element whose src is an .mp4 file, then downloads it. Use a timeout around 300 seconds.

6. Locate elements by what the user sees such as roles and visible text. Do not hardcode CSS class names. If an element is not found, run in visible mode with --headed and take a screenshot for debugging.

7. Keep a polite pace. Wait between jobs and never fire many requests in a burst, to lower the risk to the account.

8. After you finish building, test it for real in this order: login, then status, then generate 1 test image, then open the file and show it to me. Fix anything that fails before you say it is done.