Keep a follow-up request attached to the editor you are actually working in, understand the difference between embedded documents and native Designer/Compositor surfaces, and recover cleanly when an editor handoff needs another turn.
Where: Flowgen → left rail → Agent; open or focus the target editor, then continue in the same Agent conversation.
Before you start
- Open the Flowgen canvas and use the Agent from its left rail. For MCP use, connect your host to the f0 MCP server; the host remains the reasoning AI.
Key ideas
- Follow-ups keep the current editor target: The Agent tracks whether the task belongs to a native Designer, native Compositor, or an embedded document node so a follow-up does not accidentally restart as an unrelated canvas action.
- Native and embedded editors use different tool surfaces: Website/document, 3D, image layers, and other supported iframe editors use the document surface. Designer and the Video Editor/Compositor are same-window native editors with their own open/invoke/close tool families.
- MCP is the host AI, not a second Flowmo agent loop: An external MCP client reasons with its own host model and calls Flowmo tools. Opening an editor exposes Flowmo operations; it does not send the conversation to a second AI assistant.
Steps
- Open Agent from the Flowgen left rail and begin or continue the task in the conversation tied to the current Flowgen project.
- When the work is in an embedded editor node, identify the actual editor node first, open it, then use its document tools while the overlay is ready. Keep the calls scoped to the active iframe project.
- When the work is in a Designer node/project, use the Designer-specific editor tools. When it is a Video Editor or videoCompose node, use the Compositor-specific tools; do not pass either surface to the iframe document editor.
- Describe a follow-up in terms of the open artifact and the requested change. The Agent carries the active editor context across turns and routes to the native surface where appropriate.
- If a tool call completed but the next request is refused, check the reported open editor/ready state and project scope before trying again. Reopen the correct surface if it was closed or another editor replaced it.
- For MCP, inspect the live tool list and the editor’s current state before writing. Read the edited document after the operation and visually verify when the request changes appearance.
Editor routing at a glance
- Embedded website/document/section/image-layer/3D node: open the node editor, then use surface="document" tools.
- Designer node or project: open Designer and use Designer tools; it is not an iframe.
- Native Video Editor project or videoCompose node: open Compositor and use Compositor tools; it is not an iframe.
- Flowgen canvas graph: use Flowgen node/connection/run tools, not the document surface.
What carries across turns
- The active editor kind and target node/project.
- Recent tool activity and the next action needed to continue the same edit.
- Project scope for embedded-editor operations.
- The correct native tool family for Designer or Compositor work.
MCP host versus Flowmo in-product assistant
- The MCP client’s host model decides what to do and when.
- Flowmo MCP tools perform product operations with the authenticated user’s permissions.
- The in-product Flowgen Agent is a separate UI surface; MCP calls do not require sending the user’s prompt into that Agent.
Tips
- Open only the editor needed for the current step; the app has one active editor overlay at a time.
- Use the project/node id returned by the editor discovery tools rather than guessing which canvas is active.
- After writing, read the state again; a successful operation response is not proof that the intended design rendered correctly.
Limitations and important notes
- A closed or replaced editor is no longer the active target.
- Heavy Compositor or 3D documents may need a longer wait before the editor reports ready.
- The canvas graph itself is not an embedded document and has no document-surface screenshot.
Troubleshooting
The Agent says the Designer is not ready even though the deck is visible.
Check whether the native Designer surface is currently open and ready; use its dedicated open/invoke tools rather than the iframe document route, then retry against the returned project/node target.
A follow-up edits the wrong surface.
Name the intended open artifact in the follow-up and verify the reported active editor. If the target changed, reopen the desired editor before continuing.
The MCP call cannot find an editor.
Discover the actual editor-capable node/project first. Not every node is an editor, and Designer/Compositor must not be opened as document iframes.
Related guides
- Flowgen Make and Agent: open Assistant, plan work, and use live reasoning
- Designer node: complete reference
- Flowgen Video Editor node: native composition inputs, editor surface, outputs, persistence, and MCP
- Edit Flowgen editor documents through MCP
- MCP: drive Flowgen Native Video Editor with the host AI