Qwen Code and Remotion: make a product video
Qwen Code is a terminal coding agent tuned for Qwen's coder models. It edits your project and runs commands, which is all a Remotion video needs.
Give it a measured reference and it builds to exact frames instead of guessing.
Want only the install and a few prompts? The Qwen Code launch video page has them on one screen.
Why Qwen Code suits video work
- qwen mcp add connects the server in one command.
- Or httpUrl in ~/.qwen/settings.json.
- Works with Qwen's coder models and other providers.
- Renders locally.
Start a Remotion project
Remotion turns React components into video: every frame is a render of your component at that frame number, so Qwen Code edits a video the way it edits any other code. You need Node.js. Ask Qwen Code to scaffold the project, or run it yourself:
npx create-video@latestGive Qwen Code a reference to work from
A blank prompt gets a generic video. A real launch video measured frame by frame gets one with a rhythm: when each shot starts, how it enters and how much moves. The library at https://kuchi.kalarislabs.com/mcp is a free MCP server with no sign-in and no API key. Add it to Qwen Code:
1. Add the server from your terminal. No sign-in is needed.
qwen mcp add --transport http kuchi https://kuchi.kalarislabs.com/mcp2. Or add it to ~/.qwen/settings.json by hand.
{
"mcpServers": {
"kuchi": {
"httpUrl": "https://kuchi.kalarislabs.com/mcp"
}
}
}3. Restart Qwen Code and paste the setup prompt.
Then paste the setup prompt, so the agent knows how to use the library:
Connect the Kuchi MCP server at https://kuchi.kalarislabs.com/mcp (Streamable HTTP, no sign-in) and confirm it works by listing its tools.
Kuchi is a library of real product-launch videos to use as inspiration templates. When I want a launch video, read kuchi_get_workflow and follow it: get a short list with kuchi_suggest_templates and show me each one's poster and link so I can choose, in chat or by picking a video on kuchi.kalarislabs.com and pasting its link. Once I pick one, study it with kuchi_get_breakdown, look at its storyboard and note what each shot shows, then call kuchi_plan_remake with my product details and your shot analysis, and ask me for my logo, screenshots and anything else it lists as missing. Build to the blueprint's frames. Before you deliver, run kuchi_check_remake and compare your frames with the reference. Copy only the reference's motion and taste; everything on screen comes from my product.The prompts, in order
- Suggest launch video templates for a data tool and show me the posters.
- Study my pick shot by shot.
- Plan the remake with my logo and screenshots.
- Build it in Remotion on the planned frames and render.
- Check against the reference and fix.
Writing one shot in Remotion
A Remotion video is a React component rendered once per frame. Inside a shot, useCurrentFrame() returns the frame number counted from the start of that shot's <Sequence>, and useVideoConfig() gives the fps and size. Everything that moves is a function of that number, which is why Qwen Code can match a reference to the frame: an entrance that takes 12 frames in the reference takes exactly 12 frames in yours.
The blueprint says how each shot enters. Each entrance has a direct translation:
| Blueprint `enters` | In Remotion |
|---|---|
cut | No entrance animation: the shot is fully on screen at its first frame. |
transition | Animate over the first frames: interpolate(frame, [0, 12], [0, 1], { extrapolateRight: 'clamp' }) for opacity, or a spring() for scale or position. |
hold | Same scene as the shot before: keep the layout and resume the motion where it stopped. |
blank_black, blank_white | Put a frame or two of solid black or white between the shots, as the reference does. |
Here is a product-screen shot that enters with a short transition, written the way Qwen Code should write every shot: assets from public/ through staticFile(), timing from the frame number, nothing random.
import { AbsoluteFill, Img, interpolate, spring, staticFile, useCurrentFrame, useVideoConfig } from 'remotion';
// Blueprint shot 3: kind ui_screen, enters "transition", motion "medium".
export const Shot3 = () => {
const frame = useCurrentFrame();
const { fps } = useVideoConfig();
const opacity = interpolate(frame, [0, 12], [0, 1], { extrapolateRight: 'clamp' });
const rise = spring({ frame, fps, config: { damping: 200 } });
return (
<AbsoluteFill style={{ background: '#0b0b0f', alignItems: 'center', justifyContent: 'center' }}>
<Img
src={staticFile('screens/dashboard.png')}
style={{ width: '78%', borderRadius: 16, opacity, transform: `translateY(${(1 - rise) * 40}px)` }}
/>
</AbsoluteFill>
);
};For a screen recording use <OffthreadVideo src={staticFile('screens/demo.mp4')} /> instead of <Img>. Never use Math.random() or the clock inside a shot: Remotion renders frames in parallel and out of order, so anything not derived from the frame number flickers. Use Remotion's random(seed) when you need variation.
Preview, check and render
Open the Remotion Studio to scrub through the video while Qwen Code works, render single frames to compare with the reference at the times the check gives, then render the file. Launch stands for your composition id.
npx remotion studio
npx remotion still Launch out/frame-90.png --frame=90
npx remotion render Launch out/launch.mp4What trips people up in Qwen Code
- Using "url" in settings.json. Qwen Code reads "httpUrl" for Streamable HTTP.
- Not restarting after editing settings.
- Skipping the stills check.
Questions
How do I add an MCP server to Qwen Code?
Run qwen mcp add --transport http with a name and URL, or add httpUrl under mcpServers in ~/.qwen/settings.json.
Can Qwen Code make videos?
Yes, as a Remotion project it writes and renders.
Is Qwen Code related to Gemini CLI?
It started from Gemini CLI, which is why its settings look similar.

