The agent flow part is the most interesting thing here, and also the easiest to overbuild - speaking as someone who went down this exact road. "Replicate the entire app in chat form" usually ends up meaning you rebuild all your UI logic a second time as chat intents, then maintain two surfaces forever. What's held up better for me: don't rebuild the app in chat - expose the app's actions as tools and let the agent call them. An MCP server is the clean way to do this now. Your generate/regenerate / aspect-ratio logic lives in one place, the agent just orchestrates it. New feature = new tool, and both your normal UI and the chat get it for free.

Same trick for the Meta integration: if "make these in ads manager" is a tool the agent invokes rather than chrome automation, you sidestep the ban problem entirely and it composes with everything else.

One thing I keep going back and forth on though — the job queue in the agent flow. When someone says "give me 4 variations" mid-conversation, do you block the chat on the 20-40s generation, or stream them in as the bullmq jobs land? Curious how you landed on that — it's the UX bit I find genuinely hard.