正在加载视频...

视频加载失败

GPT-6 Astra could take the next step in medicine "A full interactive skeleton with all 206 bones got built in two hours" ∙ Astra was pointed at an open anatomy dataset ∙ Codex wrote the entire interface, bone by bone, all 206 of them ∙ It shipped as a...

20,901 次观看 • 4 天前 •via X (Twitter)

28 条评论

Zyvex 的头像
Zyvex4 天前

This is the part people are underestimating. The crazy thing isn’t the 206 bones. It’s that the bottleneck is no longer knowing how to build the thing. You describe it → the model builds it → you interact with it. That changes what “learning” can look like in medicine.

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

The shift from building models to interacting with them is huge

Peik Gabriel 的头像
Peik Gabriel4 天前

okay, I need to try this

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

I hope everything works out for you

Alpha Mom 的头像
Alpha Mom4 天前

two hours is the crazy part. once tools can turn a raw dataset into something this usable that fast, the bottleneck starts shifting from building to knowing what to ask for

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

The bottleneck is quickly becoming knowing what to ask, not building it

Voyz 的头像
Voyz4 天前

the bone by bone interface is such a nice touch.

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

Being able to isolate and explore each bone feels much more useful than just looking at a static 3D model

DEV 的头像
DEV4 天前

Using an open anatomy dataset for this build was a smart move, data quality matters.

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

Yes, very well said my friend

maximum 的头像
maximum4 天前

the way AI is evolving is already starting to worry me - skynet is coming, guys 😅

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

It’s evolving very rapidly. You can’t keep up with everything LOL

Joseph Ekene | AI & Robotics 的头像
Joseph Ekene | AI & Robotics4 天前

The exciting part is how quickly AI can turn complex anatomical data into something interactive and easy to explore. Tools like this could make medical education far more accessible. @ZentrixHQ Thanks for sharing.

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

I'm sure this can help medicine

Trixi 的头像
Trixi4 天前

This is the most interesting thing I saw on my feed today

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

But this is something unreal. I would really like to see it shown in lectures at medical schools

安叫兽|Bird🕊️ 🔶 BNB 的头像
安叫兽|Bird🕊️ 🔶 BNB4 天前

逐骨写完还做成交互界面,这速度有点离谱了

Zentrix⌚️ 的头像
Zentrix⌚️4 天前

I think this could be useful for learning

Brian Pridgen, MD 的头像
Brian Pridgen, MD4 天前

Reposting is fine. But please give credit to @emmanuel_2m. Same with your other posts. Please give creators credit.

Brian Shields 的头像
Brian Shields4 天前

Somewhere in Rome a capuchin monk is burning tokens redesigning their crypt

Roan 的头像
Roan4 天前

this is next level trixi

AI Mastery Guide 的头像
AI Mastery Guide4 天前

206 bones in two hours, huge for med students

Elledyne Labs 的头像
Elledyne Labs4 天前

the "shipped as a claude code artifact" line is the part that matters. 206 bones is a UI problem; shipping a working tool from a prompt is a workflow problem. codex gets the first, not the second.

Squizer 的头像
Squizer4 天前

funny that no matter which model does the thinking, it still ends up shipping through Claude Code at the end. execution layer's getting more durable than any one model.

Peace 的头像
Peace4 天前

Impressive

catman 的头像
catman4 天前

the Claude Code artifact sounds more interesting than the demo itself: can it expose the source and relationships behind each of the 206 bones? otherwise, it may be a polished anatomy viewer rather than a trustworthy learning tool.

Christina Haftman 的头像
Christina Haftman4 天前

Just in time for Halloween!

Sr. X 的头像
Sr. X4 天前

Link?

相关视频

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

195,173 次观看 • 1 年前