Shugar86/vids-studio

English · Русский
Watch the demo · Install · Series · Use cases · How it works · Guide
## Your video, still in the editor
Vids Studio connects Codex or Claude Code to the Google Vids document you choose. Describe the audience, idea and desired result. The agent uses a creative skill to plan the video, observes the editor, makes changes and checks what happened. You keep an editable Vids project that you can continue working on yourself.
The skill provides the production method; the connector gives the agent eyes and hands inside the attached tab. Together they support work on story, shots, voice, captions, pacing and sound—using the features available in your Vids account. The bridge uses no system mouse, keyboard or clipboard, so it does not take over your desktop.
## Several videos, one monitor
The 0.4 preview supports several explicitly attached documents per client, a private assignment for each chat, adaptive command limits and a shared local monitor for Codex and Claude. Start the monitor with bun run monitor; pause new commands for one video or the whole group without using the system mouse or keyboard. This does not pause the model or a Google generation already in progress. Export runners survive their MCP client's exit, with separately bounded local MP4 verification.
Connect 5–10 chats and understand the limits →
Monitor preview · synthetic examples
The archives below include these changes. Ten parallel codex exec processes passed isolated-browser acceptance; live multi-film editing in Google Vids remains a separate check. What was tested and on which build.
Source builds from main also give both profiles the same montage and media tools: scenes and transitions, PNG layers, website capture, SRT, blind ASR and frame-cut review. These additions are not yet in the published v0.4.0 ZIP files; see the changelog.
## From one video to a series
New on main: a series kit and an episode card checker. Define shared formats, worlds and limits, then give every episode its own event: a character's desire, obstacle, turn and final image. Codex and Claude follow the same method.
| Prepare | What it gives you |
| A series kit | Format rules, visual worlds, duration and generation budgets. Open the template → |
| An episode card | On-screen action, shots, speech, sound and a sample to prove first. Explore the example → |
| A check before generation | Timing errors, budget overruns, repetition and the risk of turning a story into a slideshow. Read the method → |
Situation → card → keyframes → sample → Vids assembly → final critique. Every stage produces something to review; generation and revision rounds have explicit budgets. The card checker runs locally and generates no media.
Try the example without connecting to Google
From the source repository root:
sh
python3 -I skill/google-vids/scripts/seriescard.py check \
skill/google-vids/assets/series-kit/example.card.json \
--kit skill/google-vids/assets/series-kit --json
The report contains errors, warnings and a plan-level risk score. Exit code 1 means card errors; 2 means an input-reading problem. Warnings need an editorial decision. A good plan score does not establish video quality.