01
Plan
The agent reads the product revision, evidence, previous checkpoints, and the user's requested change.
3D Studio
A modeling workspace that understands the product.
ConfigAI 3D Studio keeps the model, source evidence, product revision, agent conversation, checkpoints, and review decision in the same workspace instead of treating 3D as a detached file upload.
3D Studio · Lounge Chair
checkpoint 04Astra · high
ModelEvidenceReview
source → build123d → Blender → checkpointreview required
Start from anywhere
Missing model, source URL, existing GLB/STEP, or a blank brief.
A project can begin from the product library, a public reference page, an uploaded model that needs repair, or a description of what should be created.
Product with no model
Use the exact product revision and its sources as the modeling brief.
Reference URL
Attach the URL as project evidence before any modeling work begins.
GLB / STEP upload
Repair, optimize, or rebuild an existing asset while preserving the original.
Create from brief
Start from a prompt, then add dimensions and references as evidence.
Agent + deterministic tools
Use AI for intent. Use deterministic tools for geometry.
The modeling agent can decide what needs to change, while build123d and Blender workers execute bounded geometry steps through explicit manifests and project tickets.
02
Execute
Deterministic CAD work goes to build123d; mesh, scene, and render operations go to the Blender worker through bounded runner contracts.
03Current design
Checkpoint
Every meaningful result becomes a checkpoint with an artifact, revision context, and enough history to compare or request another change.
Review
A generated model is not automatically a product model.
The reviewer sees the artifact, source evidence, revision history, and assumptions before deciding whether to approve, reject, request another revision, attach the model to an existing product, or create a new draft product.
Human review
Compare checkpoint against references
Inspect dimensions and object identity
Separate verified facts from assumptions
Approve / reject / request revision
Attach only after approval
Artifact contract
The model pipeline is designed to fail closed: a runner should not silently attach the wrong object, overwrite the active project, or mutate the product while a job is still running.
exact object ticket
manifest snapshot
checkpoint artifact
cleanup lifecycle
Next modeling layer
Routing, semantic parts, materials, and the digital twin belong after the project contract.
We can add smarter tool routing, semantic part labeling, material workflows, and a richer USD representation without changing the core project/revision/review model.
Roadmap
Tool router
Choose Blender, build123d, or specialized workers based on the requested operation.
Roadmap
Semantic parts
Seat, back, arm, leg, frame, and other part identities attached to geometry.
Roadmap
Materials & PBR
Review material assignments and texture generation as product-linked revisions.
Roadmap
USD digital twin
Reflect approved product variants and component changes in a richer scene model.
ConfigAI workspace
Keep the model inside the product history.
3D should not be a file somebody uploaded last year. It should be a reviewed artifact tied to the product revision, source evidence, and the exact modeling work that produced it.