Meshy 3D Printing

Use Meshy CLI 0.8 (0.8.3 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.

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

Choose local or cloud work

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.3, 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. Local-only work stops at runner setup. Cloud work reuses a verified session. If login is needed, keep auth login --device running (with --region cn for a user in mainland China: the same account and credits as the global site), show its URL and user code in commentary/progress, never a final answer, and await the same tool session in this turn. After it exits, verify auth status and resume the print job. Never ask for credentials in chat, nor for a "done" message except in Setup's two-step sign-in for a user on a remote chat (a phone through a chat bot); Setup has the host wait procedure.

Only the CLI touches its config directory (~/.config/meshy by default): never read, copy, edit or delete a file there (an old credentials.json included), and never look for credentials anywhere else. When a sandboxed shell blocks the network (auth login fails with oauth_network or fetch failed), run the same command again with network access or outside the sandbox, asking the user to allow it if the host requires. Do not probe with curl or switch to --with-key (Setup, section 3).

Printing-specific constraints

• Repair changes geometry and drops textures. Use repaired geometry downstream and retexture before multicolor output. Use analysis when functional parts, thin features or other requirements make it relevant, with the printer type and print size when known so wall thickness is checked too; its report does not establish material suitability.
• Prepare a Y-up OBJ as a new Z-up file at the requested height, centered and grounded. Do not repeat the transform or apply it to STL, 3MF, or relief product output. A multicolor 3MF requires no OBJ conversion; cloud print files are scaled in the slicer (Printing recipes, Print size). Product ZIPs and optional lamp bases have distinct handling in Printing recipes.
• API, downloads and geometry operations use the CLI. Local inputs have a 50 MiB limit, and a local model must be GLB or glTF (multicolor: GLB); an STL, OBJ or FBX goes to Meshy only as an http(s) URL. Every command uses --format json --no-update-check and prints one meshy.cli/v1 envelope; writes carry the resolved --workspace WORKSPACE. Read returned paths and IDs rather than guessing.
• Submit cloud tasks once with create --async, retain their resource and lineage, and wait on the same task. Keep the turn active during waits. Unknown submission and interrupted downloads are recovery cases, not permission to generate again.
• Work within the approved scope and budget; propose additional paid stages before spending. Delivery describes applicable estimates. Local preparation and printability analysis are free.

Finish the handoff

Show an available rendered preview and deliver file paths, dimensions, analysis/repair status and reported charges. Launch a detected slicer only when requested or already authorized; launch_requested does not prove successful import or start a physical printer. If no suitable slicer is installed, still deliver the files. Explain relevant remaining checks, such as supports and wall thickness, without describing an untested model as guaranteed printable.