6 min read

Parallel video drafts in Xum: Remotion with an agent per branch

By Founder & Research Lead, Kalaris Labs · Updated

Xum, formerly Mux, runs coding agents in parallel, each in its own workspace. For a video that means you do not have to pick one template up front: build two or three drafts at once and keep the best.

Each agent connects to the same library of measured launch videos, so every draft has a real reference behind it.

Want only the install and a few prompts? The Xum launch video page has them on one screen.

Why Xum suits video work

  • One workspace per draft, so experiments never collide.
  • One line in ~/.xum/mcp.jsonc connects the server to every agent.
  • Compare finished renders side by side before choosing.
  • Also in Settings → MCP if you prefer not to edit files.

Start a Remotion project

Remotion turns React components into video: every frame is a render of your component at that frame number, so Xum edits a video the way it edits any other code. You need Node.js. Ask Xum to scaffold the project, or run it yourself:

npx create-video@latest

Give Xum 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 Xum:

1. Add this to ~/.xum/mcp.jsonc (older Mux installs use ~/.mux/mcp.jsonc). It needs Node.js for npx. No sign-in is needed.

{
  "servers": {
    "kuchi": "npx -y mcp-remote https://kuchi.kalarislabs.com/mcp"
  }
}

2. Or add the same command in Settings → MCP (Ctrl+,).

3. Open a workspace and paste the setup prompt from this page.

Then paste the setup prompt, so the agent knows how to use the library:

Setup prompt
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

  1. Suggest four launch video templates for my product and show me the posters.
  2. Workspace 1: remake template 1. Workspace 2: remake template 3. Same assets in ./brand.
  3. In each workspace: study the reference, plan, build in Remotion and render.
  4. Run the remake check in both and fix the flagged shots.
  5. Put the two renders side by side so I can choose.

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 Xum 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
cutNo entrance animation: the shot is fully on screen at its first frame.
transitionAnimate over the first frames: interpolate(frame, [0, 12], [0, 1], { extrapolateRight: 'clamp' }) for opacity, or a spring() for scale or position.
holdSame scene as the shot before: keep the layout and resume the motion where it stopped.
blank_black, blank_whitePut 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 Xum should write every shot: assets from public/ through staticFile(), timing from the frame number, nothing random.

src/shots/Shot3.tsx
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 Xum 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.mp4

What trips people up in Xum

  • No Node.js on the machine. The config uses npx to bridge to the remote server.
  • Old installs. Mux installs read ~/.mux/mcp.jsonc instead.
  • Too many drafts. Two or three is enough to compare; more just costs time.

Questions

What is Xum?

A tool from Coder, formerly called Mux, for running coding agents in parallel workspaces.

How do I add an MCP server to Xum?

Add it to ~/.xum/mcp.jsonc as an npx mcp-remote command with the URL, or in Settings → MCP.

Why build several drafts?

Templates feel different once your content is in them. Building two cheaply beats arguing over posters.