The Bridge 2.0 · AI Filmmaking with Codex, Runway and DaVinci Resolve

Quick Summary

• Tim Simmons of Theoretically Media demonstrates this workflow. Runway sponsored the remake of The Bridge, as he discloses. This article separates his project observations from official documentation and our recommendations.
• The original version was published in March 2025 and the remake in September 2026. Tim estimates about a week for the first film and about a day and a half for the new version, including cleanup. These are timings from his project, not a forecast for every production.
• Codex with GPT-6 Astra coordinated script, plan list, references and generation requests by Runway MCP. Midjourney provided character and setting concepts; Seedance 2.5 generated plans and character rotations on Runway.
• The studio skill and a local HTML dashboard structured the project around briefs, cast, locations, storyboards, prompts, shot versions and session notes. Speaking with the agent sped up direction because Tim's preferences were already documented.
• The attempt to let the agent put together the first timeline in Premiere was slow, which is why Tim made this cut. In Resolve, the agent helped with color, small adjustments, Fusion titles and the mix of dialogue, music and environment.
• Runway Ruby is presented as an option to convert SDR to HDR and work in greater depth formats. This does not automatically recover information that never existed in the SDR image. The creator says he found ProRes for Seedance 2.5, but the official help consulted documents ProRes profiles for Gen-4.5 and Aleph 2.0; Please confirm availability in your account before planning your pipeline.

Credit, sponsorship and short answer

Tim Simmons, from Theoretically Media channel, made both versions of The Bridge and explains his workflow in the video embedded above. Runway sponsored the remake, as Tim states at the beginning and mentions again during the demo. Comparison and quality impressions belong to the creator; This article organizes the provided transcript and verifies product capabilities against official sources.

Tim announces in the video the code THEO25 for 25% off for new Runway subscribers. It is an offer communicated by the creator, not a price condition verified by us. Confirm validity, eligibility and final price directly on Runway before joining.

The new film didn't come out of a prompt box nor was it entirely edited by an agent. Tim says about a day for the main part and another half day for cleaning, compared to about a week in initial production. GPT-6 Astra on Codex handled a lot of planning and execution with Runway; Tim chose plans, reviewed results and assembled the first cut by hand. He then directed the finishing in DaVinci Resolve by voice, without using the mouse at this stage, according to his report.

It's an interesting case study because it shows the real division of labor. AI speeds up repeatable tasks when it knows the rules of the movie. The director remains responsible for rhythm, selection, continuity, rights, color, sound and the decision to call the work finished.

See the films: 2026 remake and 2025 original

The remake, The Most Epic AI Short Film You'll See Today, was published on September 14, 2026. Start with it if you want to judge the final piece before going behind the scenes. The following video is the original The Bridge, published on March 24, 2025 and created with Veo-2, according to its title. Both are works by Tim Simmons and Theoretically Media.

The comparison in the same scene between the guardian and the barbarian illustrates improvements in voice, interpretation and chaining of plans. It is not an isolated test of models: tools, author experience, direction and production time have also changed. Use comparison to observe decisions, not as proof that any current model automatically produces a better film.

The pipeline, without mixing tools

The project structure was a studio skill with briefs and folders per phase. From there, Tim asked Astra at Codex to review the old film, reconstruct the script and shot list and prepare generation requests. Created character and location references in Midjourney. Then used Runway MCP to route generations, including Seedance 2.5, and organized outputs for review. He made the first cut in Premiere, transferred the timeline via XML to DaVinci Resolve and guided the finishing there.

MCP stands for Model Context Protocol. In this case, it is the connection that allows the agent to call Runway's tools within a conversation, without making the generations local or free. Runway informs that calls via MCP use account credits and that the cost varies depending on the model and settings. Access to Seedance 2.5 on Runway depends on a paid plan according to the model's official page.

To repeat the logic, and not just the list of tools, separate three responsibilities: the agent maintains context and prepares operations, the platforms create the assets and the person approves the narrative and the final result. A voice request can trigger a structured plan, but approval should not be implicit when there is cost or material from customers.

1. Codex, Runway MCP and the studio skill

Tim recommends the Codex desktop app and a Runway account. In the video, you say you asked the agent to turn on Runway MCP, but the actual flow includes logging in, authorizing the connector, and confirming that the tools appear. Follow the official Runway setup page, as menu names, plans and permissions change. Before generating, it asks the agent to identify the available model and present duration, resolution, references and expected cost.

Your Theoretically Studio Film skill isn't just a one-line instruction. Tim describes rules files and subfolders for references, brief, assets, tracking, story, visual, cast, locations, shots, stills and videos. The structure makes the project readable for both the agent and the director. The creator says that the skill and tutorial will be shared by the Theoretically News newsletter; We did not receive these files and do not reproduce the exact content of the skill here.

A small version to try needs just four things: a one-page brief, a numbered list of plans, folders for references and renders, and a status and version table. After testing two or three plans, he adds rules that solve real problems. There's no need to start with a full studio infrastructure.

2. Script, characters and 360-degree turnarounds

Astra analyzed the first draft of The Bridge to reconstruct the story and plan list. Tim created initial images of characters and settings in Midjourney. Before the final shots, the chosen video model was fed with character sheets to generate 360 ​​degree rotations. The practical objective was to observe the front, profile and back, and see where the appearance broke down.

Tim proposes a hypothesis: if the video model itself generates the character's back, perhaps this idea will be retained in future shots. He points out that it is speculation. There is no guarantee of persistent intergenerational internal memory; The verifiable gain is in having a set of references and testing visual consistency before committing credits to an entire sequence.

