horizontwo/Lenzon — Lenzon: Code to Video Pipeline
Transcript
QuickFacts
Welcome! Today we're exploring Lenzon — a system that reads code and turns it into shareable video explanations. Let's see how it works.
PlainEnglish
Here's the core idea: you give Lenzon a repository, and it produces a three to ten minute video that explains the architecture, highlights risks, and breaks down what the code actually does — all narrated and ready to share.
QuickFacts
Under the hood, Lenzon combines Next.js for the server, Vite for the player, and a fleet of AWS Fargate workers for the heavy lifting. The analysis agents run on Anthropic's APIs, and everything is wired together with S3, SQS, and Postgres for state. Let's walk through the architecture.
Architecture
Let's trace the journey. You paste a repo URL into the UI. The server enqueues a clone job — a Fargate worker pulls the code and uploads it to S3. Agent One, the Code Analysis Gnome, curls that tarball, explores the file tree, and submits a structured analysis. Agent Two, the Producer, reads that analysis and your preferences, then generates a presentation script. The player renders it in your browser with narration and animations. If you want to share, the render worker captures it frame by frame and muxes it into an MP4.
Architecture
Here's how the repo is laid out. The apps folder holds the server — that's your Next.js API and agent orchestration — and the player, which is the Vite rendering engine with canvas effects and twenty-six visual templates. The infra folder has all the AWS CDK stacks and the three Fargate workers: clone, pipeline, and render. Shared types live in packages to keep the contracts consistent.
Architecture
Let's walk through the interactive flow. You enter a repo URL in the browser. The UI calls the server to start a clone run. The server enqueues a job, and the clone worker pulls the repo, tars it, and uploads to S3 with a ten-minute presigned URL. The UI then starts an analysis session. Agent One curls the tarball, explores the code, and after about ninety seconds, submits a structured analysis back to the server. The browser polls and sees the analysis appear.
Architecture
Notice the presigned URLs. The clone tarball gets a ten-minute pass — the agent downloads it once, and the link expires. Video exports get a seven-day pass, so you can share with your team, but it's still time-limited. No permanent public access, no credentials baked into the URL. It's like handing someone a temporary building pass that self-destructs.
Architecture
The player uses two layers. The canvas is like an overhead projector — you draw animated text boxes and effects on transparent sheets, and the browser composites them at sixty frames per second. The DOM layer sits on top with real HTML: syntax-highlighted code blocks, body text, and native selection. Together they let you mix snappy animations with accessibility and detail.
Architecture
Lenzon talks to a lot of services. Anthropic provides the two agents — Managed Agents for code analysis, and the Messages API for script generation. AWS handles the heavy lifting: S3 for storage, SQS for job queues, and Fargate for the workers. GitHub provides OAuth for private repos and webhooks for pull request explainers. Google TTS generates the narration audio. And Postgres on Vercel stores all the durable state — analyses, scripts, users, jobs.
Community
Let's check the community pulse. The repo is actively maintained — the last commit was today, and there's been one commit in the past thirty days. Rick Gonzalez is the sole contributor so far, with two branches and no tags. It's a tight-knit team at the moment, but the activity signal shows this project is very much alive.
PlainEnglish
To recap: Lenzon is a two-agent pipeline backed by Fargate workers. Agent One analyzes the code, Agent Two writes the presentation script, and the player renders it in your browser with narration and animations. You can watch it live or export to MP4. The whole system is designed for async execution, because deep analysis and video rendering can take anywhere from five to forty minutes.
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