I Made Motion Graphics With Codex — No After Effects Needed

Editorial context

Codex can direct a code-based motion-graphics workflow without asking you to hand-edit After Effects keyframes. The useful part is not a magic phrase. It is the contract around the prompt: duration, resolution, exact text, timed scenes, deterministic animation, render commands and a human pixel-level review.

Verdict: excellent for repeatable graphics, not a full post-production replacement

Use Codex with HyperFrames for structured title cards, sponsor bumpers, animated charts, interface explainers and templated product sequences. It is a poor substitute for an editor when the job depends on footage selection, detailed audio work, colour grading or frame-by-frame compositing.

You are replacing some manual timeline work with code, constraints and review—not removing creative judgment. The source remains editable as HTML, CSS and JavaScript, while HyperFrames previews and renders it as video.

Best for: YouTubers, educators, product marketers and small creative teams who want versioned, reusable motion systems and are willing to inspect every render. Skip it: if you expect one-click production or need a fast tactile finishing workflow across lots of live-action footage.

Useful chapters

1. 00:00 — What “without After Effects” actually means
2. 02:00 — Sponsored Agent Opus segment
3. 03:33 — The Codex workflow begins
4. 04:21 — Find and install HyperFrames
5. 04:43 — The first motion-graphics prompt
6. 05:31 — Generate and inspect the first result
7. 06:39 — Revise with measurable natural-language changes
8. 08:17 — Create and compare multiple variants

What Curtis tested versus what the sources say

Visible in Curtis’s recorded test

• Curtis opened Codex on macOS, chose HyperFrames and submitted a 10-second brief titled “AI Tools Are Becoming Creative Teams.”
• The prompt specified three cards—Script, Design and Video—plus connecting lines, a camera push-in, a dark visual treatment and an MP4 output.
• He opened the first MP4, identified overlap, small text and an unwanted 00:10 marker, then requested larger text, stronger glow, slower camera movement, a 1.5-second end hold and removal of the marker.
• He reviewed the rerender and showed a folder he described as containing 25 variants.

Not independently established

The original project, lockfile, HyperFrames version, model identity, run logs, machine specification, MP4 metadata and verified inventory of all 25 outputs were not preserved. The footage therefore does not prove batch reliability, generation speed, cost savings or 25 simultaneous successful renders. The download below is a new July 28 reproduction contract—not the missing filmed project.

Current sourced facts

OpenAI’s current documentation establishes Codex access, plans, permissions and remote-control boundaries. HyperFrames’ current documentation establishes its code-based composition model, CLI commands, Studio timeline, Docker render path and Apache-2.0 licence. Those sources describe the products today; they do not retroactively verify the filmed run.

Exact reproducible workflow

1. Install Node.js 22 or later, FFmpeg/FFprobe and npm/npx. Install Docker if you want the deterministic render route.
2. Install the current HyperFrames agent skills with npx skills add heygen-com/hyperframes.
3. For this dated recipe, pin HyperFrames CLI 0.7.80.
4. Open a fresh Codex task in an empty project folder and provide the download’s settings/project-spec.json and prompts/01-build-prompt.md.
5. Require a 10-second, 1920×1080, 30 fps composition with four timed beats, no random or time-dependent animation, no visible timer and a static final hold from 8.5 to 10 seconds.
6. Run HyperFrames doctor, lint and check. Preview in Studio and inspect the exact title, card labels, connecting lines, camera move, text fit, contrast and final hold.
7. Submit the bounded revision prompt. It specifies measurable changes instead of “make it better.”
8. Run npx hyperframes@0.7.80 check . --strict --snapshots and review the rendered snapshots.
9. Render with npx hyperframes@0.7.80 render --docker --output renders/creative-teams-v2.mp4.
10. Capture FFprobe metadata and SHA-256 hashes with the included script, then complete the visual QA checklist before importing the MP4 into the main edit.

Copyable build prompt

Using HyperFrames, create a 10-second 1920x1080 motion graphic at 30 fps titled:
“AI Tools Are Becoming Creative Teams”

Beat 1 (0.0–2.0s): introduce the exact headline with high YouTube readability.
Beat 2 (2.0–5.0s): reveal three cards labelled Script, Design and Video.
Beat 3 (5.0–8.5s): connect the cards with restrained glowing lines and a smooth camera push-in.
Beat 4 (8.5–10.0s): hold the final composition completely static.

Use deterministic animation only. Do not add logos, a fake player, a visible timer or extra claims.
Run doctor, lint and strict snapshot checks before rendering an MP4. Report the output path and any failed check.

Copyable revision prompt

Revise only the existing composition:
- increase headline and card-label size until readable at a 640px-wide preview;
- remove every overlap and all clipped text;
- add a restrained soft glow behind each card without reducing contrast;
- slow the camera push-in by 25%;
- remove any timer or player-like icon;
- keep the final frame unchanged from 8.5s through 10.0s.

Rerun strict snapshots, render a new versioned MP4, and preserve the previous render.

What changed after filming

• HyperFrames CLI is now 0.7.80, checked July 28, 2026. The filmed version was not preserved.
• The current QA path is clearer: HyperFrames now documents doctor, lint, check, snapshots, inspection and Docker rendering. The video concentrated on prompt, preview and MP4 output.
• “No timeline” needs qualification: Curtis did not manually manipulate an After Effects-style timeline. Current HyperFrames Studio documentation does include a visual timeline, seeking, frame stepping and edits that can persist to HTML.
• The reproducible install route is command-line based: the current HeyGen setup guide recommends npx skills add heygen-com/hyperframes. Graphical plugin-directory availability can vary by Codex surface and rollout.
• Mobile is a remote control: OpenAI documents controlling a connected Mac or Windows host from mobile. The host supplies files, tools and compute; plugins are not directly available on mobile.

Current pricing and access — checked July 28, 2026

• Codex Free: $0/month for quick coding tasks.
• Codex Go: $8/month for lightweight coding.
• Codex Plus: $20/month, including web, CLI, IDE extension and iOS access subject to current limits.
• Codex Pro: from $100/month with higher usage limits.
• Business: $20/user/month billed annually or $25 monthly, with a two-user minimum.
• Enterprise and Edu: contact sales. API-key use is metered separately.
• HyperFrames: Apache-2.0 open source, with no HyperFrames seat fee or per-render licence charge. Hardware, storage, paid assets and third-party services can still cost money.

Prices, limits, models, regional availability and workspace controls can change. This section records what was checked, not a permanent price promise.

Download the Codex + HyperFrames motion-graphics pack

The pack includes the exact build and revision prompts, a machine-readable 1920×1080/30 fps project specification, ten bounded variation briefs, version-pinned workflow, evidence ledger, render-and-capture script and human release checklist.

Download the free motion-graphics pack

Official sources

• OpenAI Codex pricing
• OpenAI plugin documentation
• OpenAI remote connections
• HeyGen HyperFrames setup guide
• HyperFrames CLI documentation
• HyperFrames rendering guide
• HyperFrames Studio documentation
• HyperFrames source and licence

Related links

• Codex product record
• Introducing Codex launch record
• OpenAI company record

Get The Kingy Brief every Friday.