Start a new build by copying an FBB
flow_create_flow_from_blueprintCreate a NEW flow that starts as a complete, vetted application rather than an empty file tree — the fastest path to a working build when an FBB (a Final Business Blueprint: a whole app) matches what the user wants. For an app the user merely DESCRIBED, use start_build (the website's own start picks the FBB); this verb is for when the user asked YOU to copy one. Find one with search_blueprints({ kind: "fbb" }). The app's screens, navigation and command-frame wiring are copied byte-exact from the build the FBB points at, its custom tables are re-created under THIS organization's names (the copied code already uses those names — keep them), and a fill-in request is raised for each secret it reads. This ALWAYS creates a new flow: an FBB cannot be merged into an existing build (there are no screen-graph merge semantics). To add parts to a build you already have, use apply_blueprint_widgets instead. THE COPY ENDS YOUR TURN. It is the finished deliverable, not step one — the app is vetted and already runs. When it returns, say its report line and stop: do NOT preview, validate, edit or extend it, and do not start on anything else the user described. The result names the tools not to call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | No | ||
| color | No | A colour the user asked for, as they said it ("pink", "dark green", "navy and gold", or a hex). Resolved to a full custom palette for the flow's appearance — prefer this over guessing customColors hexes. Ignored when customColors is also given. | |
| fonts | No | ||
| shape | No | ||
| theme | No | ||
| title | No | Name for the new flow. Defaults to the blueprint's title. | |
| device | No | Override the copy's default preview device (the frame the builder opens it in): a surface word (mobile, tablet, kiosk, …), a get_scaffold profile, a skin (iphone, ipad, …) or a full DeviceConfig. Omit to follow the blueprint's surface. Changeable later with set_flow_device. | |
| flowId | No | NOT SUPPORTED — passing this returns an error. An FBB replaces an app's entire screen graph, so it can only start a NEW build. It is declared here purely so a caller that assumes otherwise fails loudly instead of having the field stripped and getting a second flow it never asked for. To add parts to an existing build, use apply_blueprint_widgets({ flowId, picks }). | |
| palette | No | ||
| hubToken | No | ||
| blueprintId | Yes | The exact FBB id, e.g. 'flow.coffee-quick-service'. An id without a version suffix resolves to the newest published version. | |
| customColors | No | ||
| supersedesFlowId | No | The EMPTY placeholder flow you were told to build into, when a starter prompt pinned you to one before you knew an FBB would be used. This does NOT write into that flow — nothing can — it marks it as abandoned in favour of the flow created here, so the human's already-open builder tab follows you instead of watching an empty workspace forever. Pass the flow id from your instructions. Ignored (reported back as superseded:false) if that flow has any files, so it can never redirect a real build. |