GAMESLASHMeshy DCC Core 0.2.4 fixes agent disconnects and duplicate actions across game asset apps
By GameSlash
November 9 update keeps creative apps connected to AI agents, improves connector installs and avoids repeating uncertain operations across Blender, Unity and Godot.
Meshy released DCC Core 0.2.4 on November 9, 2026. This update addresses connection drops between AI agents and creative applications, improves connector installation, and avoids replaying operations when the previous request's result is uncertain. For game developers moving 3D assets between Blender and engines, it targets a failure mode more consequential than a cosmetic UI change: an agent editing the wrong session or executing the same change twice.
What is different in 0.2.4?
According to Meshy's November 9 changelog, opening another supported app no longer takes over the local DCC Core service and disconnects agents already using it. Connector downloads that exceed 30 seconds no longer fail simply because of that delay. When a tool call refers to a missing function, the service now reports an unknown tool and suggests close names instead of wrongly saying the whole app is offline.
Most importantly for automated scene changes, an action that may have reached an application is reported as an unknown result and is not sent again automatically. A tool that appears to time out could have already imported a model or created objects; repeating it blindly can produce duplicate meshes or conflicting edits. The new diagnostic flow lets the agent inspect the target app instead of assuming a second edit is safe.
How this works for Blender, Godot, Unity and Unreal
Meshy DCC Core is a local gateway rather than a new 3D-generation model. It offers one agent-facing entry point to 13 creative applications and routes operations to the specific open instance selected. Developers can have an agent import a Meshy-generated model into Blender for adjustments, then move it into a Godot, Unity or Unreal project. The existing workflow supports an MCP endpoint at 127.0.0.1:19765/mcp and skills for tools such as scene, import and materials.
Checks before trusting an AI asset pipeline
In the connector guide, Blender is installed per computer while Unity, Godot and Unreal connectors are added per project. On the affected projects, confirm that the intended app and scene are marked ready, then have the agent read the scene or asset list back after edits. Version 0.2.4 also strengthens archive validation so an update archive cannot write outside its designated folder, and readiness is now determined by reaching an app through the same path used for requests.
The software runs on Apple Silicon macOS and x64 Windows, and the local DCC workflow is free without a Meshy account or credits; generating 3D models through Meshy is a separate paid-plan workflow. Core installation, updates and optional usage reporting need internet access, while agent requests stay local. These fixes improve reliability but are not evidence that every engine connector or complex asset task has been independently tested.
Sources: Meshy DCC Core 0.2.4 changelog (Nov 9); official introduction and setup; supported connectors.