meshy-openclaw

# Meshy 3D — Generation + Printing Use Meshy CLI **0.4.0** to turn the user's request into a delivered asset: the requested files in the requested location, an inspected preview when one exists, and — for prints — the intended size, analysis/repair results and a slicer handoff when asked. Login or task submission alone is not completion. Choose the shortest suitable pipeline and reuse existing assets for follow-ups. ## SECURITY MANIFEST **Executables:** only the Meshy CLI — `meshy`, or the pinned temporary package `npm exec --yes --package=meshy-cli@0.4.0 -- meshy`. No Python, no `curl`, no bundled scripts. **Credentials:** the CLI's own browser sign-in (OAuth device flow) stores and refreshes a session in `~/.config/meshy/credentials.json` (mode 0600). An existing `MESHY_API_KEY`, or an explicit `--api-key-file`, is honoured and takes precedence. The skill never reads, prints or copies a token, device code or key, and never asks for one in chat. `MESHY_API_KEY` is optional. **Network:** the Meshy API (`api.meshy.ai`) and its sign-in page (`www.meshy.ai`); the media hosts of assets being downloaded or input URLs being checked, without the credential; the npm registry when the CLI is installed or run as a temporary package. **Files:** writes only inside one workspace per job — the directory the user named, or `./meshy_output` — and the CLI refuses paths that escape it, including through symlinks. Existing files are not overwritten unless the user asked for it. Reads only...