horizontwo/Lenzon — Lenzon: Code to Animated Video
Transcript
QuickFacts
Welcome to Lenzon, also known as Codesplain. This is a platform that takes any code repository and turns it into a polished animated video, complete with narration and visual diagrams. Let's explore how it works.
PlainEnglish
Here's the big idea. You paste a GitHub URL, and Lenzon produces a three to ten minute animated video that walks through the architecture, highlights risks, and explains what the code actually does. All narrated, timed, and ready to share.
QuickFacts
Under the hood, Lenzon is a TypeScript monorepo. The server runs on Next.js fifteen, hosted on Vercel. The player is built with Vite, using anime.js for canvas effects and Three.js for future 3D diagrams. State lives in Postgres via Prisma. The heavy lifting — cloning repos, analyzing code, rendering videos — happens on AWS Fargate workers, orchestrated through SQS queues. And the two AI agents run on Anthropic's platform: Managed Agents for the code analyzer, Messages API for the script producer.
Architecture
Let's zoom out and see how the pieces fit together. The user sends a request to the Vercel server. That server enqueues a clone job, which a Fargate worker picks up. The worker shallow-clones the repo and uploads it to S3. Then the server hands that tarball to Agent One — the Code Analysis Gnome — who explores the code and delivers a structured report. That report flows to Agent Two, the Producer, who writes a presentation script. The script is sent to the browser Player for live playback. And if you want a video file, the Render Worker captures the playback frame by frame and muxes it into an MP4.
Architecture
Think of it like a relay race. Agent One is the research assistant who reads the codebase and writes a detailed summary: architecture notes, quality grades, plain-English explanations. Agent Two is the presentation designer who takes that summary, picks visuals, writes narration, and creates the slide deck. The first agent delivers data; the second agent turns it into a story.
Architecture
Here's what happens when you use the web UI. You paste a GitHub URL and click Analyze. The browser sends a clone request to the server, which enqueues a job for the Clone Worker. That worker pulls the repo, tars it up, and sends back a presigned URL. The UI polls until the clone is ready, then kicks off the analysis. The server starts a Managed Agents session for the Gnome, who downloads the tarball, explores it, and eventually calls submit code analysis with the results. The UI polls again, and boom — you see the analysis report.
Architecture
Let's see where the code lives. The repo is a monorepo with two main apps. The server folder holds the Next.js backend — API routes, agent orchestration, and the Prisma schema for Postgres. The player folder is the Vite-based browser app — the core rendering engine, the script player, and twenty-six visual templates. The infra folder contains all the AWS CDK code for Fargate workers, queues, and buckets. And shared types is a package that both apps import for consistent type definitions.
Architecture
Why Fargate workers? Because analysis and video rendering can take minutes or even hours, way beyond any serverless timeout. Each worker lives in a private VPC, reads jobs from its own SQS queue, and reports back to Vercel via HMAC-protected callbacks. The clone worker is sized for fast git operations. The pipeline worker orchestrates the full chain. And the render worker is the biggest, with four vCPUs and eight gigs of RAM to handle Playwright and ffmpeg.
Architecture
The player uses a two-layer rendering strategy. The canvas layer is fast and fluid — perfect for animated text boxes, dramatic effects like zoom and glow, and cinematic title cards. The DOM layer sits on top and handles things that need native browser rendering: syntax-highlighted code, accessible text, and interactive diagrams. Together they let you mix snappy animations with rich detail.
Community
Let's check the pulse of this repo. It's marked active — the last commit was just yesterday, June sixth. There's been one commit in the last thirty, ninety, and three hundred sixty-five days, all from Rick Gonzalez. It's a solo project right now, with two branches and no tags yet. Early stage, but actively maintained.
PlainEnglish
So that's Lenzon. A two-agent system that turns code into video. The Gnome analyzes, the Producer scripts, and the player renders it all in your browser. Fargate workers keep the heavy lifting off the serverless platform. The stack is modern, the flow is async, and the result is a shareable animated explainer. Thanks for watching!
How this was made
Lenzon read horizontwo/Lenzon and generated this walkthrough automatically. The narration above is the transcript of what it says.
Explain a pull request from your own repo
Point Lenzon at a repo or a pull request and get a narrated walkthrough like this one.
Try it