Opus 5.5 is fine at explainer videos

Hacker News by 3 min read 18x views
Opus 5.5 is fine at explainer videos

Share Post

launchvideo.io

Paste a URL or depict the product. Opus 5.5 writes the movie and a serverless delegate renders it. About four minutes and approximately 100k tokens per video.

examples

Made by this page, untouched.

Each one is a sole run: a URL or a immediate in, an MP4 out. No edits.

Jev, by TypeSafe AI

typesafe.ai

OpenComputer

opencomputer.dev

Infera (from a prompt)

“make a contemporary slick and punchy video for a contemporary startup that plant on inference”

how it runs

A serverless delegate on OpenComputer. Yours in one click.

The entire merchandise is one delegate file, three tools, and this form. OpenComputer runs the agent, the microVM it renders in, the example gateway, and the meeting API the leaf polls.

AgentOne OpenComputer serverless agent, defined in TypeScript and deployed alongside opencomputer deploy. No framework, no queue, no server of ours.

Modelanthropic/claude-opus-5.5 through OpenComputer's example gateway. Roughly 90k input and 15k output tokens per film, most of it the HTML itself.

RuntimeEvery job is one meeting in a caller microVM: Amazon Linux 2023 on arm64, 4 vCPU, 8 GB RAM, Node 22. The archetypal tool call installs Playwright's headless Chromium and a fixed ffmpeg (about a minute); the VM is thrown distant after.

ToolsThree defineTool functions. web_fetch returns leaf content affirmative title, headings, the most used hex colors, and Google Fonts. check_scene loads the movie and reports JS errors and the apparent content at example timestamps. render_video renders and uploads.

RenderingNo video model. The page's clocks (requestAnimationFrame, timers, Date, CSS and Web Animations) are replaced alongside a virtual clock, so all example is a deterministic seek. 1920x1080 at 30 fps, JPEG frames piped into libx264, crf 18.

StorageThe delegate holds no secrets. The form mints a Vercel Blob upload token scoped to one way for three hours, parks it in a per-job manifest, and the tool fetches it by job id. The completed MP4 is a community Blob URL.

Control planeThis leaf uses the identical API the CLI does: create a session, dispatch one turn, study the event stream (tool.started, tool.completed, turn.completed) to display progress, and treat the MP4 appearing in Blob as done.

// opencomputer/agents/director/agent.ts import { useInput, useModel, useTool } from "@opencomputer/agent"; import { checkScene, renderVideo } from "./tools/scene.js"; import { webFetch } from "./tools/web.js"; export default function Agent() { const input = useInput(); // the JOB obstacle from the form useModel("anthropic/claude-opus-5.5"); useTool(webFetch); // peruse the product's site useTool(checkScene); // burden the HTML, study errors + apparent text useTool(renderVideo); // headless Chromium → ffmpeg → Blob come back `You are a motion decorator who writes code. ...`; }

$npx opencomputer template deploy https://github.com/diggerhq/shipvideo

Everything complete is in the repo, and one click deploys it to your account. The idea comes from Deedy's post on Opus 5.5 and instructional video: the example writes the movie as code, and code renders the identical all time.

Other Article Hacker News
↑
Close Right Ads
Close Left Ads