MeshCentral Setup & Agent Customization

I already run MeshCentral in a test lab and now want to move to a production-ready, customized build. The goal is to extend the existing platform rather than starting from scratch. Most of the server-side code (NodeJS) can remain stock; the key work sits in the C/C++ agent that installs on each endpoint. Here’s what I need done: • Build and deploy a clean MeshCentral instance on my Windows Server (Node.js LTS already installed). • Fork the agent source, add a brand-new action/command that the current agent does not support, then compile for Windows 10/11 and macOS (Intel + Apple Silicon). • Wire the command into the server so it appears in the web UI and is callable through the REST API. • Document every code change and deliver reproducible build steps (CMake/GCC–Clang toolchain, signing instructions, etc.). • Provide the final agent binaries plus a patch or pull-request style diff for the server integration so I can keep tracking upstream releases. Acceptance criteria 1. A user authenticated in MeshCentral can trigger the new command from the device actions menu and receive the expected output. 2. Source compiles cleanly with ‑Wall and passes the existing agent test suite. 3. All functionality survives a server upgrade test (I’ll pull the next upstream build to confirm). You will have RDP access to a staging VPS and a test Windows VM; macOS builds can be produced in CI if you prefer GitHub Actions. Tools currently in use include Node.js 18.x, Visual Studio 2022, and clang 15, but I’m flexible as long as the result works on the target OS versions.