Skip to content
EditorBrainDocsEspañolOpen EditorBrain ↗

Your context

Save and reuse your styles

Capture an edit with its code, assets and adaptation rules.

Download Markdown ↗

The fixes for nested capture, resource upload, --dry-run, folders in components and captions prepare --style require 0.42.1.

These commands require CLI and API 0.42.0 or later. Check the available version in Versions and availability and editorbrain help before you use them.

A style stores the method, the resources and the code you can adapt to other videos. Saving it does not change your brand and does not automatically change a project's style.

Start from a video you already edited

Terminal
editorbrain styles create my-style --from-project my-video
editorbrain styles check my-style

The CLI walks videos/<id>/ and .editorbrain-local/<id>/, including nested production folders. It collects direction.md and review.md with their source path, files and hashes, recognized receipts and beats with declared times. Receipts are identified by their content (model/provider and generation fields, including jobs or tasks collections), regardless of the file name. It does not invent intervals and it does not turn a render into a human approval. If you omit my-style, the ID will be my-video-style.

Review the candidate resources and complete what to keep, what to adapt and when to skip each technique. Recovered prompts stay as examples from the pilot; turn them into a recipe with variables before you apply them to another brand. Unrecognized, missing or oversized files appear as warnings.

Capture allows up to 2,000 entries and eight folder levels. Prioritize the chosen scene and its dependencies, generated media, SFX and logos; deduplicate by SHA-256 before the limit of 200 portable resources. Exclude vendor, QA, frames and scene copies except explicit dependencies. The portable budget is 90 MiB per file and 512 MiB in total. Final renders are registered by hash as local evidence, with an independent 2 GiB budget and explicit warnings; they are not uploaded. If there are several reviewed scenes, choose --scene .editorbrain-local/<project>/build/styles/<style>/scene.html. Prompts are captured only when their output is linked to media that scene uses; ambiguous or unlinked ones are skipped. It does not run code or call providers. These selection and karaoke improvements require CLI 0.43.0 or later; they are not part of the immutable 0.42.1 tarball.

Take the files to another computer

Terminal
editorbrain styles push my-style --with-resources --dry-run
editorbrain styles push my-style --with-resources
editorbrain styles pull my-style --dir ./other-folder

Files go to the workspace's private storage and use its quota. The CLI verifies the download and SHA-256 before it saves the remote documents. The manifest keeps permanent IDs; on download, files land in production-assets/styles/my-style/.

Images, video, audio, HTML/JS/MJS/JSON, WOFF/WOFF2/TTF/OTF fonts and .py, .swift and .sh source tools are accepted on current versions. Also declare their dependencies: uploading a script does not install Python, Swift, FFmpeg or packages on another machine. Native application projects and other formats need manual preparation. Code travels as a private download; uploading or downloading it does not run it.

A normal text push warns if the style depends on local files. A style push selects only that style's documents; it does not include every project in the folder. It does not overwrite conflicts. A multi-document save can stop after some writes: check the results and try again after you reconcile changes.

Restricted team members do not change shared styles. They can only download resources of the styles associated with their editable projects. Knowing a hash does not grant access.

Reuse a scene's code

Terminal
editorbrain styles component extract --style my-style --id takeover --scene videos/my-video/scene.html --bindings bindings.json
editorbrain styles component list --style my-style
editorbrain styles component prepare --style my-style --id takeover --parameters next.json --out videos/other-video/takeover.html

components.json is the style's private component registry; it does not change the public library. Without explicit parameters, the scene stays captured, waiting to be adapted. It is not presented as a component that is reusable or tested on another video.

The agent should group the editable values in an object inside a script block. Example bindings.json:

JSON
[
  {"name":"headline","type":"string","literal":"Pilot title","occurrences":1,"role":"text"},
  {"name":"anchor","type":"number","literal":1.125,"occurrences":1,"role":"timing"}
]

And next.json:

JSON
{"headline":"This video's idea","anchor":3.375}

Each literal must appear exactly the declared number of times; ambiguous replacements in HTML attributes are not made. Parameters can be string, number or boolean and represent text, clip, time or composition. Parameter names allow camelCase; IDs stay lowercase. role:"directory" allows a folder relative to the workspace, with no symbolic links or private paths (up to 500 entries and four levels). Adjust the path to the output location, but it does not upload the folder automatically: declare its files in resources.json. Fractional times are kept. Preparation keeps the original and refuses to replace the output file.

