- Removed the `sceneSpan` function from the `useAutoCaptions` hook to simplify caption insertion logic. - Updated the `insertFresh` function to streamline caption creation by removing unnecessary parameters. - Introduced new functions in the `timing.ts` file to manage transcript duration and caption source handling, improving accuracy in timing calculations. - Added caching for transcript lengths in `utils.ts`, allowing for synchronous access to transcript durations after initial reading. - Enhanced the overall caption handling process to ensure better integration with the timing system and improve performance.
The professional video editor built for agents
npx skills add diffusionstudio/skills -g
Why Diffusion Studio
Diffusion Studio is an open-source video editor built for agents. It runs as a desktop app with a command line that lets an agent watch and listen to footage and cut it on a timeline.
Every output opens in a full video editing interface, so you can pick up and refine exactly where the agent left off.
What it's for
- Video editing: raw footage into a finished cut
- Motion graphics: explainers, promos, and title sequences
- Generative assets: images, video, and voiceover, declared in code and composited into the timeline
- Clipping: highlights from a long video, reformatted for social
- Video understanding: summaries, scene search, quotes with timestamps
Getting started
Use with Claude Code, Codex, Cursor, Copilot, or Gemini CLI. Install the skill once, globally:
npx skills add diffusionstudio/skills -g
/editor is the main skill you'll use. Ask for what you want in plain language. Behind it is dapi, the CLI that drives the app.
Prompt examples
Motion graphics
/editor Create a ~20-second promo for vercel-labs/native in Vercel's presentation style. Research its official website, GitHub, and brand guidelines; use authentic assets and verified product features, with crisp typography, polished motion, and a strong final CTA.
/editor Recreate the 3blue1brown animation from https://youtu.be/HEfHFsfGXjs, closely matching its visual style, pacing, framing, colors, labels, and transitions. Use the exact collision mathematics from Gregory Galperin's original paper, do not approximate the physics.
Video editing
/editor edit the footage in /path/to/folder
/editor turn this footage into a polished YouTube video. Add readable captions and an attention-grabbing graphic in the opening to give viewers a strong visual hook.
Clipping
/editor Can you pull the best 30-second moment from https://youtu.be/MtQ0qxyf-Ds and make a vertical version for social?
/editor Make a 15-second version of this launch video. https://x.com/claudeai/status/2045156267690213649
Video understanding and reasoning
/watch In three bullets, explain what starts the conflict. Include timestamps. https://youtu.be/aqz-KE-bpKQ
/watch Name three recurring locations and give one visual cue that distinguishes each. https://youtu.be/dQw4w9WgXcQ
Made with Diffusion Studio
Both were created by prompting. The compositions are published in diffusionstudio/open-projects:
| Launch video | Raise announcement |
|---|---|
![]() |
![]() |
Compositions as code
Compositions are SolidJS modules. dapi mount compiles them and renders each element into an editable node in the document; re-mounting rebuilds in place, like reloading a webpage. Solid's control flow (<For>, <Show>, …) and any npm package are available to compose the tree, and generative assets are declared as values and produced on mount:
import { For } from "solid-js";
import { generate } from "@diffusionstudio/jsx";
const hero = generate.image({ prompt: "A neon city at night, cinematic" });
const motion = generate.video({ prompt: "slow camera push-in", startFrame: hero });
const TITLES = [
{ text: "The Grid", start: 0, end: 2.5 },
{ text: "Neon Nights", start: 2.5, end: 5 },
];
export default function Project() {
return (
<rect scene="intro" name="Intro" width={1920} height={1080} fill="black">
<video src={motion} width={1920} height={1080} />
<sequence>
<For each={TITLES}>
{(t) => (
<text
textAlign="center"
textBaseline="middle"
fontSize={128}
width={1920}
height={1080}
fill="white"
start={t.start}
end={t.end}
>
{t.text}
</text>
)}
</For>
</sequence>
</rect>
);
}
Everything a mount produces stays a first-class editor node, so a person can pick up in the UI exactly where the script left off.
Seeing and hearing the media
Cutting footage requires understanding it. The CLI ships the inspection tools an agent needs to work with media it cannot watch:
dapi media probe clip.mp4 # container + codec metadata, like ffprobe
dapi media grab clip.mp4 -t 0 12 45 # decode frames to PNGs
dapi media filmstrip clip.mp4 # grid of video frames
dapi media waveform track.mp3 # audio waveform, silence flagged
dapi media transcribe interview.wav # timed, word-level transcript
dapi media listen interview.mp4 -p "what is said in the intro?" # ask a multimodal model
dapi capture intro # see the canvas itself, by the node's id in the JSX
CLI at a glance
The core loop is three commands:
dapi open # use -b to run the editor headless
dapi mount hero.tsx # render a composition into it
dapi node render -o hero.mp4 # encode the scene to disk
| Command | Purpose |
|---|---|
dapi open |
Launch the app and open (or create) a project folder, anywhere on disk |
dapi context |
Summary of app state |
dapi capture |
Render a node in isolation to a labelled contact sheet, or one PNG per position |
dapi media … |
Inspect a file by id or path: probe, grab, filmstrip, waveform, transcribe, listen |
dapi models / dapi voices / dapi fonts |
Discover generation models, speech voices, local fonts |
dapi screenshot / dapi logs |
The app itself: capture the window, read recent console output |
dapi fetch |
Download a video from yt/tt/ig |
dapi whoami |
The authenticated account |
dapi report |
Report a bug in the CLI or the app: diagnostics bundled, filed as a GitHub issue via gh |
Conventions throughout: single results are one JSON value, collections are JSON Lines, errors go to stderr with exit code 1. Everything is built to be piped, grepped, and driven by a program.
Documentation
- CLI reference: every command, its options, and its output
- JSX reference: the composition markup with elements, timing, paints, generative assets, and captions
- Examples: runnable compositions, from basic scenes and generative assets to three.js and raw WebGPU
Repository layout
| Path | Package | What it is |
|---|---|---|
apps/web |
@diffusionstudio/web |
The editor UI (Solid + Vite) |
apps/desktop |
@diffusionstudio/desktop |
Electron shell hosting the editor |
apps/cli |
@diffusionstudio/cli |
The dapi CLI |
packages/jsx |
@diffusionstudio/jsx |
JSX runtime, types, and generated assets (generate.*) for compositions |
Contributing / local setup
Requirements: Node 20+ and npm.
git clone https://github.com/diffusionstudio/editor.git
cd editor
npm install
cp apps/web/.env.example apps/web/.env # required: the app won't run without it
npm run dev:web # editor in the browser (Vite dev server)
# or
npm run dev:desktop # editor as a desktop app (Electron): builds the CLI, starts the web server, launches the app
To put dapi on your PATH (macOS/Homebrew layout; adjust the link target for other setups), link it once:
npm run symlink:create --workspace=@diffusionstudio/cli
The link points at the CLI build, which npm run dev:desktop refreshes on every start, so the linked dapi always runs the latest code.
Before sending a PR:
npm run check # typecheck all workspaces
npm run lint # lint all workspaces
License
The brand assets in apps/desktop/assets are not covered by this license. Copyright (c) Diffusion Studio Inc. All rights reserved.

