LEARN

Cursor walkthrough

Use Agent in the editor project to read files, run commands and inspect the preview.

← Back to assistants

Cursor desktop · Agent

Follow the product controls

Download a template first. The controls below follow official references; labels can change between versions. See the linked product guide if a control differs. Choose a template →

  1. 01

    Open this project folder

    Open the folder containing the package and assets in Cursor, check the file tree, and start an Agent conversation for this video.

  2. 02

    Open the Agent side pane

    Open Agent with Cmd+I on macOS or Ctrl+I on Windows. Use an agent that can work with files and the terminal, switching from planning when ready to produce.

  3. 03

    Send the path and check tools

    Provide the package path and brief below. Check the actual entry point before preparing inputs, review terminal requests and resolve specific dependency errors.

  4. 04

    Review the running preview

    Open the returned preview URL and check terminal results. Revise by timestamp; inspect a checkpoint’s file scope before restoring, and save approved versions separately.

Starting brief for Cursor

Copy this, fill in the bracketed fields, and send it with the package path or readable guide.

Read the complete brief
I am producing this video in Cursor Agent with the original package and assets in this workspace. Check the files, package entry and terminal tools, then start a real preview after plan approval.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.

After the preview, finish these two steps

  1. Revise by timestamp. For example: shorten the title at 00:08 and use image two at 00:12. Reopen the full preview and check captions, picture, sound and actual duration.
  2. Approve export and save. Ask for the video, editable project and asset paths. Play the complete export and check aspect ratio, resolution and audio sync.
Preview and export checklist →

If you get stuck

The preview URL does not open

Ask Agent to check the running process, actual port and startup log, and send the browser error to this conversation.

The .motion file is rejected or unreadable?

Prefer the original package in the current project with an exact path. For attachments, wait for upload and request the actual filename and outer entries. Use the website’s ZIP-compatible download if available; do not wrap .motion in another ZIP.

Full file handoff instructions →

Official entries and references

References checked on 2026-10-31. Product homepages establish entry points; the content and handoff workflow is MotionGit guidance. Signed-in controls and availability vary by version, region and account. This is not certification of a full .motion export in every client.

← Back to the directory to choose another assistant