← Back to Blog
Case Study

Claude Code + Google Flow: How an AI Agent Made a Full AI Clay Video (and the One Word Flow Refused)

November 16, 2026·8 min read·By amine.smpc
The three clay characters Claude Code made in Google Flow: Jordan, Inès and Maître Amel

The cast Claude Code made through AutoFlow: Jordan, Inès and Maître Amel.

This is the full story of how Claude Code made a French AI clay video, "Le Piège du Black Friday", through Google Flow and the AutoFlow Chrome extension: the research, three clay characters, twelve clips, seven miniature sets and the final edit. It also made one mistake and hit one wall, and the wall turned out to be a single word.

The finished video

An 86-second vertical video. Inès bought a €399 TV on Black Friday; Jordan, the shop owner, says sale items are never refunded; Maître Amel, a clay lawyer, explains that online buyers get 14 days to change their mind, a full refund including delivery, on their own card.

Clay character Inès with a 399 euros TV, Black Friday
Clay lawyer Maître Amel: online purchase
14 days to change your mind, Code de la consommation
Inès refunded in full

Step 1: research and fact-check

Black Friday falls on 27 November 2026, so Claude picked France's biggest money question of that week: can a sale item be returned? The twist is a real rule: bought online, you have 14 days to withdraw, even on a sale item. Claude checked every line against Légifrance and service-public.gouv.fr, and even asked a second fact-checking agent to confirm one line, whether a seller can refund with a voucher instead of money, before writing a single prompt.

Step 2: three clay characters

Through AutoFlow's character maker, Claude made Jordan the shop owner, Inès the buyer and Maître Amel the lawyer. Each got a face, a name and a custom voice, saved once in Flow, so every clip that names them gets the same figurine. Then it showed the cast and the script and waited for a yes before spending any credits.

Making clay characters in Google Flow with AutoFlow

The character maker in Flow, driven by Claude Code.

Claude Code assembling the cast picture

Claude Code builds the cast picture and checks the script.

Step 3: twelve clips in Agent mode

Claude wrote twelve prompts, each starting with the character's name, and added them as one queue in Agent mode: Omni 1.2 Flash, 9:16, 360p. It caught a bug before Flow did: one of Amel's lines said "Jordan", so AutoFlow attached Jordan's character to her clip. It stopped the run and fixed the line.

The Agent-mode queue in AutoFlow with twelve clay prompts

Twelve prompts, one Agent-mode queue.

Claude Code stopping the run to fix a prompt

Claude stops the run when the wrong character is attached.

Google Flow generating the clay clips

The clay clips generating in Flow.

The word Google Flow refused

Ten clips came back perfect. Two of Amel's lines were refused, held by AutoFlow, and sent back to Claude with the reason. Claude reworded them, then tried a brand-new, more cartoon-like Amel; when told to keep the original, it stopped and put her back. Still refused: three wordings, four tries each.

The real cause was one word. Both lines used the French word for "late", which is spelled exactly like an English slur. Flow's safety filter read the English meaning. Rewriting the sentence without it ("trop tard") and both clips passed. When Flow refuses a clip, check every word, in every language.

AutoFlow holding refused prompts for the agent

AutoFlow holds the refused prompts for the agent.

Finding the word that triggered Google Flow's safety filter

The cause: one word read in the wrong language.

Step 4: collecting the clips

The downloads came back under Flow's own file names, so Claude transcribed all sixteen files with Whisper to match each one to its line. Then it found the bug in AutoFlow that caused it, fixed the download naming, added a test and rebuilt the extension.

Claude Code matching clips to lines with Whisper

Every clip matched to its line.

Step 5: seven miniature sets

Google Cloud billing was off, so Claude made the seven miniature clay sets as Flow images instead, with Nano Banana in another Agent-mode queue: Inès's room, a cluttered shop, a lawyer's library and office, a courthouse staircase, a happy room and a studio.

Seven miniature clay sets made as Google Flow images

The seven sets, made in Flow.

Step 6: the edit

A script pulled out each clip's audio, timed every word and cut each figurine out of its background. Claude trimmed the silence at the start of five clips, wrote twelve scenes (sets, slam words, law citations, close-ups and sound effects) and rendered the video. Every euro amount and article of law on screen came from the sources it checked.

Preparing clips: audio, word timings and cut-outs

Audio, word timings and cut-outs.

The recipe

  1. Research a timely topic and source every fact.
  2. Make the characters once, with a face and a voice.
  3. Queue the clips in Agent mode, one prompt per line.
  4. Fix refusals by changing words, and check every language.
  5. Let the agent collect, build the sets and edit.

It works with Claude Code, Codex or Antigravity. Install AutoFlow, switch on AI agents in Settings, and paste the setup for your agent; see how to connect an agent.

❓ Frequently Asked

Can Claude Code make videos in Google Flow?

Yes, through AutoFlow. Claude Code connects to the AutoFlow Chrome extension with the autoflow-agent MCP server, then makes the characters, queues the prompts, runs them in Google Flow, reads why a clip was refused, rewrites it and downloads the files. In this run it also made the miniature sets as Flow images and edited the final video.

Why did Google Flow refuse the prompts?

Two lines contained the French word for "late" or "delay", which is spelled like an English slur. Flow's safety filter read it as the slur and blocked the clip, even after three different wordings. Rewriting the sentence without that word fixed both clips at once.

How do I fix a Google Flow 'safety blocked' error?

Read every word of the prompt, including the dialogue and in every language. A word that is harmless in one language can be an insult in another. Change wording rather than retrying the same text, and if a realistic-looking face keeps failing, check the reference image too.

What is Agent mode in AutoFlow?

Agent mode is the run mode an AI agent uses when it drives AutoFlow. The queue runs like Full mode in its own Flow project, but refused prompts are held for the agent to reword, every event is reported back to the agent, and the files are collected for it.

Does the agent spend credits without asking?

It should not. In this run Claude Code showed the cast and the script and asked before generating the clips and sets. Running a queue spends your own Flow credits, so the AutoFlow tools tell every agent to ask first.

Are the legal facts in the video checked?

Every claim was checked against Légifrance and service-public.gouv.fr on 16 November 2026: 14 days to withdraw from an online purchase even on sale items (Code de la consommation L221-18), a full refund including delivery on the same payment method (L221-24), and an increase for late refunds (L242-4). It is general information, not legal advice.

Jordan, Inès and Maître Amel are fictional clay characters. The video explains French consumer law as general information, not legal advice.

Related guides