Create an AI edit and review the preview

Ask ChatGPT to select useful moments from real footage, save an ordered edit plan, and produce a playable review preview.

Before you start

• Open an existing video project with the correct listing.
• Verify the footage in Footage.
• Save a creative brief in AI edit.
• Connect bsquare-agentos in the ChatGPT conversation.

Start with the goal and main selling point, then let usable footage determine the length. Do not stretch poor coverage to meet an arbitrary duration.

Steps

1. Open the project's AI edit tab.
2. Select Get editing instructions. If a plan already exists, select Get adjustment instructions.
3. Copy the prompt into ChatGPT and add the result you want.
4. The assistant reads the project and listing, samples the real footage, and checks promising intervals more closely. Short motion clips matter: a few still frames cannot prove a camera move is steady.
5. Ask it to save the shot order, source intervals, crop, transitions, and any supported music choice in the same project.
6. Ask for a preview, or return to AI edit and select Generate video preview. The web button compiles the saved plan and submits the preview.
7. Open Finished and wait for Preview ready. If a current preview already exists, review it rather than submitting another.
8. Play the preview and note specific changes.

A saved plan is editable instructions. Compilation freezes those instructions into a particular Source revision. The preview is a real render of that revision, not a completed final video.

Copy into ChatGPT

@bsquare-agentos Create an edit for video project “[project name or ID].” Read its current brief, linked listing, existing plan, scripts, and uploaded footage.

Inspect the real video evidence across each source, then check candidate intervals in motion. Lead with [verified selling point], show how the spaces connect, and use clean hard cuts at normal speed unless a different treatment is supported by the footage.

Prefer a shorter strong cut over weak filler. Use only verified listing text. Save the plan in this project, compile it, and generate a review preview. Tell me what you could inspect, what still needs a human check, and any missing pickup shots. Do not generate a final video or publish anything.

Music is optional. To request it, add: “Use an available authorized background track that fits the pacing. If none is available, continue without music.”

What to inspect

Watch the whole video, then revisit every cut.

• Opening: Does the strongest verified feature appear early?
• Layout: Can a viewer understand how the spaces connect?
• Motion: Are there jerks, blurred turns, repeated pans, or awkward speed changes?
• Crop: Are important features cut off, especially when landscape footage becomes vertical?
• Transitions: Do dissolves create double doorframes or furniture?
• Text: Are address, price, counts, labels, and disclosures correct and readable?
• Ending: Is any hold intentional, and does the closing frame stay long enough to read?
• Audio: If music was added, listen to its level, loop, and ending yourself.

The assistant should say when it could not play or listen to the evidence. Technical measurements are not proof that an edit looks or sounds good.

Copy a specific revision request

@bsquare-agentos Adjust the existing edit in project “[project name or ID].” Keep the same project and brief.

At [preview timestamp], [describe the problem]. Replace that shot with a steadier supported interval, keep the main subject visible, and leave the other good sections unchanged. Save the revised plan and generate a new preview. Do not generate the final video.

After an edit or a brief change, review the new preview. Approval of an older revision does not approve a different cut.

Current editing boundaries

• Director output is vertical 9:16 at 30 fps, with 1–32 clip selections and a renderer limit of 180 seconds.
• Source windows must be at least 0.5 seconds.
• Supported treatments include cuts, short dissolves, focal-point cropping, constant speed from 0.5× to 2×, and bounded adjustments for mild shake, level, and brightness.
• Gentle stabilization uses an 8% zoom. Check that the crop still works.
• Continuous speed ramps are restricted to suitable steady, constant-frame-rate footage and may not be available through every connection. The assistant must check the live tool contract rather than assume support.
• The current Director compiler mutes original clip audio. It can add an available authorized music track, but it does not automatically mix recorded narration or create speech captions.
• It cannot reveal rooms that were never filmed, recover missing detail, or verify legal room use from footage.

Saving a plan does not render or charge for production. Compilation can perform media processing, and preview generation is actual rendering. Do not treat these later stages as a free validation check.

If the preview cannot be made

No footage: Request a shot list or upload the missing clips.

The brief changed: Refresh the project and ask the assistant to update the plan against the latest brief.

The connection cannot submit the brief's required fields: Ask the assistant to identify the unsupported step and stop there. Do not clear the brief or create a duplicate project to work around a version mismatch.

Duration or footage budget exceeded: Shorten the edit, reduce source usage, or split the work.

A preview or link fails to load: Refresh its status or playback link first. Do not start a new render just to replace an expired link.

Next: Approve the reviewed preview and generate the final MP4 in AgentOS.