// AI NEWS · FEATURE

PhiloLabs Uses Claude Fable 5.1 Agent Swarms to Generate Explorable 3D Worlds Entirely From Code

A project called fable51-worlds shows autonomous Claude Fable 5.1 agents researching, modeling, and quality-checking browser-native 3D reconstructions of real places — Union Square in San Francisco and Higashiyama in Kyoto — then shipping them as plain Three.js apps. It is code-generated geometry, not a video or image model.

2026-09-03 · by Moe Ameen

Published 2026-09-03 · Updated

Short answer

fable51-worlds is an MIT-licensed PhiloLabs project in which Claude Fable 5.1 agent swarms research real places, generate them as code and check them against photos, then ship plain Three.js apps. Union Square in San Francisco has 453 building footprints, 129 storefronts, 220 pedestrians and 109 vehicles. Higashiyama in Kyoto has a 2.3 km walkable route. It is a research showcase, not an Anthropic product.

Key takeaways

  • PhiloLabs' fable51-worlds uses Claude Fable 5.1 agents to build explorable 3D places as Three.js code.
  • Union Square SF includes 129 storefronts, crowds, traffic, cable cars and Apple and Nintendo interiors.
  • Geometry comes from OpenStreetMap and USGS 3DEP; in Union Square, Playwright checks 34 fixed viewpoints against real photos.
  • Each world ships a walkthrough video and its own QA report, defects included.

What is the fable51-worlds project?

PhiloLabs published fable51-worlds, an open-source project (MIT-licensed) that uses autonomous Claude Fable 5.1 agent swarms to create explorable, browser-native reconstructions of real places and ship them as plain Three.js applications. The tagline is literal: "worlds via code, from fable 5.1." Rather than a model that renders pixels, this is a coding agent that writes the geometry, the scene assembly, and the runtime — every building, storefront, sign, tree, and traffic light is generated from open data and public reference imagery by code.

The pipeline runs in four stages. Research: parallel agents gather OpenStreetMap geometry (ODbL), USGS 3DEP elevation, transit specs, and storefront data with source attribution. Asset generation: Blender scripts (bpy) emit optimized GLB kits — façade modules, street furniture, vehicles, vegetation. Runtime assembly: a pure Three.js app combines terrain, streets, façades, props, crowds, and traffic from JSON specs. Quality assurance: Playwright-driven camera matching screenshots fixed viewpoints and compares them against photographs taken from the same spots, and independent reviewer roles (architect, geographer, technical artist) file reports.

Two worlds ship in the repo. Union Square, San Francisco: 453 building footprints, 75 hand-authored façades, 129 named storefronts, 220 pedestrians, 109 vehicles, working traffic lights and cable cars, day/sunset/night modes, two explorable interiors (Apple and Nintendo), and 34 camera-matched validation points. Higashiyama, Kyoto: a walkable route of about 2.3 km, a cel-shaded anime look, and a self-contained single-HTML deployment option. Each world also ships with a walkthrough video, about a minute long, recorded inside the finished scene.

Keep the framing straight. This is a demonstration of Fable 5.1's agentic coding applied to spatial reconstruction, built by PhiloLabs — not a new Anthropic product, and not a generative video or image model in the Sora or Veo sense. It is a research-grade showcase, not a consumer app you sign up for, and every world ships its own QA report with the defects listed. Treat the specifics above as a snapshot of the repo on the authoring date and check the source for current figures.

Why do code-built 3D worlds matter for creators?

  • It is a proof of a different kind of visual generation: not pixels from a diffusion model, but a real, explorable 3D scene written as code from open data — with source attribution and camera-matched QA baked into the pipeline.
  • The scope is the headline. Agents built a city-block reconstruction with crowds, traffic, and two walk-in interiors from a single prompt, which changes what a solo creator or small studio can attempt without a 3D team.
  • The most immediately usable creator output is not the world itself but the walkthrough video recorded inside it — a novel-viewpoint fly-through that is real, shareable footage.
  • It is not a content tool. There is no captioning, no brand voice, no carousel or blog fan-out, and no scheduler — it produces a Three.js app and a video file, and the distribution work still lives somewhere else.
  • The output is technical to run (a browser app plus assets, or a self-contained HTML file), so the gap between "impressive demo" and "posted to your audience" is exactly the production-and-publish step most creators do not want to build.

