Your brand is the starting point; each video can have exceptions. Asking for a different edit should not change how all of your future videos are edited.
What you can set
| Area | Examples | It applies when… |
|---|---|---|
| Identity | Name, colors and typography | The project uses that brand |
| Language | Primary language, pronunciations and glossary | Voice or text is created or adapted, or Tempo transcribes proper names |
| Editing | Pace, target duration, visual support, presenter framing | It fits the real content |
| Text | Amount, captions, treatment and position | Text or captions are enabled |
| Media | Your own, the internet or generated; exclusions | Visual resources are needed |
| Sound | Music, voice, SFX density and limits | There is an editorial reason to use it |
| AI tools | Quality, format, language and preferred provider | The tool is available and authorized |
| Guidance | Who decides, how many questions and when to review | During the edit |
Allowing images from the internet does not mean using them in every scene. The agent should consider that source when it adds information. Turning SFX off does exclude added effects, including those that come inside components.
Three independent decisions
| Setting | What it controls | What it does not do |
|---|---|---|
| Creative direction: automatic or guided | Who chooses the look and the resources | It does not change the quality bar |
| Questions: essential, collaborative or none | When to ask you | It does not grant a budget |
| Review: proposals, a sample or direct | When you want to see or approve progress | It does not connect providers |
Letting the AI decide hands off a creative decision; it does not mean always using the same preset or ignoring constraints. If a style preference does not fit, the agent can propose or record an adaptation. Explicit constraints and approvals stay in force.
These options can be changed later. Moving from automatic direction to guided direction fills in only the pending categories; it does not erase earlier answers.
Brand, style and project
- Brand: what is usual for that client or business.
- Style: a reusable method, adaptable to the topic.
- Project: the job and its exceptions, only for that video.
Required brand constraints need an explicit exception with a reason. The colors in an example do not automatically replace yours. One brand's preferences are not borrowed for another.
Memory you control
A correction does not automatically become a permanent rule. It can sit as a learning proposal; you decide whether it is saved for a project, a style or a brand. A rule tied to a series or a format should not apply to every video.
For this tutorial series, use real screenshots when I name a tool. Save it for this series; do not apply it to my personal videos.
Corrections are captured as feedback and suggestions, not as global changes. Memory and corrections explains how to see them, confirm them and resolve conflicts with settings. Taking part in product improvements is a separate decision; it is not inferred when you accept an editorial preference.
See your preferences in Studio
You can ask "show me this project's preferences." The new Studio shows the project's real brand and lets you prepare change proposals. Copying them does not save them: the agent confirms the scope, checks the current revision, saves and reads the result back. MCP offers open_preferences_studio; the preferences open command is available from CLI 0.52.0. HTML you generated earlier is not redesigned by itself. Studio and reviews.
Check what your agent read
editorbrain workflow check --project my-project
editorbrain resolve my-project --dir ./my-videos
The first reads the connected context; the second resolves the local documents and saves their hashes. If they differ, sync and review the conflict before you edit. A read receipt does not prove that a video has already been produced.
Next in guidesMemory and corrections →