The Runway page confirms that Seedance 2.5 accepts text, image, video and audio references, up to the limits of the product, and allows plans with audio. This does not replace revision of silhouette, costume, direction of gaze, voice and geography of the scene. In a series of shots, approve a continuity sheet for each character and save the reference actually used in each generation.

3. The dashboard and session diary prevented losing the movie inside the folders

With the number of files growing, Tim created a local HTML dashboard pointed to the production folder. The panel brought together every plan and prompt, storyboards, references, locations, notes, scenes and sequences. This did not generate better images in and of itself. It made visible what had already been created, what was missing and which version belonged to which decision.

In a documents section, Astra wrote a summary after each session: work completed, changes, problems and next steps. The diary is not a magical model memory. It's a persistent record that a new session can read and that also helps Tim recover context when he himself forgets a choice.

For a small project, keep at least one record per shot: ID, narrative goal, model, prompt, references, duration, version, cost, status and approval notes. Use project-relative file paths and record asset provenance. Do not expose client data, sharing links or credentials in the dashboard.

4. Voice guidance: speak normally, generate with rules

Tim used the Codex voice mode to describe plans conversationally. The skill already contained prompting preferences, so Astra could transform an instruction like changing gaze weight or camera energy into a structured proposal. The director received the clip, approved or rejected it, and adjusted the direction.

The difference is not dismissing the prompt. It's removing from the director the task of repeating syntax, format and context in each shot. Before executing, it asks the agent to show goal, action, reference, framing, movement, sound and failure criteria. If a reference contradicts continuity, interrupt and correct it.

This workflow still involves waiting. Tim notes delays between preparing a request, sending it to Runway, receiving the result and archiving it. His total project time fell, but the pauses between actions felt longer. A status panel and short test generations help identify what can proceed in parallel without losing editorial control.

5. The agent failed as a first-time editor

Tim tried to let Astra work on the Premiere timeline via computer use. He found the process slow and intrusive: the agent occupied the screen and lost track when the interface changed. He ended up putting together the first version himself. This is the most important part of interpreting the video title: the agent participated in the entire production, but did not replace the human decision about pacing and shot selection.

During the project, Runway announced plugins for Premiere Pro and After Effects. The official page confirms generation and editing from the panel in these applications and consumption of account credits. Tim did not use them to assemble this piece; mentions them as a future possibility. Do not confuse this integration with an autonomous assembly demonstrated in the video.

A useful test is to give the agent a 20-second cutoff with verifiable rules, measure the time to an approved version, and compare with the editor. If correcting the result takes longer than editing, keep the manual assembly and delegate only conformity, organization, notes, proxies or other tasks with clear boundaries.

6. Resolve: color, small cuts, Fusion and audio

After the first montage in Premiere, Tim exported the timeline via XML and imported it into DaVinci Resolve. He asked the agent for a color pass over the output material, described in the video as Rec.709, and added Dehancer for a grain treatment. The agent made small trims and dissolves, created initial and final titles in Fusion and leveled three audio groups: dialogue, music and environment.

Blackmagic introduces Color, Fusion and Fairlight as areas of color, composition and audio integrated into Resolve. The unusual thing about the test is that Tim states that he did not touch the mouse during this phase. It is not a guarantee that any project can be completed like this. Always confirm scopes, contrast, consistency between shots, readability of titles, dialogue levels and final export on real devices.

The narrative also exposes agency costs: Tim estimates that he spent around 70% of his weekly quota using the top plan, including experiments and steps that he considers unnecessary. We do not convert this percentage into euros nor do we treat it as a typical cost. To budget, count generations, duration, resolution, corrections, review hours and agent usage in your own plan.

Ruby, ProRes and the limit of an SDR image

Tim points to Runway Ruby as a way to convert SDR clips into HDR formats with greater working latitude. Runway describes outputs as 16-bit EXR sequences and 10- or 12-bit ProRes or HEVC files. Conversion can redistribute tones and facilitate certain processing, but it does not transform an SDR MP4 into a RAW negative or recover details that were not captured or generated. Run a short test before converting the entire film.

In the video, Tim says he found a ProRes 422 HQ option associated with Seedance 2.5 and regrets not using it in the beginning. The current build documentation with Seedance 2.5 lists MP4 and MOV formats, without stating that MOV is ProRes. Specific ProRes/PNG export help documents this selection for Gen-4.5 in Tool Mode and Aleph 2.0 in Edit Studio on eligible plans. Surfaces and functionalities can evolve; confirm codec, profile, cost and final file in your account, rather than planning the entire chain based on this isolated observation.

If the delivery is SDR, you don't need an HDR step in principle. Decide color space, gamma, codec and monitoring for the destination of the film. What doesn't change is the need to check banding, compression blocks and gradation continuity before rendering the master.

How to test this method on a small film

Choose an original scene lasting 20 to 40 seconds, a maximum of two characters and a location. Write premise, conflict, ending, style, rules of continuity and rights of materials. Build a list of four to six shots with duration, sound and action. Approve cast and location references before animating. Take a short test of the character in movement and evaluate the front, profile, back, voice and costume.

Connect an agent to Runway MCP only after understanding permissions and credits. Use the agent to prepare a generation plan and request approval before each batch. Saves each result in a record with prompt, model, reference and version. Assemble the first sequence in the editor of your choice, compare it with the script and only automate finishing steps that you can inspect and reverse.

It closes with human review: narrative coherence, editing, color, audio, music licenses and assets, possible image authorizations and delivery format. The lesson of The Bridge 2.0 is not that one person stopped making films. It's just that a system of context and tools allowed a director to focus more time on the decisions that make the film work.

If you want to delve deeper into the controls, examples and limitations of the model used in the plans, JQ VISIONS also has a specific analysis of Seedance 2.5, linked to the sources. Read it as a technical complement, not as a substitute for the direction and editing demonstrated by Tim.