Your coding CLI runs the studio, and every frame gets checked

New

• Your coding CLI is the whole studio. 1VideoTool now starts from the coding CLI you already use — Claude Code, Codex, Devin, Gemini CLI, OpenCode, Grok and more. The first-run card finds the CLIs on your Mac, asks once for permission to let one build scenes and run Blender, and every picker defaults to it. Cloud generation (Gemini, Runway, fal) moves behind an Advanced generation switch in Settings, so nothing asks for a key unless you turn it on.

• Several videos at once. Director runs now work in their own productions side by side, and you can open, browse and edit other productions while they work — no more "a director run is working" when you switch.

• Videos that follow a design guide. Every directing agent now works from a built-in video design guide: one protagonist to follow, a clear structure that ends on its opening image, one look per film, real names and numbers, short on-screen text, transitions that grow out of the content and sound on every event. The agent writes its intent card, beat sheet and decisions into the video's plan, and the app checks them before anything renders.

• Every frame is checked. A lint runs on every rendered frame and catches overlapping or covered text, text off the safe area or too small to read on a phone, low contrast, text that moves or leaves before it can be read, missing glyphs, flicker and blank frames. Scenes with problems go back to the agent one at a time to be fixed, then a second model can review stills of the cut as a critic, citing the frames it looked at.

• Notes with every delivery. Next to each finished video you get a five-line summary and a NOTES file: facts the agent could not verify, stand-ins it used, what the checks found and the video's known weak spot. Placeholder text on screen stops the export until you approve it.

• New transitions and a protagonist. Scenes can dive into an element (portal), hand an object to the next scene, match-cut on a shape, dissolve through the style's own texture, cut on the beat, or morph one layout into the next. A protagonist — a cursor, token, card, prompt, window, number, an image or an Ink character — can carry through the whole video and collect what it gains along the way.

• Product demos show the verb. Screenshots sit in a window, phone or laptop frame that settles flat, and a cursor moves onto the control the line is about and clicks it (or a highlight rings it).

• Living 2D and 25 style packs. Ink characters breathe, blink and glance by default, speak narration with lip-sync and act on cue; animation keeps moving through the whole beat instead of stopping after the entrance. Pick from 25 style packs (cel, anime, paper cut-out, whiteboard, pixel, halftone, vox collage and more) plus three new ones — Riso print, Keynote glass and Cinematic essay — with Inter, Fraunces and JetBrains Mono bundled. Ink Studio keeps its work, remembers the conversation, builds characters from parts and critiques its own pictures.

• Sound that follows the picture. Pops, stamps, typing, draw-ons and transitions get their effects automatically, the music drops out before the reveal and the reveal hit is always the loudest, narration can J-cut into the next scene, and every video is mastered to its format's loudness (−14 LUFS for social and product videos, −16 for long-form) without clipping.

• For MCP clients. guide_get returns the design guide and the checks, run_get returns the run's intent, beat sheet, lint and review files, video_create takes a style, and an external CLI can act as the critic with review_packet_get and review_findings_submit.

• Fixes. Custom cubic-bezier easings followed the wrong curve; short videos were mastered 1–2 LU quiet with peaks over the ceiling; an Ink clip used in both a video and a picture slot failed the render.