Meshy

View saved version →

---
name: meshy-3d-generation
description: "Generates and edits digital 3D assets with the Meshy CLI: text-to-3D and image-to-3D models, texturing, remeshing and LODs, UV unwrapping, format conversion (GLB, FBX, OBJ, USDZ, STL, 3MF, Blender), rigging, animation, motion clips from text and reference images. Use when the user asks to make, texture, rig, animate or convert a 3D model or game asset. For physical 3D printing use meshy-3d-printing."
license: MIT
compatibility: "Needs Node.js 22.12+ and the Meshy CLI 0.8.x, 0.8.2 or later (npm install -g meshy-cli@0.8); network access to the Meshy API."
---

# Meshy 3D Generation

Use Meshy CLI **0.8** (0.8.2 or later) to turn the user's request into a delivered asset. Completion means
saving the requested files in the requested location, inspecting an available preview, and
finishing any project integration the user requested. Login or task submission alone is not
completion. Choose the shortest suitable pipeline and reuse existing assets for follow-ups.

## Read what this request needs

| Need | Reference |
|---|---|
| CLI runner, credentials, or output location | [Setup](references/setup.md) |
| Generation, texturing, remeshing, conversion, scale, or 2D images | [Pipelines](references/pipelines.md) |
| Rigging, animation, or generated motion | [Animation](references/animation.md) |
| Cost, waiting, preview, delivery, or finding a previous model | [Delivery](references/delivery.md) |
| Failed or uncertain operation | [Troubleshooting](references/troubleshooting.md) |

Read the relevant section when needed; recipes are examples to adapt to the requested result,
not a requirement to execute every stage. An untextured model skips texture generation; an
existing GLB needs no extra format conversion. Use command help when parameters are uncertain.

## First use and authorization

**DeepSeek Harness with the Meshy plugin** (`DSH_MESHY_CLI` is set; check with
`test -n "$DSH_MESHY_CLI"`): the plugin ships the CLI and keeps the sign-in. Run every command as
`"$DSH_MESHY_NODE" "$DSH_MESHY_CLI" …` in place of `meshy …` — never a `meshy` on PATH, which
cannot see that sign-in — install nothing, and when a command reports that nobody is signed in,
call the `meshy_sign_in` tool instead of `auth login` (Setup, section 1). Everywhere else:

Before the first command run `meshy --version`; no need to ask. When `meshy` is missing or
older than 0.8.2, install the newest 0.8.x with `npm install -g meshy-cli@0.8` and say so in
one line; Setup covers a refused install and a CLI of 0.9 or newer. Reuse a verified session. If login is
needed, follow Setup and run `auth login --device` (adding `--region cn` for a user in mainland
China: the same account and the same credits as the global site) in a persistent tool session. Show its
verification URL and user code in **commentary/progress, not a final answer**. Await that same
session in this turn until it exits, verify `auth status`, then continue the original request.
A background process cannot resume a finished turn; do not require a "done" chat message, except in
Setup's two-step sign-in for a user on a remote chat (a phone through a chat bot).
Browser approval stays with the user; credentials never belong in chat.

## Execution boundaries

- Run API, upload, download and mesh operations through the CLI. Local inputs have a 50 MiB
  limit, and a local model must be GLB or glTF (rigging, UV unwrap and multicolor: GLB); use the supported
  URL input route for anything else.
- Use `--format json --no-update-check` on every command: stdout is one `meshy.cli/v1` envelope,
  auth included. Resolve `WORKSPACE` from the user's output
  path and pass it to writes.
- Submit once with `create --async`, retain the owning resource and ID, then `wait` on that
  task. Keep the agent turn active while awaiting a running command. Follow Troubleshooting
  on timeout or unknown submission; these do not authorize another paid create.
- Continue work within the user's approve

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: meshy-3d-printing
description: "Generates and prepares models for physical 3D printing with the Meshy CLI: white and multicolor prints (3MF, STL, OBJ), printability analysis and repair, splitting into parts, Creative Lab products such as figures, lamps and keychains, sizing, and slicer handoff (Bambu Studio, OrcaSlicer, PrusaSlicer, Cura). Use when the user wants something 3D-printed or asks for print or slicer files."
license: MIT
compatibility: "Needs Node.js 22.12+ and the Meshy CLI 0.8.x, 0.8.2 or later (npm install -g meshy-cli@0.8); network access to the Meshy API."
---

# Meshy 3D Printing

Use Meshy CLI **0.8** (0.8.2 or later) to deliver the requested print files at the intended size, with
analysis/repair results where applicable and a slicer handoff when requested. This skill is
self-contained. Ordinary digital assets belong to meshy-3d-generation.

| Need | Reference |
|---|---|
| CLI runner, credentials, or output location | [Setup](references/setup.md) |
| Local preparation, white or multicolor prints, analysis/repair, or splitting into parts | [Printing recipes](references/printing.md) |
| Creative Lab products (figures, lamps, keychains, magnets, keycaps, fidgets) | [Creative Lab](references/creative-lab.md) |
| Cost, waiting, preview, delivery, or finding a previous model | [Delivery](references/delivery.md) |
| Failed or uncertain operation | [Troubleshooting](references/troubleshooting.md) |

Read relevant sections as needed. Recipes illustrate valid commands; select only the stages
needed for the user's output.

## Choose local or cloud work

| Request | Route |
|---|---|
| Scale, orient or ground an existing OBJ | Local `mesh prepare-print`; no auth or balance |
| Open an existing STL or 3MF | Local `slicer detect` and `slicer open`; no auth or balance |
| White model from text or photo | Generate geometry without textures; analyze/repair as needed; prepare the file |
| Multicolor model | Generate/reuse geometry; analyze/repair as needed; texture; multi-color-print |
| Print in separate parts (build plate, colours per part, fewer supports) | Generate/reuse geometry; auto-split; slice the parts |
| Check or fix an existing model (holes, thin walls), any format | Free analyze-printability by task ID or `--model-url`; repair only if needed |
| Resize an existing STL, 3MF or GLB | Scale it in the slicer; only an OBJ is resized locally |
| Creative Lab figure (a stylized collectible from a photo), vinyl figure, brick figure, lamp, keychain, fridge magnet, keycap or pixel fidget board | Prototype → review → build → select product artifacts |
| Creative Lab collapsible fidget | One create from the photo → STL |

Colour routes differ: multicolor paints one object's surface for a multi-material printer; a
split cuts it into parts, one filament each, and drops the texture (split before any repair;
the two do not chain); the pixel fidget board is a product of its own.

A figurine does not by itself require Creative Lab. Infer the route from the intended product;
ask about size, color or style only when the missing choice materially changes the result.
For an existing model, distinguish local preparation from cloud printability analysis; a
local dimension check cannot establish full printability.

## Cloud authorization

**DeepSeek Harness with the Meshy plugin** (`DSH_MESHY_CLI` is set; check with
`test -n "$DSH_MESHY_CLI"`): the plugin ships the CLI and keeps the sign-in. Run every command as
`"$DSH_MESHY_NODE" "$DSH_MESHY_CLI" …` in place of `meshy …` — never a `meshy` on PATH, which
cannot see that sign-in — install nothing, and when a command reports that nobody is signed in,
call the `meshy_sign_in` tool instead of `auth login` (Setup, section 1). Everywhere else:

Before the first command run `meshy --version`; no need to ask. When `meshy` is missing or
older than 0.8.2, install the newest 0.8.x with `npm install -g meshy-cli@0.8` and say so in
one line; Setup covers a refused install and a CLI of 0.9 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.