// the take
The agent binary that pairs with MeshCentral for remote device management — runs on Windows, a long list of Linux distros, macOS and FreeBSD, across x86-32/64, ARM and MIPS, from one C codebase. This is for people running or extending a self-hosted MeshCentral deployment, not a general-purpose RMM tool on its own.
Genuine cross-platform breadth from a single codebase, with CI workflows per OS (freebsd-build.yml, linux-build.yml, mac-build.yml, windows-build.yml) actually exercising that claim instead of just asserting it. It embeds Duktape so the agent core (meshcore) can be pushed and updated as JS from the server without redeploying the compiled binary — explains options like noUpdateCoreModule and forceUpdate in the .msh format. The KVM/remote-desktop code handles the painful platform-specific cases head on: separate Wayland and X11/DRM-EGL capture paths on Linux, with documented GDM/LightDM workarounds for capturing the login screen before a user session exists. There's a real self-test harness (agent-selftest.js) that simulates the actual server handshake and drives WebRTC data channels, KVM, terminal sessions and file transfer with CRC checks, not just isolated unit tests.
Prebuilt lib-jpeg-turbo .a binaries for a half-dozen platform/arch combos are checked straight into the repo instead of built from source — for an agent that runs with high privilege on managed endpoints, that's an opaque dependency to audit. The AMT/Intel ME stack (heci, lme, wsman) plus full KVM and remote terminal access gives this a large attack surface, and there's no visible threat-model or security-architecture doc to match it. Automated testing stops at the manual/interactive self-test — it needs a live server connection and sometimes an elevated, GUI-capable console session, so there's nothing resembling CI-run unit tests for the C core; quality control leans on a manual docs/testing/ReleaseCheckList.md. Documentation is almost entirely operational (per-OS install quirks, .msh config keys) — anyone wanting to understand the custom ILib networking/event stack or the KVM capture pipeline is working from the C source with little beyond a short docs/Architecture.md to go on.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →