GPT 6 Astra + After Effects = INSANE Video Editing

Published
Sep 17, 2026
Duration
15:19
Click to load the YouTube player

Record the workflow where it actually runs, then use After Effects to make the important parts easier to follow. An underline can identify a command as the narration reaches it. A close view can reveal the result of a version check. The terminal output remains real footage, while the explanatory elements stay editable.

This is the most useful application in Ron’s Astra and Higgsfield experiments. His team uses different machines, models and agent harnesses; moving every working setup to a filming-room computer can take longer than explaining it. Capturing the original machine avoids that reconstruction. News segments and short visual effects can use the same editing tools, with different source material and review.

Before you start

Have After Effects installed on a supported computer, the Higgsfield Adobe plugin, and an agent connection capable of reaching it. Astra is the model used in the source; Codex is the agent interface, After Effects is the editing application, and Higgsfield provides the connection. Installing a panel does not by itself prove the agent can control your open project.

The current Higgsfield integration guide, checked October 28, 2026, supports After Effects 2024 or newer. Adobe access and generation credits are separate from the plugin installer. Ron mentions a seven-day Adobe trial and the team’s return to Creative Cloud Pro, but check your own account’s terms before relying on that offer. Photoshop and Premiere Pro are related supported applications; their workflows are not demonstrated here.

Prepare a copy of your footage, its narration or transcript, and the reference material the effect depends on. For a software tutorial, use a demonstration environment and remove secrets or unrelated account information before recording. For a creative effect, collect the source clip and any assets you are entitled to use. An agent finding a downloadable project does not establish permission to republish every asset it contains.

Choose a short first deliverable. A twenty-second explanation or a six-second effect is enough to discover whether the connection, source material and editing plan work together.

Install the panel, then verify the agent connection

Follow the download for your platform on the official After Effects plugin page. On macOS, the documented route is to open the downloaded disk image, move Higgsfield to Applications and run its installer. On Windows, Higgsfield’s instructions use the ZXP Installer and the downloaded .zxp package. Quit Adobe applications fully before installation, then reopen After Effects and select Window → Extensions → Higgsfield. These steps come from the provider’s installation instructions.

For agent control, the product page distinguishes the Bridge connection from generating a clip in the panel. It lists https://bridge.higgsfield.ai/mcp for the agent bridge and links the ChatGPT plugin route. Use the setup instructions for the supported client you actually have. The recording uses Codex; use the current setup instructions for your client version rather than treating the recorded panel installation as a complete connection guide. Source: setup tour, 3:06.

Before handing over a long edit, ask the connected agent to identify the open composition and summarize its existing layers without changing them. Treat that as a proposed connection check: a response grounded in your current project is more useful than a generic explanation of After Effects. Then work on a copy and request one small, visible change. Confirm it appears in the intended composition and remains editable.

Editable work is the reason to use this route. Ron’s alternative generated fire clip obscured his face and got the spoken line wrong. Regenerating a whole clip could cost more credits and still change unrelated details. A composition lets you request a smaller flame or move a highlight without treating the entire shot as a new image-generation problem. It still needs review.

Capture genuine screen evidence

For the tutorial exercise, pick a workflow that already works on its own machine. Record its actual inputs and outputs, then keep the unedited capture as the source. If you need a clean installation demonstration, run it in a disposable environment rather than altering the production setup merely to make the screen look tidy.

In the source example, Astra uses a separate sandbox on Ron’s VPS, consults official Hermes documentation and records real command execution. The dependency output is therefore evidence of the commands running, not terminal text animated to resemble a successful install. Source: tutorial footage, 4:05.

Ask for a shot list tied to the narration. A useful proposed brief is:

Use the supplied screen recording as the source of all terminal output.
Match each explanation to the relevant moment in that recording.
Add editable highlights and short labels without replacing the output.
Show the command, its execution and the result needed to verify the step.
Flag any instruction that has no matching evidence in the capture.
Produce a short test segment before editing the whole recording.

This is an editorial template, not the exact prompt from Ron’s session. The expected result is a small segment whose command text and output can be checked against the raw recording. If the narration describes a result that never appears, fix the narration or capture the missing step. Do not ask the editor to fabricate a plausible success screen.

Add motion only where it explains the task

Identify what a beginner needs to notice at each point. In Ron’s demonstration, an underline follows the shell-reload command when he explains it, followed by the version check. Time the emphasis to the spoken explanation so the viewer can follow the step.

After Effects project showing a Verify your installation composition above a timeline of editable layers
Actual After Effects project at 6:40. The version-check footage sits inside an editable composition, with the timing and separate elements visible below. Inspect the underlying recording when checking the command output. Open the image for a full-size view.

