Release notes

See what's new in each Meshy DCC Core release.

0.2.4

Released November 9, 2026.

Agents stay connected. Opening an app no longer takes over the Meshy DCC Core service and disconnects the agents that use it.
Large connector downloads. Installing a connector no longer fails when its package takes more than 30 seconds to download.
Safer archives. Connector, marketplace, and update archives are checked more strictly before they're unpacked, and an archive that tries to write outside its folder is refused.
Clearer tool errors. Calling a tool that an open app doesn't have reports the tool as unknown and suggests close matches, instead of reporting the app as offline.
No repeated actions. A request that may already have reached an app is reported as having an unknown result and is never sent again.
Readiness. An app counts as ready only after Meshy DCC Core reaches it the same way it sends requests, and the diagnostics say why an app isn't ready.
Usage statistics. The daily report also goes to a second analytics service. For details, see Usage statistics.

0.2.3

Released November 3, 2026.

MCP access to the local service. Agents that use MCP can connect to the Meshy DCC Core service at http://127.0.0.1:19765/mcp, next to the meshy-dcc command and skill. It's one service for every app, so you still don't set up an MCP server for each app.
Project lifecycle. From the command line or over MCP, an agent can configure a project, open or reuse the exact app instance for that project, and close it safely. Closing an app keeps your unsaved work, and Meshy DCC Core doesn't repeat a step whose result is unknown.
App detection. Meshy DCC Core finds the installed copies of all 13 apps, including more than one version of the same editor and a custom location you used before, and prepares their connectors before you create a project.
Activity check. meshy-dcc active-work shows whether an agent session still has requests in progress.
Connectors 0.1.2. All 13 connectors are rebuilt on this release, with a corrected macOS build. The Godot connector also verifies the exact editor it started and rejects invalid vector values before it changes a scene.
Skills stay as you set them. When a package manager such as npm installed Meshy DCC Core, it leaves your agents' skills unchanged until you run meshy-dcc agent-skill --execute.
Fix: an app or service that Meshy DCC Core starts is no longer tied to the app that started it.

0.2.2

Released October 28, 2026.

To update from 0.2.1, run meshy-dcc update apply --yes, then run meshy-dcc gateway restart once. From 0.2.2 on, updating restarts the service for you.

Usage statistics. Once a day, Meshy DCC Core sends anonymous, aggregate counts, such as versions, connectors, and tool-call outcomes. It never sends what you work on. You can turn it off at any time. For details, see Usage statistics.
Update now. When an update is available, Overview in the window shows an Update now button. meshy-dcc update apply --yes also restarts the local service, so the new version runs at once. Add --no-restart to leave the service running.
Connectors 0.1.1. All 13 connectors move to 0.1.1. The Blender connector checks that a saved scene was written, the 3ds Max mesh tools load again, and the FreeCAD connector no longer publishes a file when a step fails after it writes the file.
Clearer timeouts. A call that reaches its time limit reports that its result is unknown, so your agent reads the scene back before it repeats the call.
Fix: a tool call that timed out could still run later and change the scene in Blender, Maya, 3ds Max, Houdini, or Substance 3D Painter. The time limit now reaches the app. This fix needs connectors 0.1.1 or later.
Fix: on Windows, an update that had finished was reported as failed.
Fix: reloading skills no longer drops the skills a connector registered, and search finds skills described as "2D".
Fix: meshy-dcc doctor and meshy-dcc gateway status only read your setup and no longer change it.
Security: the local service and the connectors' Python components include fixes for published security advisories. Connectors 0.1.1 and later carry them.

To update from 0.2.0, install Meshy DCC Core again with the command in Install Meshy DCC Core, or run npm install -g meshy-dcc@latest if you installed with npm. On Windows, run meshy-dcc gateway daemon stop first. Then run meshy-dcc gateway daemon restart.

Report a problem. Run meshy-dcc report --summary "...", or go to Settings > Report a problem in the window. You see the exact report first, and nothing is sent until you add --yes or click Send. For details, see Report a problem.
More logos. The window shows the logos of Houdini, Substance 3D Painter, FreeCAD, OpenSCAD, and Material Maker, and of the Pi, Amp, and Kimi Code CLI agents.
Fix: meshy-dcc update apply --yes now updates the meshy-dcc-server installed next to the command, and the first command after an update shows its own output.
Fix: the setting that turns off the daily update check now also turns off the marketplace check that ran with every command.

0.2.0

Released October 19, 2026. The first release.

One creation pipeline across your DCC apps. One entry point to every open instance of 13 apps, from Blender, Unity, Godot, and Unreal Engine to Houdini, Maya, 3ds Max, Substance 3D Painter, and ZBrush, on macOS (Apple Silicon) and Windows (x64), with each request routed to the exact instance and tools loaded as skills on demand.
One skill for every agent. The installer adds the Meshy DCC skill to Claude Code, Codex, Cursor, and the other agents it finds, out of more than 70 supported.
The Meshy DCC Core window. meshy-dcc ui shows connected apps, installs connectors, turns the skill on for your agents and lists every skill each app has loaded. Available in English, Chinese, Japanese, and Korean.
Custom skills. Write a Blender skill of your own, or have your agent write it, and every agent can use it.
Safe by design. Every request goes to the app instance the agent names, the agent reads every change back, and the local service accepts requests only from your computer.