How do you turn a world walkthrough into posts with Kompozy?

The part of this a creator can actually post is the walkthrough video — the tour recorded inside the generated world. A Three.js app does not go to TikTok, but that fly-through is real footage, and footage is where Kompozy starts. Screen-record the world tour (or download the walkthrough video from the repo), drop it into Kompozy as a source, and one clip becomes a run of finished pieces held to a single Persona Brief so they read as one creator: vertical clipped shorts cut from the long fly-through, Persona Shorts where your talking-head avatar narrates over the world, quote graphics pulled from the best on-screen moments, a blog article on how it was built, and an email newsletter. Autopilot then schedules and publishes the set across the eight social platforms plus blog and email behind a per-post review.

That review gate matters here for one honest reason: AI-built worlds are the kind of thing an audience wants disclosed. Kompozy's per-post step is where you add your own AI-disclosure line before anything ships. Fable 5.1 World Modeling builds the spectacle; Kompozy turns the walkthrough footage it hands you into a week of repurposed, captioned, on-brand posts and gets them out the door.

What are the key facts about fable51-worlds?

  • fable51-worlds (PhiloLabs, MIT-licensed) uses autonomous Claude Fable 5.1 agents to generate explorable 3D worlds as plain Three.js apps — code, not a diffusion render.
  • Two worlds ship: Union Square SF (453 buildings, 129 storefronts, crowds, traffic, two interiors) and Higashiyama, Kyoto (a 2.3 km walkable route, cel-shaded).
  • Data comes from OpenStreetMap and USGS 3DEP; QA uses Playwright camera-matching against reference photos plus independent reviewer roles.
  • Each world ships with a walkthrough video recorded inside the scene, plus its own QA report with the defects listed.
  • It is a research-grade showcase, not a content tool — no captions, brand voice, or publishing. The walkthrough video is the shareable output; a tool like Kompozy handles the clip-and-publish step.

What does this look like in Kompozy?

This persona short was generated in Kompozy. It is the talking-head format you could narrate over walkthrough footage with; there is no fable51-worlds footage in it.

Real output · Kompozy Persona short format · from the Kompozy workspace

Who is this for, and who should skip it?

Best for:

  • Developers and technical creators curious about agentic coding applied to 3D scenes.
  • Creators who want striking walkthrough footage to talk over.

Not ideal for:

  • People wanting an app to sign up for. It is a GitHub repo you run yourself.
  • People who need posts out of the box. It produces a browser app and a video file.

Frequently asked questions

What is Fable 5.1 World Modeling?

It refers to PhiloLabs' fable51-worlds project, which uses autonomous Claude Fable 5.1 coding agents to research, model, and quality-check explorable 3D reconstructions of real places, then ship them as plain Three.js browser apps. It generates the scene as code from open data — it is not a generative video or image model.

Did Anthropic release a world model?

No. Fable 5.1 is Anthropic's text-and-reasoning model; fable51-worlds is a third-party project by PhiloLabs that applies Fable 5.1's agentic coding to 3D reconstruction. It is a demonstration of the model's coding ability, not a separate Anthropic world-generation product.

Where does the data for these worlds come from?

Geometry comes from OpenStreetMap (ODbL), USGS 3DEP elevation data (public domain) and the GSI elevation service. Reference photographs are used to check the result and are not redistributed in the repo.

Can I post one of these worlds to social media?

Not directly — the output is a Three.js web app, not a video file. The shareable asset is the walkthrough video recorded inside the world. You can screen-record or export that fly-through and then use a tool like Kompozy to clip, caption, and publish it across platforms.

How do we know this?

We checked every figure, date and quote on this page against the sources listed below on 2026-10-23, and removed or rewrote claims we could not confirm. Kompozy plan and format details come from kompozy.io/pricing.

Sources

  1. GitHub — PhiloLabs/fable51-worlds (read 2026-10-23)
  2. GitHub — fable51-worlds Union Square README (read 2026-10-23)
  3. GitHub — fable51-worlds Higashiyama README (read 2026-10-23)
  4. Kompozy — Pricing (read 2026-10-23)

Related news

← All AI news · Get started →