Image to Three.js browser workspace

Your coding agent builds in its authorized project while this page receives the progress, editable source, review evidence, and sandboxed interactive preview. PLAYTEX does not launch a second agent or upload the reference image.

Create a browser session Agent protocol Read the complete guide

Your agent builds; the browser displays

Create a private 24-hour session, paste its generated prompt into Codex, Claude Code, Cursor, OpenCode, or another capable coding agent, and attach the reference there. The agent publishes meaningful stages and generated artifacts back to the open page.

A clear privacy boundary

The reference stays with the user's agent. Generated status, source, preview, sculpt spec, evidence, and artifact metadata are intentionally relayed to the private browser session. No PLAYTEX account or API key is required, and the session expires automatically.

A staged reconstruction instead of a one-shot mesh

  1. Validate whether the image is suitable and admit only readable references.
  2. Write a quality contract and inventory identity-defining details.
  3. Create and strict-validate the component, topology, material, pivot, and attachment spec.
  4. Build in locked passes from blockout through structure, form, materials, interaction, and optimization.
  5. Compare against the reference, review multiple useful angles, and self-correct within a bounded loop.
  6. Return the TypeScript factory, sculpt spec, review evidence, and honest fidelity and limitation notes.

Canonical agent outputs

  • createModel.ts with a factory returning THREE.Group
  • object-sculpt-spec.json with hierarchy, materials, attachments, pivots, sockets, and review state
  • Reference-versus-render comparison and multi-angle review evidence
  • Suitability, fidelity, assumptions, limitations, and reviewed-angle notes

GLB or GLTF export can be added downstream when the user requests it, but the core contract remains editable procedural source.