Verified, then logged.
Sun 22 Nov 2026 · 00:22 KST / 15:22 UTC한국어 | ENSearch /

02 / IT · Analysis

Meshy DCC Core fixes agent disconnections in `0.2.4`

The update prevents retries when a request's result is unknown and checks app readiness through the path used to send requests.

Image from Meshy
Image: Meshy

Meshy said DCC Core 0.2.4 fixes a fault that disconnects agents when an app opens. The change affects agents using the same local service.

The release notes list 9 Nov as the release date. Alongside keeping agents connected, the update addresses duplicate actions by preventing retries when a request may already have reached an app.

Compatibility. Meshy said an app now counts as ready only after DCC Core reaches it through the path used to send requests. Diagnostics also explain why an app is not ready. This makes readiness checks part of the same connection process that handles requests.

Tool errors and connection failures

Meshy said it changed how DCC Core handles calls to tools that an open app does not have. The service now reports an unknown tool and suggests tools with similar names, rather than reporting the app as offline.

The release notes describe a request that may already have reached an app as having an “unknown result” and state that it is “never sent again”. Possible delivery determines whether the service retries the request, separately from the connection's status. A lost connection therefore does not establish that an action failed to run.

App connections through a local service

Commercial terms. The release notes do not specify a licence or terms for commercial use.

Local operation. Meshy lists support for macOS on Apple Silicon and Windows on x64. Agents connect to a shared local service, without a separate server for each app.

The release notes state that the local service accepts requests only from the same computer. Taken together, connection handling and unknown-result handling make successful connection and completed work distinct states. The update keeps agents connected while preserving that distinction when deciding whether a request can be sent again.