Runtime compatibility
Production and export depend on execution tools and the template’s runtime dependencies, rather than the model brand. Creative tools such as Claude, Codex, Cursor, GitHub Copilot and Grok are not partnership endorsements or a claim that every client has been tested.
| Tool type | What it can do | Export requirements |
|---|
| Chat-only web or mobile assistant | Explain instructions and prepare copy and inputs | Export cannot be promised; hand off to a tool with execution capabilities |
| Desktop or CLI assistant with real file access, unpacking and commands | Inspect packages, edit content and run production steps | Must also support the package’s runtime.profile and rendering dependencies |
| The local renderer specified by the template | Read production instances and create previews and video | Follow motion.json, README and motion.lock.json; common HTML/Canvas templates need Node.js and a browser, and video assembly may need FFmpeg |
Work modes and model selection
Use a work / Agent mode with file operations and command execution. The recommendations below are MotionGit guidance. A capable model handles understanding and execution; prepare the browser, Node.js, FFmpeg or other dependencies specified by the package.
| Creative tool | Entry to use | Recommended model |
|---|
| Claude | Claude Code execution tasks, or a desktop Code / Cowork workspace with file and command tools | The most capable coding / Agent model available to you |
| ChatGPT / Codex | ChatGPT users should use Codex with a local project / work task connected to the production directory | The most capable coding model available; use a higher reasoning setting when offered |
| Cursor | Open the production directory in Cursor Agent; approve file edits and terminal commands as needed | Choose the most capable coding / Agent model available to your account |
| GitHub Copilot | Start Copilot CLI in the production directory; use ask / execute mode for production | Choose the most capable coding / Agent model available to your account |
| Grok | Grok Build Agent environment with file and terminal tools; ordinary Grok chat can prepare content | The most capable coding / Agent model available in that environment |
Copilot CLI plan mode prepares an approach; switch back to execution to produce files. Approve required tools as needed. Entries and models depend on your client and account. In ordinary chat, prepare content and hand off to a tool with execution access.
Work entries checked against official documentation on 2026-10-07: OpenAI app and local tasks, Claude work and computer use, and Grok Build CLI. Cursor and Copilot entries checked on 2026-10-08: Cursor Agent and GitHub Copilot CLI. The Claude Code installation entry was also checked on 2026-10-10: Claude Code quickstart. These describe tool capabilities, not completed template export tests.
Recorded tests and unverified environments
- 2026-10-06: dark-tech-kit 0.1.0 completed cold unpacking, still rendering and video with audio on macOS, Node 23.11.0, Chrome 154.0.8037.98, Playwright Core 1.58.2 and FFmpeg 9.0.1. Evidence: the project’s public acceptance record C4 acceptance record. This proves only that version’s execution workflow, not approval of the latest version, other templates or visual quality.
- Windows, Linux, other versions and each specific client of the brands above: full production and export remain unverified. Website browser tests are not template rendering tests.
Read the package’s instructions and dependencies first. Confirm file and command access, and obtain user authorization before installing dependencies, using the network or reading external assets. Inspect, preview, then export. Chat-only tools can prepare inputs but must not claim they rendered a video.
