LEARN

Qwen Code / 通义千问 walkthrough

Start qwen from the project folder, configure a provider, and follow the package entry point.

← Back to assistants

Qwen Code CLI; Qwen chat can prepare content

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 using the official quickstart

    Follow the official installation instructions for your system, reopen the terminal, and check that qwen is available. Installation commands belong in a terminal.

  2. 02

    Run qwen in this video folder

    Open a terminal in the folder containing the package and assets, then run qwen. Quote paths with spaces, or use your file manager’s Open in Terminal action.

  3. 03

    Configure with /auth

    Follow first-run provider setup, or enter /auth in the session. Choose the correct platform and region, and keep credentials out of your video brief.

  4. 04

    Send the brief and verify execution

    Send the brief and check the current folder and package entry point. Use /doctor for configuration checks or /help for commands, then approve production of a real preview.

Starting brief for Qwen Code / 通义千问

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

Read the complete brief
I started Qwen Code in this video project directory. Confirm the directory, accessible .motion package and command tools, then check its instructions and dependencies.

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

Authentication does not work

Run /auth to choose your actual provider, then /doctor. The old Qwen OAuth route is discontinued; use a connection offered by the current official quickstart.

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