CodeBuddy plugin · a supported IDE such as VS Code · Craft
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
Open the project folder
Open this video folder in an IDE with the CodeBuddy plugin installed and signed in. This guide uses the plugin Craft interface; standalone clients may differ.
- 02
Switch Ask to Craft
Choose Craft below the composer. Use Plan to review the approach, then check that editing and command execution are available for production.
- 03
Add file context
Right-click the package or project folder in the IDE file tree and choose CodeBuddy > Add to chat, or provide its exact path. Send the brief and verify that it can read the original package.
- 04
Approve and inspect
Start the plan or ask it to produce the preview. Review file diffs, accept or reject changes using the interface, and open the returned preview file or URL.
Starting brief for CodeBuddy
Copy this, fill in the bracketed fields, and send it with the package path or readable guide.
Read the complete brief
I am using Craft in the CodeBuddy plugin with this project added to chat. Check the workspace path and .motion file before proceeding beyond example code. 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
Craft cannot find the package
Check the current workspace file tree, add the file to chat or provide its exact path, and ask for the actual filename it read.
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.