Declared literal HTML/CSS dependencies are redirected to the verified files on the current computer. Paths built in JavaScript, dynamic imports and external dependencies need an explicit review. The agent should review the code before it runs it.

Image and caption recipes

Terminal
editorbrain media style create my-style --style my-style --file recipe.json
editorbrain styles captions create --style my-style --file captions.json
editorbrain styles techniques create --style my-style --file techniques.json

These commands create documents without replacing an existing one. To adjust a draft that already exists, edit it and run styles check.

DocumentWhat it stores
media-style.jsonModel, references ordered by ID, a prompt with variables, a prior review and an optional animation recipe
captions.jsonFont, weight, size, color, active box, position, forbidden zones and hiding during crossings
techniques.jsonFunction, conditions, anchor phrase, resources, component and steps to verify each technique
components.jsonOriginal code identified by hash and explicit parameters

Minimal recipe:

JSON
{
  "schemaVersion":1,"id":"my-style","status":"ready",
  "model":"chosen-model","referenceOrder":[],
  "promptTemplate":"{characters} in {scene}, palette {palette}",
  "variables":["characters","scene","palette"],
  "reviewBeforeAnimation":["Review identity, geometry and readability"],
  "animation":{"model":"chosen-video-model","promptTemplate":"Animate {scene} while keeping the identity"}
}

referenceOrder contains IDs from resources.json, in the order the provider requires. The recipe can also guide images for thumbnails and carousels. Saving it does not generate images, does not authorize spend and does not replace checking an integration.

Caption example:

JSON
{
  "schemaVersion":1,"id":"my-style","enabled":true,
  "font":{"family":"Arial","weight":600,"size":48,"color":"#FFFFFF"},
  "activeBox":{"color":"#000000","padding":12},
  "position":{"x":0.5,"y":0.8},
  "forbiddenZones":[{"x":0.2,"y":0.1,"width":0.6,"height":0.3}],
  "hideDuringCrossings":true
}

The example colors and positions are not required values for your videos. Positions and zones use coordinates from 0 to 1; sizes and padding use output pixels. font.resourceId can link a verified font of your own. tokenBindings can map fontFamily, color and boxColor to brand keys, such as typography.body; their resolved values are then applied. Turning captions off on the brand or the output profile takes priority.

To prepare a reproducible caption layer:

Terminal
editorbrain styles captions prepare --project other-video --file cues.json --out captions.html

Add --style my-style to preview a different preset without changing the project's saved style. Brand and output-profile constraints keep their priority.

Cues are an ordered array, with no overlapping intervals: [{"start":0,"end":1.2,"text":"Your idea","active":true}]. crossing:true marks crossings where the caption should hide. The renderer captures the transparent layer by calling and awaiting window.renderAt(seconds). The linked font is included in the HTML; if you do not link one, you must have it installed.

The layer hides the text if it touches a forbidden zone or leaves the frame. It does not detect faces and it does not transcribe: the agent must provide the real zones and times. It is not a render of the full video.

Check whether it fits another script

Terminal
editorbrain styles test my-style --project other-video

The result proposes text spans for anchor phrases in techniques.json, with the text found, context, file, JSON field when it applies and the line of the decoded script. Offsets use UTF-16 units; they are not lines of the JSON file. It also identifies ambiguous matches, pending components and missing resources. It resolves the destination brand's constraints too. It does not modify the project, does not render and does not spend credits.

A technique can be declared like this:

JSON
{
  "schemaVersion":1,"id":"my-style",
  "techniques":[{
    "id":"reveal-product","purpose":"Show the product when it is named",
    "when":["The script introduces a product"],
    "anchor":{"kind":"phrase","text":"this product"},
    "resourceIds":[],"componentId":"takeover",
    "omitWhen":["The scene is not about a product"],
    "verify":["The entrance matches the word in the final audio"]
  }]
}

The agent evaluates semantic conditions; the CLI does not pretend to understand any script. Text ranges are not timestamps. A candidate result also does not prove visual quality: review the next video before you call the transfer tested.

API and MCP

resolve_project and the workflow context include styleProduction for the selected style; its documents take part in the context hashes. MCP agents use the existing read/write tools with the expected revision. draft_project_style prepares a draft from the cloud project and the own assets you chose explicitly, including source code that is already saved. It does not discover files on your computer and it does not copy resources that are missing. The local capture, download and prepare commands described here use the CLI; connecting it is not required to read or save an authorized cloud draft.

