Floo
Docs
Documentation
Back to FlooStart designing
Getting started
  • Your first canvas
  • The canvas editor
Agents
  • Connect an agent
  • The Floo Agent
  • MCP tools
Collaborate
  • Comments and mentions
  • Approvals and versions
  • Prototypes
  • Design memory
Imports and integrations
  • Imports
  • Linear
  • Slack
  • Outbound webhooks
Teams and billing
Agents

The Floo Agent

The built-in agent: connect a model key, pick a model, and send briefs through specialist roles.

The Floo Agent designs on its own: no client to install. It runs on the model account each person connects, so model usage is billed by that provider, on your key.

Connect a model key

Open Settings → Agent models, choose a provider and paste a key. Floo keeps it in an encrypted vault and never shows it again; only the last four characters are displayed. One provider is connected per person; connecting another replaces it.

ProviderKey looks likeModelsDefault
Claude APIsk-ant-…Fable 5.1, Opus 5.5, Sonnet 5.5, Haiku 4.5Sonnet 5.5
OpenAIsk-…GPT-6 Astra, GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.6 LunaGPT-5.6 Terra
GeminiAIza…Gemini 3.1 Pro, Gemini 3.7 FlashGemini 3.7 Flash
OpenRoutersk-or-…Kimi, Qwen, GLM, DeepSeek, MiniMax, MiMo and Gemini modelsKimi K2.6

OpenAI models also take a reasoning effort: Low, Medium, High or Extra high. A few OpenRouter models are text-only; they can't look at screenshots, so their runs skip visual review.

Images. Agents can generate images in place. GPT Image 2 runs on an OpenAI key and Nano Banana 2 on a Gemini key; Seedream is available when the server is configured for it.

Queue a brief

  • From Home — describe a screen; Floo makes a canvas and queues the draft.
  • Ask AI (⌘I) — scope the brief to the selected frame or element.
  • A comment — mention a role and the task is pinned to that element (see below).

The task appears in Agent tasks with its status line and progress. Open it to see the brief, the summary, the frames it touched and the timing; Stop a running task, Retry a failed one, or Reply to queue a follow-up with your feedback.

Roles and pipelines

The Floo Agent works under specialist roles. A brief walks a pipeline of them, one stage at a time:

RoleMentionOwns
Floo Agent@designMakes the frame
UX Lead@uxFlow, hierarchy and states
Copywriter@copyEvery word, layout untouched
Brand Keeper@brandPalette, type and radii match the canvas
Accessibility@a11yContrast, semantics, focus, targets
Polish Pass@polishSpacing rhythm, alignment, overflow

Ready-made pipelines in the composer:

  • Solo — the designer alone.
  • Ship — design, then a polish pass.
  • Full — design, copy, brand, accessibility, polish.
  • Audit — UX, brand and accessibility review an existing frame.

Mention a role in a comment

A comment that @mentions a role queues it on the element the comment is pinned to, and the answer lands in the same thread. Only people who can edit the canvas and have a model key can queue work this way; for everyone else the mention stays a plain comment.

PreviousConnect an agentNextMCP tools