Skip to content
EditorBrainDocsEspañolOpen EditorBrain ↗

Create and review

Studio: review and revise

Comments by moment or point, versions and preference proposals.

Download Markdown ↗

Studio is your project's visual artifact: proposals, samples and delivery. It lets you play the result and say what to change without learning an editor. The agent continues the work from your decisions; Studio does not edit the MP4 by itself.

The new design is available through the API and MCP, and in CLI 0.52.0. It includes the redesigned Studio and preferences open; update the CLI and skills to use it locally. HTML you already generated does not change automatically. Versions.

Where to open it

Where you reviewWhat you need
A computer, with local filesThe artifact and its temporary local server
A phone or another computerThe project's private cloud link and access to that account
A chat with MCP and no CLIprepare_review_artifact: a cloud link or a verified template with the agent's local tools

Delivery respects the destination you authorized. localhost only works on the machine that keeps the server running; it is not a public link for a phone. The cloud option uses existing authorized reviews of the same project. Do not upload a video only to show its preferences.

What you can do in the new Studio

  • Changes: comment on the current moment, mark a range or write a note for the whole video. For a visual problem, point at a spot on the image.
  • Text: review the available transcript. If words have measured times, you can jump to a word or propose removing it. A strikethrough is a proposal; it does not change the audio yet.
  • AI review: read the checks and limits the agent declared. "Not evaluated" does not become approved because you opened the tab.
  • My preferences: see the brand and the settings of that project; prepare change proposals without accidentally applying them to another brand.
  • Compare versions: appears when two versions and recorded differences exist. Each keeps its own times: after a cut, second 12 can be a different moment.

How it works opens the help. With the keyboard, C comments on the current moment, G creates a general note, Space plays or pauses and the arrows move one second. They do not fire while you are typing in a field or using a dialog.

Send your corrections

From 00:08 to 00:11, replace the graphic with a product screenshot. Keep the audio, the captions and the rest of the cut.

Comments in the Studio artifact are browser drafts until you copy or export them. Copy the answer into the Claude or Codex chat so the agent can continue; closing the viewer sends nothing. If it cannot be saved in the browser, keep the export before you leave.

The project's web review and the team's shared comments have their own save actions. A comment written in Studio is not considered remote until it is recorded through that flow. The agent keeps the version, hash, range and point; it does not turn screen coordinates into invented video coordinates.

If a correction is still wrong, point it out again: its link to the previous comment is kept. An agent's claim of "fixed" does not replace your review. Corrections are also captured as feedback and a suggested memory, without changing permanent rules.

Proposals and approvals

The existing phases stay: proposals (directions), review (review) and delivery (delivery). Studio's tabs are not new stages. Direct mode skips earlier creative pauses; approvals that are still valid are reused when their context still matches. There must always be a reviewable delivery.

Preparing, opening or copying an artifact does not automatically record that you saw it or approved it. The agent checks the link, presents the artifact and records the decision with the existing tools, tied to that version and context. Approving a sample does not approve any later render, a brand memory or a spend.

Publish a private sample in one step

With CLI 0.46.0 or later, from the project folder:

Terminal
editorbrain production submit --project my-project --file renders/revision-v1.mp4 --title "First sample"

It prepares the light copy at the saved preview quality, uploads it and registers the review. It keeps a local receipt so interrupted sends can be recovered without duplicating files or reviews. You do not need to edit media.json or invent a UUID by hand.

For a correction, add --parent UUID (or latest if there is only one candidate) and --addresses "the user's actual correction". For an alternative or a technical change, declare its reason with --revision-kind. If a response is uncertain, check the receipt or the review before you send it again.

In MCP, submit_production_review registers media that is already available; it does not read a local path on your computer. If the file is already registered on the project, reuse its identifiers instead of uploading another copy. A project with local storage does not become cloud just because you published without checking its upload permission.

Create a local artifact

This JSON needs a real, light MP4 at the path shown:

JSON
{
  "schemaVersion": 1,
  "projectId": "my-project",
  "version": "preview-v1",
  "title": "First review",
  "stage": "review",
  "video": {"file": ".editorbrain-local/previews/revision.mp4"}
}
Terminal
editorbrain production review-artifact --file review.json --out .editorbrain-local/revision-v1.html
editorbrain production review-open --file .editorbrain-local/revision-v1.html

Keep the HTML, its manifest and the preview copies together. Leave the review-open process running and use the URL it returns. Check playback and comments; an HTTP 200 does not prove the video works. Ctrl+C stops the server. Drafts belong to the browser and port you used: export them before you change either.

From CLI 0.52.0 you can add --context-file workflow.json to review-artifact, with the current response of workflow check --project my-project --details. Its project and context must match to show preferences; do not fill the panel with guessed values. preferences open --project my-project opens only the settings and does not upload videos. Check your installed version before you use these options.

Each local artifact media file allows up to 24 MiB. --media-mode embedded produces a single HTML file that can exceed the chat viewer; do not send base64 to the agent to dodge that limit. This artifact limit is different from the upload and render limits.

Verify and deliver

Terminal
editorbrain production verify --project my-project --file ./renders/final.mp4
editorbrain production delivery-check --project my-project --file ./renders/final.mp4
editorbrain production review-sheet --file ./renders/final.mp4 --out .editorbrain-local/sheet --platform reels

verify checks technical evidence and the configured checks. delivery-check checks the exact file against preferences, origin and destination; it does not render or upload it. The agent also inspects motion, voice, cuts, face, text and editorial consistency. A contact sheet does not prove listening and does not certify creative quality.

The final delivery needs a current approval and current evidence. After that, the cleanup policy you chose in storage can apply, keeping originals and the approved final.

To continue from the web, use “Copy changes for my agent”. The message identifies the exact version you are viewing and directs your agent to its comments, including points marked on an image. It works over MCP or CLI, depending on your connection. The agent keeps the rest intact, records a corrected version, and links the changes to their comments. This does not approve the result or change your brand's memory.

Next in guidesProjects, batches and teams →