GitHub Copilot CLI · local interactive session
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 →
- 01
Install and check access
Install and sign in using the official Copilot CLI guide. Organization accounts may need CLI policy enabled; editor completion alone does not configure the CLI.
- 02
Start copilot in the project
Open a terminal in the folder with the package and assets and run copilot. Check the directory; this route uses a local interactive session.
- 03
Use the correct mode
Shift+Tab cycles plan and ask/execute modes. Review the approach, then return to ask/execute for production and handle command requests as prompted.
- 04
Open the generated files
Ask it to start a preview and return a URL or file path. Review actual playback before requesting export and the video and project paths.
Starting brief for GitHub Copilot CLI
Copy this, fill in the bracketed fields, and send it with the package path or readable guide.
Read the complete brief
I started GitHub Copilot CLI in this project directory and will use ask/execute mode for production. Check the exact .motion path and package entry, then verify runtime tools and assets. 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
- 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.
- 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.
If you get stuck
Planning never executes
Check the mode with Shift+Tab, return to ask/execute, provide the package path and ask it to identify the next actual command.
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.