I asked Claude Opus 5.5 to design and carry through a short film. The result, which I call I Am Here in English, runs for 4 minutes and 57 seconds. I installed MiniMax, Grok, Codex and other CLIs locally, then let Opus call the tools to bring the script, visuals and sound together.
I wanted to see whether it could carry the whole job forward. Once a script exists, someone still has to break it into shots, choose how to generate the footage, arrange the voices and music, and decide what to change when something goes wrong. I handed those decisions to Opus. Here is the film.
Install the tools and give the agent a way to use them
This approach needs an agent environment that can run terminal commands and read and write local files. Opus handles the brief, script, shot design and task planning. Grok CLI generates video material; MiniMax's speech and music tools handle voices and the score. Codex CLI can also be connected for scripting and engineering work.
A CLI turns those capabilities into executable commands. The agent reads the tool instructions, passes a prompt and parameters, receives a task status or output file, and chooses the next step. The Grok Imagine documentation covers image and video generation. The MiniMax CLI and its companion skill describe tools such as speech synthesis. Check the help for your installed version to see which subcommands are actually available.
Installation is only the first step. Each tool needs its login or API configuration, the asset folder must be writable, and Opus needs to know the available tools, their limits and their output locations. That gives it a way to move from a plan to generating assets, organizing files and checking results. The tools and file management are local; generating visuals and audio through cloud models still requires a connection, an account and the relevant quota.
I gave it a filmmaking brief
The request was ambitious: 3 to 5 minutes, a meaningful script, large-scale scenes and deliberate cinematography, with music, effects, voices and character continuity considered together. I even asked for something that could win at Cannes. That was the creative target; whether the film moves an audience has to be judged from the film itself.
I also set a few working boundaries. It could choose the visual style. Important script and shot decisions could use a stronger model or a higher effort level. It could choose how to organize sub-agents, while keeping token use reasonable. Anything unclear could be discussed before starting. Below is an English translation of my full prompt; the Chinese version of this article preserves the original wording.
Read the full prompt in English
Next, design a script and make a short film of about 3 to 5 minutes. I want something that could win at Cannes: epic in scale, with grand scenes, an excellent script and deep meaning, fully demonstrating Opus 5.5's abilities in screenwriting, shot design and directing, with rich cinematic language.
It should amaze people. The opening could be Hollywood-level, with things like background sound and changing titles. Early on, it could show that the film was made by Opus 5.5, Grok CLI for video, and MiniMax CLI for voice and background music. They do not all have to appear at once; integrating the credits into suitable shots or interfaces could feel more refined.
If anything is unclear, discuss it with me before starting. To bring the video into reality, consider whether Opus 5.5 high should handle execution, and whether important work such as the script and shots should use Fable or Opus 5.5 max. You can decide how to arrange these sub-agents. I want reasonable token use while preserving quality, because we want this film to win awards.
Consider the background score, music, effects, voice consistency, and consistency of characters and settings. It does not have to be animation. Live action, 3D, animation, a new art style, or something abstract are all fine. You are free to choose.
If anything is unclear, confirm it with me before you begin.
The prompt brings the goal, creative freedom and constraints together. Words like epic and cinematic still leave a tool with little to generate. The intended meaning has to become scenes, actions, shots and sound before the production tools can do useful work.
Organize a several-minute film around shots
Problems tend to show up when footage is assembled. A character looking right in one shot does not ensure continuity in the next. Several beautiful clips do not automatically tell a coherent story. A useful approach is to settle the beginning, turning point and ending, then define each shot's subject, action, framing, camera movement and narrative purpose.
The shot plan also needs durations and sound cues. Is there dialogue? When does the ambient sound enter? Does the music continue, or should the scene have a moment of quiet? Decide those alongside the visuals. Adding sound after all the footage is generated can leave dialogue too long or transitions too short, forcing changes across the timeline.
Video tasks may also require waiting for results. The coordinator should keep track of shot identifiers, task status, asset locations and usable versions, then check each result when it arrives. If one segment needs changing, revise that segment rather than regenerate the whole film. The shot plan is also the task list and the basis for editing.
Give characters and voices shared constraints
Continuity across shots benefits from reusable character descriptions, setting descriptions and reference assets. Define clothing, appearance, palette, lighting, time and spatial relationships as clearly as possible. Where a tool supports reference images, reuse the same references. These constraints can reduce drift, but each generated segment still needs inspection.
The same applies to voices. Keep a character's voice and basic parameters fixed, then adjust delivery speed and pauses for the emotion. Music and ambient sound need to leave room for speech, and action effects need to align with the picture. Having enough assets means the generation stage produced files; intelligible dialogue, natural cuts and emotional continuity have to be judged on the complete timeline.
Spend the budget on decisions that affect the whole film
My references to high, max and Fable asked the agent to think about allocating the work. Higher effort or a stronger model can be reserved for story structure, key shots and reviewing the full edit. Asset organization, status checks and batch processing can follow clear rules once the decisions are settled. A higher setting alone does not guarantee better-looking shots.
Token use is also only part of the budget. Video generation, audio generation and retries have their own costs. Generating many shots before the story is settled risks throwing those assets away when the plot changes. Converging on a plan before generating and reviewing material makes rework easier to control.
The film is embedded above, so the result is there to judge. What makes this approach worth pursuing for me is bringing the script, shots, sound and tool execution into one coordinated job. Opus can move those stages forward; the final step is still watching the whole film and deciding which images belong and which parts need another pass.



