A single developer turned one design image into a full interactive 3D human anatomy app in a few iterations — no 3D artist, no game studio, just a chained pipeline of AI tools. "The Bugged Dev" built Anatomy Atelier by generating a design with GPT Image 2.0, converting organ images into 3D meshes with TripoAI, and handing the assembly, optimization, and interaction logic to OpenAI Codex running on GPT 5.6 Sol.
The interesting part isn't that AI can generate a 3D heart. It's the second half of the story: Codex took models that started at 120–150MB each, pushed total scene assets to roughly 900MB, and tanked performance to 16fps — then optimized that down to 28.6MB total, loading each organ on demand. That's a 97% asset-size reduction, and it's the difference between a demo and something that actually loads on the web.
TL;DR — what Anatomy Atelier is and how it was built
| Question | Direct answer |
|---|---|
| What is it? | An interactive web app with rotatable 3D models of the heart, brain, lungs, liver, and kidneys, with clickable hotspots and explanations |
| Who built it? | Solo developer "The Bugged Dev," posted August 2, 2026 |
| Design tool? | GPT Image 2.0, used to create the base design and per-organ reference images |
| Image-to-3D tool? | TripoAI, converting each generated image into a 3D model |
| Coding agent? | OpenAI Codex, described as running on GPT 5.6 Sol |
| Rendering stack? | Three.js in the browser |
| Starting asset size? | ~900MB total, ~120–150MB per organ model, 16fps |
| Final asset size? | 28.6MB total, ~2–5.5MB per organ, loaded on demand |
| Is it free to try? | Yes — live at anatomy-livid.vercel.app, no login mentioned |
| Is the code public? | Yes, on GitHub under thebuggeddev/anatomy |
| Notable reaction? | OpenAI's Greg Brockman called it "chatgpt for building interactive educational tools" |
The pipeline: four tools, one build
The build order matters because it shows where each tool's strength was actually used, rather than asking one model to do everything badly.
- Design image (GPT Image 2.0). The developer created one overall design image first, establishing a visual style before touching any 3D tooling.
- Per-organ reference images (GPT Image 2.0). Every organ — heart, brain, lungs, liver, kidneys — got its own generated image, one by one, matching the established design language.
- Image-to-3D conversion (TripoAI). Each organ image was fed into TripoAI to produce a 3D mesh, skipping manual sculpting entirely.
- Assembly and coding (OpenAI Codex). Codex received the design image, the master prompt, and all the 3D models, then built the first working version of the Three.js app.
That first Codex pass reportedly worked and looked right — but shipped models roughly 30x larger than what a browser should load per asset. That gap between "AI produces something functional" and "AI produces something production-ready" is the real story here, and it mirrors what explainx.ai has tracked in other long-horizon Three.js coding agent experiments: generation is now cheap, but performance and polish still take iteration.
Where Codex did the real engineering work
Three specific things separate Anatomy Atelier from a one-shot demo:
Asset optimization
Codex reduced each organ model from 120–150MB down to roughly 2–5.5MB while preserving visual quality — likely through mesh decimation, texture compression, and format conversion (Three.js projects typically move toward glTF/GLB with Draco or Meshopt compression for this kind of reduction). The developer reports this took the total package from ~900MB to 28.6MB.
On-demand loading
Rather than loading all five organs upfront, each model loads only when selected. This is a standard web-performance pattern, but getting an AI coding agent to apply it correctly — lazy-loading a Three.js asset without breaking scene state — is not trivial to prompt for reliably.
Educational content generation
Beyond the models themselves, Codex reportedly generated the anatomical illustrations showing where each organ sits in the body and built the interactive hotspot markers that explain organ substructures. That's UI logic, content generation, and 3D interaction stitched into one coherent app.
What people are asking
Is this a medically accurate reference tool? There's no indication the models were validated against clinical anatomy references or reviewed by a medical professional. Treat it as an educational visualization and engagement tool, not a substitute for a verified anatomy atlas — the value here is in interactivity and interest, not diagnostic precision.
Did Codex really do all of this in one shot? No, and the developer is explicit about that: "the process wasn't exactly one shot, but it also wasn't difficult. You just have to do it step by step." The optimization pass in particular took multiple iterations to hit the final file sizes.
How is this different from Karpathy's Three.js world demo? Andrej Karpathy's procedural Lord of the Rings world generated a scene entirely from a text prompt with no real-world reference assets. Anatomy Atelier instead chains a design-to-image-to-3D-to-code pipeline across four separate tools, which is closer to an asset production workflow than a single-prompt generation test.
What made Greg Brockman single it out? His framing — "chatgpt for building interactive educational tools" — points at the shift from AI writing static explanations to AI producing genuinely interactive learning artifacts, aligned with what explainx.ai covered in its own move toward interactive learning pathways.
The inspiration chain
The developer credited Dilum Sanjaya's earlier 3D animal and plant cell project as direct inspiration, describing it as a "looong wish" finally realized. That's a useful data point on its own: one well-shared vibe-coded educational demo is now visibly seeding a second, more ambitious one within the same year. It's the same compounding pattern explainx.ai has tracked in other vibe-coded, single-developer projects — a low barrier to entry means good ideas replicate fast.
Bottom line
Anatomy Atelier is a useful case study for anyone chaining generative image, image-to-3D, and coding-agent tools together: the AI-generated first pass got the app "looking right" quickly, but the unglamorous optimization work — cutting 900MB to 28.6MB — is what actually made it usable on the web. That optimization step, done conversationally through Codex rather than manually in a 3D tool, is the part worth paying attention to.
Related on explainx.ai
- Karpathy's Opus 5 Lord of the Rings Three.js world
- img2threejs: procedural 3D as editable code
- Claude of Duty: procedural Three.js FPS
- Software for one: personal apps built by AI coding agents
- Introducing interactive AI learning pathways on explainx.ai
- Microsoft's AI for Beginners curriculum guide
Sources: The Bugged Dev's original post · Anatomy Atelier live app · GitHub repository · TripoAI
Claims about tooling, asset sizes, and workflow reflect the developer's public post on August 2, 2026. explainx.ai has not independently benchmarked the live app's file sizes or frame rate.