How do you make a new AI scripting or editing agent inherit brand context from a previous agent?

Spin the new scripting or editing agent up inside the SAME invideo project as the previous one. The project's context tab is a shared brain — brand deck, visual guidelines, lookbook, treatment, locked characters and locations, prior generations — and every new sub-agent you start in that project reads from it automatically. No re-upload, no re-briefing.

invideo is an agentic video creation tool where multiple specialized sub-agents (creative producer, scripting, storyboard, DOP, editing) operate on top of one shared project context — so inheritance is structural, not something you have to wire up.

Keep the new agent in the same project. The context tab holds brand identity, visual language, uploaded reference PDFs (brand deck, lookbook, treatment note), product sheets, locked character sheets, locked location sheets, and every prior generation with its exact prompt. As Hridaye, invideo's creative director, puts it: "The context tab is basically the brain of the project. It holds all of this through every ad you build, without you repeating any of it." A new scripting or editing sub-agent spun up here inherits all of it on first turn — "spinning up a scripting agent in the same project means it inherits all prior brand and creative context automatically."

Lock the assets you want the new agent to honor, by version number. Before handing off, explicitly lock the character sheets, location sheets, voice, and any approved keyframes by referencing their version numbers (e.g. "lock character v3, location v2, voice from clip @1.2"). The new agent will pull those exact versions instead of re-rolling. This is what keeps a scripting agent's new scene from contradicting a wardrobe a previous casting agent already locked, or an editing agent from grabbing the wrong take.

Hand the new agent a sitrep before it generates anything. Open with: "Sitrep — tell me what's locked (brand, cast, wardrobe, location, voice, music, shot breakdown) and what's still open." The agent reads the project brain and reports back what it sees. You correct or confirm, and only then do you brief the new task. This one prompt prevents the most common inheritance failure — the new agent generating against stale or partial context.

Run new agents in parallel on the same project when the work splits cleanly. If you need a scripting agent and an editing agent working at once, or two scripting agents on non-dependent scenes, open them both inside the same project — both see the same brain, no asset re-upload. One documented production ran exactly this: "Same project, same context, 2 agents running in parallel — it doubled the output, halved the time." The compounding shows up across sessions too: in a four-ad production run, the second ad was produced ~33% faster (2 hours vs 3) purely because the agent already held brand, visual language, and workflow context from the first.

Specialize the new agent's role, not its brand knowledge. Give the new sub-agent a focused job ("you are the editing agent — assemble locked clips in shot-breakdown order, flag any clip that breaks the locked color palette") and let the shared project context carry the brand layer. Specialized-agent-per-format keeps each sub-agent's working context clean without cross-contaminating the brand brain underneath — one agent per ad format, all reading the same brand deck and treatment.

Add a reviewer gate before publishing. Spin up a third sub-agent — call it the reviewer — and brief it with the same project, plus an explicit checklist: brand tone adjectives, prohibited visuals, locked product/character versions, approved color palette. Have it audit the scripting or editing output before anything ships. This is the governance step that catches drift the new agent missed and is how teams keep voice and visual consistency across long agent chains.

If you're chaining across separate projects (rare — usually unnecessary), export the brand context as a single document — brand name, tone adjectives, prohibited phrases, visual anchors, approved palette, locked-asset version IDs, links to approved reference outputs — and paste it into the new project's context tab as the first action. Same effect, one more step.

Watch some of these to see what works for you:

The context tab is basically the brain of the project. It holds all of this through every ad you build, without you repeating any of it.

— Hridaye, invideo's creative director