The most quoted number from Astra's launch week was 99.9% on ARC-AGI-3, which turned out to be harness-dependent. The number worth quoting instead is 3,295, and you can watch where it came from.

Everything below is the original post. Play them.

A drawing of a steam train, rebuilt as 3,295 parts

The 3,295-object build@tomkrcha
Tom Krcha: "After few minutes it crafted 3,295 fully editable detailed objects with beautiful geometry."

The word doing the work is editable. Most 3D generation returns a single fused mesh: you can look at it, you cannot select the chimney or change a wheel diameter, and a modeller receiving it starts over. An object tree is a different asset class. It rigs, it exports, and it survives a second person opening the file.

It takes control of Blender

The second shift is easy to miss. Astra is not writing you a Blender tutorial. It drives the application.

Computer use, inside Blender@mreflow
Matt Wolfe: a humanoid wolf modelled in about eight minutes, then a 50-bone skeleton and a keyframed run cycle in about six, then into Unreal Engine as a playable character.

Four words and a reference image

The whole prompt@skirano
"Make this in Blender" with one image attached. Everything else was inferred.

Photographs to a walkable house

Zillow listing to 3D@realYunfanYe

Worth noting that Yunfan Ye posts his own caveat in the same breath: "the video was just created in one shot and there are still some wrong details." That is the honest version, and it is more useful than the reels.

Blender to Unreal Engine 5@goofyninjaaa
Goofy, in Spanish: a full house modelled in Blender and turned into an Unreal Engine 5 walkthrough. Pool, garden, living room, kitchen. His point: this is what a visualisation studio bills for today.

Head to head against Claude Fable 5.1

Same brief, two models@karankendre

What it is still bad at

A detailed teardown from yage.ai, which ran exploded views, rigging and webcam motion capture, found character modelling "still leaves plenty of room for improvement, as generated figures tend to stray considerably from the original designs," that getting a character right "requires an exhausting amount of manual micro-management," and that scene assets came back noticeably low-poly.

Structure yes. Fidelity sometimes. Character design not yet.

The operator read

Ignore the renders. The transferable lesson is the object tree.

When you are choosing between two AI outputs, prefer the one that returns structure over the one that returns a result, even when the result looks better today. A fused mesh and an object tree can render identically. Only one of them is still useful after the person who prompted it leaves.

That test applies well outside 3D. A generated report versus the query that produced it. A generated design versus its component tree. A generated answer versus the pipeline that derived it. Same choice every time.

Where are you generating results instead of structure?

Book a free Diagnostic: 30 to 45 minutes, no deck, no pitch. We find the place in your stack where you keep the output and throw away the thing that made it.

Book the Diagnostic →

Part 1 of Astra, Week One.

Sources
1Every post on this page is embedded from X and is the primary source for its own claim. Tom Krcha (@tomkrcha), Matt Wolfe (@mreflow), Pietro Schirano (@skirano), Yunfan Ye (@realYunfanYe), Goofy (@goofyninjaaa) and Karan (@karankendre), all September 3 to 4, 2026.
2yage.ai, "Exploring GPT-6 Astra's 3D Modeling: Exploded Views, Rigging, Motion Capture, and Video Generation", for the stated weaknesses quoted above and for the Hakurei Shrine exploded view and webcam-driven motion capture runs. yage.ai
3Build catalogues cross-checked while assembling this series: thejayant.in, atoms.dev and favtutor.com.
John Tan
John Tan

Founder and CEO of nativefirst.ai. Embeds with scaling founders and CEOs to ship Level-3 agents and AI workflows in production.