raea and 67.js: two young render engines built for agents to drive, from React video to path-traced 3D

raea, in one paragraph. raea ('Render Anything Engine') from @shinyobjectz_ uses the same composition idea as Remotion: a React component draws a frame for a given moment, with useCurrentFrame and interpolate. The difference is under the hood. Instead of headless Chrome capturing pages, a Rust engine built on Bevy draws every frame on your GPU and encodes in hardware where it can. Per the README, a 90-frame 1080p test renders in about a second on an Apple Silicon Mac. The same file can play live as a game, render one PNG frame for an agent to inspect, or go through 'raea check', which flags clipped text, low contrast, unsafe areas, freezes and loudness before anyone watches. v0.1.0 shipped Nov 9, v0.1.1 (the first build with a desktop app for Mac, Windows and Linux) on Nov 11, and release candidates for 0.1.2 kept landing today. The repo passed 2,200 stars in under four weeks.

What makes it agent-shaped. The installer drops raea's skills into ~/.claude/skills, and there's a Claude Code plugin, so the agent learns how to write, render and check compositions on its own. The scene stays queryable as data, so the loop is render a frame, look, fix, re-render. The author also lists beat detection that cuts a music video to a track's drops ('raea song'), Tone.js-based scores written as TypeScript, export to CapCut projects and transparent overlays, React Three Fiber scenes rendered straight to video, and typed scripting for Blender and Godot. Those are the author's claims from launch-week posts; treat each as a feature to verify, not a guarantee.

An early head-to-head. ARCVORA rendered the same 33-second short (footage, captions, two sound layers) in raea and HyperFrames on an Apple M3. In their smaller 20-second test, the median of three runs was about 12 s in raea versus 24 s in HyperFrames, and 16.5 s when raea read the existing HyperFrames HTML instead of a native rebuild. Frames matched closely, but bitrates differed (about 3.5 vs 4.3 Mbps at the same target), and raea logged a caption styling warning. Their conclusion: keep editing in HyperFrames, try raea for the export, and still watch the file before you publish. That's one creator's test on one machine.

Caveats for raea. It's labelled young, with rough edges and gaps in the docs, and Windows is the least tested build. The licence is FSL-1.1-ALv2, which is source-available rather than open source: you can use and modify it, but not to build a competing product, and each version converts to Apache 2.0 after two years. Read it before you put raea inside a product you sell.

67.js, the 3D side. codepawl's 67.js is an MIT 3D engine aimed at agents first. A scene is plain data (geometry, a matrix and a material per part), and an MCP server with about two dozen tools lets an agent create and edit the scene, keep checkpoints and roll back, get PNG previews, and submit renders for stills or MP4. Glaze is the real-time WebGL2 rasterizer; Cook is a path tracer on CPU, WebGL2 or Vulkan for finished stills. The project's own benchmark table puts Cook's native backend at roughly 0.7 to 1.3 s for 256 samples on its six test scenes versus 3.4 to 8.5 s for Cycles with OptiX, with Cycles still slightly cleaner by its FLIP error metric. That's the maintainers' benchmark. v0.19.0 (Nov 11) added multi-scene MCP sessions and leaner tool responses so agents spend fewer tokens.

Where these fit. Both sit next to the code-built film wave we've been tracking: Claude Fable 5.2 driving Blender (Kevin Ngo posted another one today, an '80s music video animated in Python and rendered in Blender), ESCAPEMENT and Cinematic Skill. raea is the candidate if you want React-style motion graphics without a browser render farm. 67.js is the candidate for agent-built 3D previs and product shots when Blender feels heavy. Neither replaces a finishing tool yet.

Signals: raea has community and creator posts (including a 58-like @vibelancer thread and a YouTube comparison) but no GitHub Trending appearance and no tracked curator pick. 67.js got a tracked curator post from @RoundtableSpace today (about 40k impressions), but no trending appearance. Neither is HOT by our rule.