Use flowmo’s in-app AI as a context-aware router over design, interaction, Flowgen/media, video, and other specialized tool surfaces—distinct from an external MCP host that calls those tools directly.
Where: Editor → AI assistant panel (or ⌘⇧K) — Open the assistant and type a request
Key ideas
- Context-aware routing: The assistant reads the active product surface, selected elements, page/scene structure, attachments, and request intent before choosing a specialized route.
- Specialized executors: Design, interactions, media generation, video, CMS, research, and other routes advertise different tools; no single route can safely perform every action.
- In-app versus MCP: Inside flowmo, the router owns the agent turn. In an external Claude/Codex MCP session, the MCP host is the agent and should call f0/flowgen tools directly instead of starting this second loop.
Steps
- Open the AI panel and start a new session for the goal.
- Select the narrow target and attach only the references the request needs.
- Describe the outcome, constraints, and whether content/layout may change.
- Review the plan, route/tool actions, and canvas result before accepting.
- Start a separate session when unrelated prior context should no longer influence the answer.
Good context
- Exact selected element or group.
- Relevant page/scene/project information.
- Required brand/Brain item or design system.
- Reference image, HTML, PDF, or document needed for this task.
- Explicit responsive, interaction, content, and acceptance constraints.
External host boundary
Claude, Codex, and other MCP hosts have their own model, history, and usage. The same underlying flowmo executors are available directly, so forwarding an external prompt into the in-app router is unnecessary and can duplicate reasoning and cost.
Tips
- Select the narrowest target before an edit request.
- Ask for a plan or stop-before-run boundary for multi-page, expensive, or destructive work.
Limitations and important notes
- Available routes, tools, attachments, and models depend on the current surface, plan, and permissions.
- AI output still requires visual, responsive, accessibility, factual, and cost review.
Troubleshooting
The assistant edits the wrong scope
Undo, select the exact element/group, remove irrelevant attachments, and restate whether structure or content may change.