Create Flow with AI

Create Flow with AI turns a rough idea into a crisp, well-worded flow spec — in a chat. The AI’s job is intake quality (the what and why, strong acceptance criteria), not implementation planning. It reads your project’s knowledge along the way, so its questions and suggestions are about your project, not generic advice.

Open it from your project’s flow board: Create flow with AI (Pro/Max).

The chat

• Answers stream live — words appear as the AI thinks, so even long answers feel instant.
• Replies are formatted — lists, bold text, and headings render properly in the chat bubbles.
• Clickable choices — when the AI asks a decision question with enumerable answers (“PDF or Excel?”), the options appear as chips under the message. One click answers. Multi-select questions stage several picks with a Send answers button. You can always type a free answer instead.
• Images — attach screenshots via the 📎 button, paste them with Cmd+V, or simply drag & drop them onto the chat. They land on the created flow as attachments.

While you chat, the live preview on the right fills in: summary, description, acceptance criteria, and proposed tasks. Create is enabled once the spec passes the same validation as a manually created flow.

What the AI knows (grounding)

Each turn is grounded in your project’s knowledge:

• ADRs — the AI references relevant decisions and warns when your idea collides with one.
• Documented patterns — it suggests reusing what your project already has.
• Work in flight — it flags overlap with flows that are currently in progress.
• Project description — so it talks about your domain, not a generic app.

Steering the AI (project settings)

Project owners can pin AI instructions for planning in Project Settings. Whatever you write there is injected into every AI answer in this project — ideal for the domain, user roles, your preferred acceptance-criteria format, and the language/tone. Set it once; every chat obeys it.

Sharing your AI with members

AI features require a Pro/Max plan and a personal API key (Settings → AI — Anthropic or any OpenAI-compatible provider such as Google Gemini). By default that applies to every user individually.

Project owners can change that with Share my AI with project members (Project Settings):

• Members without their own key use the owner’s key for AI features in this project, and the owner’s plan covers them.
• A member’s own key always takes precedence — nobody spends the owner’s budget who brings their own.
• The shared key never leaves the server; members can’t see it.
• Set spending limits at your API provider (Google AI Studio, Anthropic Console) — that’s where cost control belongs.

After Create

The created flow lands in the idea state with everything from the chat: the description, the acceptance criteria (visible as a card under the description), proposed tasks (Tasks tab), and any attached images. With Seal for planning checked, the flow is spec-sealed right away — ready for the planning automation to pick it up.