MDM installation

Installer: .pkg

1. Installs the aicodemetricsd binary to /usr/local/bin/
2. Creates a LaunchAgent at ~/Library/LaunchAgents/com.getdx.aicodemetrics.plist
3. Starts the daemon as the logged-in user
4. Detects and installs hooks for supported AI coding agents

If developers have repositories in macOS protected directories (Desktop, Downloads, Documents), Full Disk Access must be granted to /usr/local/bin/aicodemetricsd. Configure this via an MDM privacy preferences policy profile (PPPC).

Installer: .msi

1. Installs the aicodemetricsd binary and a bundled Watchman binary
2. Creates a scheduled task that runs the daemon as the logged-in user
3. Detects and installs hooks for supported AI coding agents

Installer: .tar.gz with install script

Note: Supported on Debian and Red Hat-based distributions, amd64 only.

1. Installs the aicodemetricsd binary to /usr/local/bin/
2. Creates a systemd user service at ~/.config/systemd/user/com.getdx.aicodemetrics.service
3. Enables and starts the service
4. Detects and installs hooks for supported AI coding agents

macOS MDM platforms can deliver credentials via a Configuration Profile using managed preferences. Managed preferences take priority over the config file — if both are present, the Configuration Profile values win.

Preference domain: com.getdx.aicodemetrics

Option A: MDM admin dashboard: If your MDM platform supports custom preference domains (Jamf, Mosyle, Kandji, etc.), add the keys above under the com.getdx.aicodemetrics domain.

Option B: Upload a .mobileconfig file: Use this example as a starting point. Replace each of the API credential placeholders with your organization’s values, generate unique UUIDs for the two PayloadUUID fields, and upload the file to your MDM platform.

Note: The daemon reads managed preferences only at startup. If you push updated credentials via a Configuration Profile after the daemon is already running, restart it with aicodemetricsd restart or by running launchctl unload followed by launchctl load on the plist.

Alternatively, deploy a config file to ~/.aicodemetrics/config.json on each machine.

Credentials can be delivered via the registry at HKLM\SOFTWARE\GetDX\AICodeMetrics using the same key names as the config file (api_url, api_key, log_level). Deploy via Intune, Group Policy, or your MDM platform. Registry values take priority over the config file.

Alternatively, deploy a config file to %LOCALAPPDATA%\aicodemetrics\config.json. Restrict write access to the config directory to prevent user tampering.

Deploy a config file to ~/.aicodemetrics/config.json via Ansible, Chef, or your configuration management tool.