Show HN: Lazycow Studio – turns footage you never edited into reels, locally Kensaurus released Lazycow Studio, a free, Apache-2.0 open-source tool that catalogs a user's unedited photos and videos, cuts short vertical reels on the beat of free music, and builds long YouTube videos with maps and chapters, all running locally on the user's own computer. The studio exposes an MCP server, an OpenAPI 3.1 HTTP API and an npm package so AI agents in Claude Desktop, Cursor, VS Code or Claude Code can make drafts and publish approved reels, but no agent has an approve tool — nothing is booked or posted until a person presses Approve. Tagging and search run on OpenCLIP on the user's own processor, so the main flow needs no API key or LLM, and cloud AI runs only when a key is added. You shot it. Lazycow edits it. The footage you never edited becomes reels and trip films. You only press Approve . Lazycow Studio finds the right clips in your photos and videos, cuts short vertical reels on the beat of free music, and builds long YouTube videos in parts, with maps and chapters. Then it books the posts. It runs on your own computer. Lazycow Studio is made by kensaurus https://kensaur.us . It is free and open source under Apache-2.0. - Your footage stays on your computer. Tagging and search run on your own processor. The studio only reads your files. Nothing leaves your computer unless you connect a network or add a key for a paid AI tool. - A person approves every post. Nothing is booked or posted until you press Approve . AI agents can make drafts and post approved reels. They cannot approve. - Your AI agent can drive it. An MCP server, an HTTP API OpenAPI https://github.com/kensaurus/lazycow-studio/blob/main/docs/openapi.yaml and an npm package. One click connects Claude Desktop, Cursor or VS Code; one line, Claude Code. Who it is for: a small hotel, guesthouse, café or shop, or a creator, with a folder of footage and no time to edit it. You do not need to code: download, unzip, double-click. It posts to YouTube, Facebook and Bluesky, and fills in the schedulers of X, TikTok, LinkedIn, Google Maps and LINE in your own Chrome. Download https://github.com/kensaurus/lazycow-studio/releases/latest · Quick start quick-start · Use it from your AI tool use-it-from-your-ai-tool · User guide https://github.com/kensaurus/lazycow-studio/blob/main/docs/user-guide.md · Support Lazycow support-lazycow · 日本語 https://github.com/kensaurus/lazycow-studio/blob/main/README.ja.md Review, Approve, booked. Recorded in our own studio, which makes the reels for Tsumagoi Work&Camp in Gunma everyone on camera agreed . ▶ Watch the 40-second demo https://github.com/kensaurus/lazycow-studio/blob/main/docs/media/lazycow-demo.mp4 : its footage, reels being made, a person reviewing, the posting week, results and the workflow. Start the studio first. Then add it to your tool in one click, or one line in Claude Code: claude mcp add lazycow -- npx -y lazycow mcp - Claude Desktop: open the downloaded lazycow.mcpb to install it as an extension. If the double-click setup installed the studio, leave its settings empty: it finds the port and token in the studio's .env . Otherwise, pick the studio folder. - Cursor, VS Code, Claude Code and any other MCP client run npx -y lazycow mcp { "mcpServers": { "lazycow": { "command": "npx", "args": "-y", "lazycow", "mcp" } } } , which needs Node 20 or newer on your PATH. The double-click setup keeps its own Node out of your PATH, so use the lines in the studio's Settings › Keys & AI › Use with Claude or Cursor instead: they have your paths filled in. - No MCP? The same studio over HTTP: OpenAPI 3.1 https://github.com/kensaurus/lazycow-studio/blob/main/docs/openapi.yaml , or npx lazycow api GET /api/overview . The agent can check the studio, make reels, plan posts and publish approved reels. It has no approve tool. Every tool: docs/mcp.md https://github.com/kensaurus/lazycow-studio/blob/main/docs/mcp.md . Self-host with Docker. From a clone, put an API token of 24 characters or more in .env the studio will not start without one , then docker compose up -d runs it in a container image ghcr.io/kensaurus/lazycow-studio . Footage folder, port and updates: docs/self-host.md https://github.com/kensaurus/lazycow-studio/blob/main/docs/self-host.md . The studio has three parts. A Node server server/review.mjs , listening on 127.0.0.1:4317 only, unless you turn on server mode https://github.com/kensaurus/lazycow-studio/blob/main/docs/self-host.md serves the page and an HTTP API. A Python engine python -m studio … catalogs, tags and picks clips. Remotion and ffmpeg render the reels. Tagging and search use OpenCLIP on your own processor, so the main flow needs no key and no LLM. Cloud AI runs only when you add a key: on OpenRouter, a reviewer and suggested lines; on fal.ai, tools such as slow motion, music and voice. The writing jobs and the picture questions can run on your own model instead: any OpenAI-compatible server, local Ollama, LM Studio, vLLM, llama.cpp or hosted Settings › Keys & AI › Your own AI model, or STUDIO LLM BASE URL in .env . The agent you connect over MCP can use any model. php flowchart LR UI "Studio page