Floom · launch video · ROUND 2 · agent > loop + design elevation
Your agent, covered — storyboard
Building a real production agent means solving a huge tangle of runtime plumbing. Floom covers it. 7 scenes, 0:30, 1920×1080. The hook is a reference-grade architecture mind-map of agent complexity that collapses into one Floom agent. Round 2: "agent" is the noun (loop is internal jargon), and the diagram is elevated to title+description cards, curved connectors, and a dotted field.
Truth boundary: every capability shown is a real Floom runtime/ops concern, verbatim from floom.dev — schedule, approvals, run history, resumability, stop/edit, notify-only-when-needed. No chat-UI concern (markdown rendering, streaming, voice, forking, custom UI) is ever shown as something Floom handles.
A dense architecture mind-map of the runtime concerns you'd build yourself — scheduling, triggers, retries, background execution, approval gates, run history, resumability, secrets, supervision, notifications, error handling, state — all wired to one hub. Headline: "To run one agent for real, you build all this."
The same tangle, now denser and heavier with a second web of cross-links. One damning line: "Weeks of plumbing. Before it does one useful thing."
The tangle folds inward — the twelve concerns ghost out to the edges and converge into one premium Floom worker card (gmail-digest · runs hourly · asks before it sends), raised to true center with real depth. Relief. Headline: "Or you write the job. Floom runs the agent."
The receipts. A 2×3 grid of ticked, title+subline capabilities: runs on a schedule · asks before it acts · every run logged · resumes if it drops · stop or edit anytime · notifies only when needed. Headline: "Floom covers all of it."
Real editor marks — Claude Code, Cursor, VS Code, Windsurf, terminal — with the true one-line install. Headline: "From your agent, or your terminal." Command: npx @floomhq/floom mcp install
One concrete run, not an abstraction: gmail-digest summarized 6 new emails, posted to #team, sent 9:00am — after you approved it at 8:59am. Human-in-the-loop stays visible. Headline: "One line. It runs itself."
Light endcard: "You bring the job. Floom runs the agent." plus the black squircle mark, the Floom wordmark, and floom.dev.