Also see the libraries, preferences and versions.

Skipped resources and karaoke

push --with-resources and its --dry-run mode group unsupported types in skippedResources. They remain local dependencies and appear in warnings; the style is not declared complete in the cloud. Turn notes into style documents and local tools into requirements. SVG travels as a private binary download, the same as code.

In captions.json, "mode":"karaoke" keeps the phrase visible and puts activeBox only behind the active word. Omit mode or use "phrase" to keep the previous behavior. Provide real per-word times, without estimating them:

JSON
[{"start":0,"end":2,"text":"Hello world","words":[{"text":"Hello","start":0,"end":0.8},{"text":"world","start":1,"end":2}]}]

During pauses between words, nothing is highlighted. crossing and forbidden zones still hide the whole phrase. Times must sit inside the cue, in order and without overlap.

Without a project, styles captions prepare --style my-style --file cues.json --out preview.html generates a preset view at 1080×1920. It reports that it does not apply brand or project preferences; for the final edit use --project.

Find your styles and reuse an edit

Available from CLI 0.43.0. Check the installed help before you use these commands.

editorbrain styles mine --dir ./my-studio lists the styles saved in that folder. styles list still shows the published library. An editing style defines the video's treatment; media styles are visual recipes for images. Use styles create --help to see only the creation options, without walking the whole help.

You can prepare another hook or CTA with variants create comment --project video-id --file changes.json. The file accepts hook, cta and instructions. The variant is a local specification: it shares the original media, keeps the brand preferences and needs its own render and review. It does not change the base project and it does not inherit its approval. variants list --project video-id warns if the base context changed since you created it.

Adaptive styles (0.47.1)

Optional rules distinguish preferences and explicit requirements. A technique can be adapted or skipped for a video, leaving a reason on the project; that does not change the shared style and it does not erase a required failure. styles rules inspect --project ID returns rules and hashes. production verify checks the final file with limited evidence: optional local OCR (--ocr), timed samples and audio measurement. Missing evidence is unknown, not approved. A private sample can be uploaded to ask for an opinion even if observations remain.

styles captions preview --style ID --demo-text "A clear idea" --out preview.html creates a local demonstration, without transcribing or spending credits. --video-out preview.mp4 renders explicitly with a browser and FFmpeg installed. For real captions, provide measured times with --file; demo timing never replaces the transcription. styles captions export --style ID --file words.json --format ass --out captions.ass lists effects it cannot keep. SRT does not store the design. Source modules are private files, not programs that run when they are downloaded.

Check that your version announces styles share or that MCP includes prepare_style_template: available from 0.50.0 and the compatible service.

On the web, open My styles → your style → Share template. The owner chooses the resources, an optional demo and reviews the documents before creating the link. Local resources need to be uploaded first with the style's existing resource function. Disk files are not selected automatically.

Whoever opens the link can see the description and save a copy in their own workspace. They can adapt that copy without changing the original style. Resources that were not selected appear as material they must supply; the required code must be declared and included. Projects, personal memory, private examples and library permissions are not transferred.

The link can circulate among several people and expires in 30 days from the web (1–90 days through the API). Shared links lets you revoke it. Revocation blocks new imports; copies that were already saved remain. An update is another template, never a silent change in the recipient's account.

Files use each workspace's storage, with no AI credits. Importing does not run scripts, change brands, assign styles or authorize a render. Review the content and the rights of the files before you share them.

From an agent you can ask: "Prepare this style to share and show me what would travel." MCP uses prepare_style_template, publish_style_template, inspect_style_template and import_style_template. The CLI offers:

Terminal
editorbrain styles share prepare my-style --ids scene,font,click
editorbrain styles share publish --file reviewed-template.json
editorbrain styles template inspect 'FULL_LINK'
editorbrain styles template import 'FULL_LINK' --id my-copy --expected-version HASH --request-id UUID --user-confirmed
editorbrain styles template status UUID

Keep the same UUID and content when you retry an interrupted operation. The publish file contains the title, description, chosen IDs, reviewed version and explicit confirmations; the MCP contract lists the fields. The link secret must not be stored in project documents or public logs. If you want to download the copy, styles pull my-copy uses the existing flow with hash verification.

Next in guidesMy footage and storage →