Review the test at the size your audience will see. If the terminal text is unreadable, crop or reframe the useful area rather than adding more labels around an unreadable full desktop. Leave enough context to show what application and step the viewer is seeing. Watch with the narration: a correct highlight arriving too late can direct attention to the wrong line.

Keep the original screen capture, explanatory elements and narration identifiable in the project. Ask the agent to name the main composition, the captured footage and the added highlights so a later editor can adjust them. The recording demonstrates this general use of editable visuals, but does not provide a finished unattended pipeline or measured publishing-speed improvement.

Build a storyboard before a news edit

For a news segment, begin with the source article and the claims you intend to explain. Ask for a script, then a scene plan showing which source supports each claim and what will appear on screen. Decide where real screenshots are needed and where a clearly explanatory animation is appropriate.

Ron’s example concerns Nous Research using Hermes to refactor its codebase. The sample narration describes 36 work areas, 1,393 dispatched subagents and a peak of 218 active workers. Those figures belong to the news story being illustrated; they are not the number of agents used to edit the video. Source: news example, 7:04.

The plan aimed at a three-minute video and contained 27 scenes. The visible planning message refers to a 3:22 recording, so use your actual narration duration rather than forcing a nominal length. Only a segment of the intended production was shown as a finished sample.

Agent storyboard proposal describing 27 scenes, motion sketches and a short production test before the full film
Actual planning screen at 9:15. The message proposes a test from 0:52 to 1:12 before producing the whole film. Use that kind of small review point to judge whether the motion supports the narration. Open the image for a full-size view.

A scene table can contain the spoken sentence, source, visual, movement and duration. Ask the agent to describe the movement in ordinary language: what enters, what changes and what the viewer should understand. Preview the most demanding scene before approving the whole sequence.

Ron prefers the motion, zooms and transitions to the team’s previous static slide treatments. That is a production judgment, not measured audience retention. You can make the same decision by watching whether a scene clarifies the idea or merely keeps the screen busy.

Choose the right representation for a cutaway

An architectural cutaway needs information about the building’s interior as well as its exterior. Collect both before asking an agent to imitate a complex camera move. If the references do not establish a room’s geometry, an attractive animation may still invent the space.

The source experiment uses Villa Savoye after Astra looks for a well-documented building. It attempts a dollhouse-style view inspired by the White House sequence in The Residence. The moving view and glowing emphasis communicate the intention, but the result falls short of the reference; a research image becomes conspicuous near the end. Source: architectural experiment, 9:44.

If a shot needs a camera to move around believable interior geometry, decide whether to construct that geometry in a 3D tool before compositing. Astra proposed Blender alongside After Effects for a more photorealistic result. That was a proposed next approach, not a completed improvement demonstrated in this source. The related Blender workflow guide develops planning and scene construction further.

For an explanatory diagram, a simpler representation may be sufficient. Label it accordingly and judge whether it explains the building rather than pretending it is a faithful filmed interior. Do not spend the entire edit polishing an approach that lacks the information needed for the shot.

Troubleshoot a fire effect against the full reference

Use a short test and name the visible defect. Ron’s first fire attempt had a clear cutoff edge and lacked the reflected glow he wanted on his face. A reshoot with a more neutral background and a clearer palm helped the input but did not resolve the whole effect.

A useful correction request identifies the frame or interval, the defect and the reference behavior: “The flame is cut off at this boundary; inspect the element’s bounds and compositing. The reference includes light on the face, while this shot does not.” Treat those as questions to investigate, rather than claiming to know which layer is responsible without inspecting the project.

Original palm footage beside a revised After Effects fire composite from the same shot
Actual source comparison at 14:10. Compare the flame's placement and its relationship to the hand and face across the shot. This is a composited result, not a new effect created for this article. Open the image for a full-size view.

Verify the reference coverage before requesting another attempt. Ron discovered that Astra had not followed the entire roughly forty-minute tutorial. After reading its full transcript, the agent identified omitted steps and produced a better test. Reading a transcript is useful, but does not by itself prove that the agent inspected every visual operation. Ask it to identify which sections it used, what it could not see and which steps are still missing from the project.

The agent also located an ActionVFX project ZIP containing the fire elements, transparency information and layers. A six-second effect involved multiple compositions and elements. The source does not supply a complete recipe or licensing review for that external project, so this guide does not present a fabricated recreation. Keep the tutorial, its supporting materials and your own test side by side while checking the steps.

If the Higgsfield panel is missing, fully quit the Adobe apps, rerun the installer and check Window → Extensions on a supported version, as the provider recommends. If the panel appears but the agent cannot identify the project, check the bridge connection separately. If the connection works but the effect is poor, review the source coverage and the visual defect before assuming another complete render will solve it.

Deliver the editable project, source files and a rendered preview together. State what is still wrong or unverified. The agent workflow lesson covers the broader review process; for these edits, the essential handoff is a result another person can inspect and change without reconstructing the whole session.