LEARN

Grok Build / Grok walkthrough

Produce with Grok Build file and command tools, distinguishing chat from template rendering.

← Back to assistants

Grok Build CLI; ordinary Grok chat needs a separate handoff

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

    Install Grok Build

    Follow the current official Build installation and login guide. Ordinary grok.com chat and the Build CLI are different interfaces; production here uses Build.

  2. 02

    Run grok in this video folder

    Open a terminal in the folder containing the package and assets and run grok. Follow first-run sign-in, or use grok login as documented.

  3. 03

    Send the path and production brief

    Ask it to check the project, package entry and tools, then execute the approved preview plan. A conversation-export command is different from video export.

  4. 04

    Review preview and export

    Open the returned preview URL or video and revise by timestamp. Ordinary chat’s + control can attach supported source material; hand off to Build or another local tool if it cannot run the template.

Starting brief for Grok Build / Grok

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

Read the complete brief
I am in this video project directory in Grok Build. Check the path, original .motion package and file/command tools, then follow its entry point. Deliver video and editable sources rather than a chat transcript export.

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

grok export returns text

That command exports a conversation transcript. Ask the assistant to use the template’s actual rendering entry and return the video path.

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