Talos3D
Log in Sign up

Authored 3D design platform

Structured 3D models for design tools and automation.

Talos3D is a work-in-progress 3D platform built around authored geometry, command history, semantic model state, and capability-based extensions. The goal is practical rather than ornamental: keep the editable model contract available to the user interface, MCP clients, automation, drawing export, and domain-specific tools. The first hosted product surface is Talos3D Architecture, served on architecture.talos3d.com.

Authored model first Shared command surface for UI and AI Drawing workflows from the live model Capability-based extension boundaries
Open Architecture App Log in / Sign up

Built in the open around authored models, drafting workflows, and a public command substrate that can support both product UX and external tools.

Model meaning

Structure stays visible.

Entities, relationships, views, and commands remain first-class instead of becoming editor-only knowledge.

Platform thesis

One core, multiple hosts.

The same foundation is being used for native workbench code, MCP access, domain packs, and browser-hosted workflows.

Case study · Reference Cottage 5×6

From napkin sketch to blueprint set in two evenings.

A hand sketch of a 30 m² lakeside cottage went to the Talos3D agent. Over nine rounds of plain-language direction, it became an authored model with catalogue doors and windows, a timber frame, an insulated roof and two foundation options. The result is an eight-sheet A3 drawing set and site and interior studies, all drawn from the same model.

Follow the journey See the drawings
White timber cottage with a dark standing-seam roof, two pairs of patio doors and sliding shutters, in a Swedish lakeside meadow.
AI-assisted illustration Revision I from the southwest. The building geometry comes from the model.
  1. Hand-drawn floor plan sketch. 01Sketch Two rooms, a bathroom and a round table for four.
  2. Model cutaway with the folding partition open. 02Iterate Each direction applied to the model, then checked against it.
  3. Timber frame of the cottage. 03Structure 194 framing members, a 22° insulated roof, slab or piers.
  4. Drawing sheet A-105, plan and bathroom. 04Blueprints Elevations, plan, section and framing at 1:25.
  5. Interior study of the north room looking toward the lake. 05On site & inside Studies that keep the model's geometry.

Current render studies

Cedar pavilion captured from the current viewport.

These captures are exported from the current Talos3D viewport using authored entities, bundled material definitions, and the active renderer. They are product-state images, not post-produced concept art.

Cedar pavilion rendered in Talos3D with translucent wall panels and a dark base.
Cedar pavilion model with translucent wall panels, timber posts, roof planes, and a dark base.
Alternate angle on the cedar pavilion showing timber framing and translucent panels.
Alternate viewport angle showing the timber frame, panel placement, and material contrast.

Why it matters

Mesh-only state loses design context.

When editing intent exists only as triangles or editor-local state, downstream tools have to reconstruct basic facts. Talos3D stores authored entities, relations, views, dimensions, and commands so model inspection and editing can operate on the same underlying data.

Less reconstruction

Rooms, storeys, openings, features, guides, and relationships do not need to be reverse-engineered from triangles.

More usable AI

The in-app assistant and external agents work through the same MCP and command surfaces instead of hidden editor hooks.

Better communication

Recent drafting work turns the live model into orthographic views, dimensioned exports, and paper-ready PNG, PDF, and SVG output.

Key differentiator

The authored model is the product.

Talos3D treats meshes, highlights, previews, and caches as derived artifacts. The real source of truth is the authored model: entities, definitions, parameters, semantic assemblies, typed relations, and evaluated facts.

Recent work

Drafting emerges from the same live scene

Orthographic drawing views, dimension offsets, guide-line inference, named views, and `export_drawing` turn modeling state into paper-style PNG, PDF, and SVG output without a separate drawing model.

AI without special privileges

MCP is a real public surface

Model inspection, screenshots, view control, lighting, dimensions, guides, assemblies, and edits are exposed through a structured MCP interface backed by the same command and history pipeline the UI uses.

Broader than one vertical

Architecture is a reference extension, not the limit

The core currently hosts modeling, architecture, terrain, content libraries, and assistant workflows. The capability model is intended to let future domains add tools, vocabularies, rules, and catalogs through the same extension boundary.

Current direction

Talos3D treats rendering as one output of the model.

Current work keeps authored model state primary, exposes inspection and edits through MCP, and derives views, drawing output, and domain workflows from the same command-backed model.

Model meaning

  • Authored entities and definition graphs
  • Assemblies and typed relations
  • Evaluated body summaries for AI

Communication

  • Orthographic and named views
  • Dimensions and construction guides
  • PNG, PDF, and SVG drawing export

Platform reach

  • Embedded assistant through MCP
  • Capability-based domain packs
  • Desktop and browser-hosted direction

Built with

Rust, Bevy, and a browser-hosted direction.

Talos3D uses Rust for correctness and performance, Bevy for ECS-driven runtime composition, and a browser-hosted direction aligned with WebAssembly (Wasm).

Rust

Data modeling, reproducible command pipelines, geometry work, import/export, and AI integration are implemented in Rust.

Bevy

The ECS architecture supports plugin composition, capability boundaries, authored entities, and multiple workbench surfaces.

Wasm

Bundled catalogs, abstract storage boundaries, and managed assistant relays all point toward browser-hosted deployments that keep the same core model contract.

Open platform

For teams evaluating structured 3D authoring.

The public core is the best place to inspect the current model contract, MCP surface, command pipeline, drawing work, and extension boundaries.

Read core README Read product overview